4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chen-Yu Tsai
[ Upstream commit 7f3ed79188f2f094d0ee366fa858857fb7f511ba ]
The HDMI DDC clock found in the CCU is the parent of the actual DDC
clock within the HDMI controller. That clock is
On Wed, Dec 13, 2017 at 02:53:43PM +0100, Sabrina Dubroca wrote:
> generic_gcmaes_decrypt needs to use generic_gcmaes_ctx, not
> aesni_rfc4106_gcm_ctx. This is actually harmless because the fields in
> struct generic_gcmaes_ctx share the layout of the same fields in
> aesni_rfc4106_gcm_ctx.
>
>
On Wed, Dec 13, 2017 at 02:54:36PM +0100, Sabrina Dubroca wrote:
> When I added generic-gcm-aes I didn't add a wrapper like the one
> provided for rfc4106(gcm(aes)). We need to add a cryptd wrapper to fall
> back on in case the FPU is not available, otherwise we might corrupt the
> FPU state.
>
>
On Thu, Dec 21, 2017 at 9:40 PM, Paul Moore wrote:
> On Wed, Dec 20, 2017 at 2:48 AM, syzbot
>
> wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> 6084b576dca2e898f5c101baef151f7bfdbb606d
>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
>> compiler: gcc
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Arvind Yadav
[ Upstream commit 04820da21050b35eed68aa046115d810163ead0c ]
Free memory region, if gb_lights_channel_config is not successful.
Signed-off-by: Arvind Yadav
Reviewed-by: Rui
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Manning
[ Upstream commit 1f372c7bfb23286d2bf4ce0423ab488e86b74bb2 ]
The NS for DAD are sent on admin up as long as a valid qdisc is found.
A race condition exists by which these
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: "Wei Hu(Xavier)"
[ Upstream commit 5e437b1d7e8d31ff9a4b8e898eb3a6cee309edd9 ]
After the loop in hns_roce_v1_mr_free_work_fn function, it is possible that
all qps will have been freed (in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
[ Upstream commit 7841d554809b518a22349e7e39b6b63f8a48d0fb ]
Fix a NULL pointer deref (hu->tty) when calling hci_uart_set_flow_control
on hci_uart-s using serdev.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Keller
[ Upstream commit 17a91809942ca32c70026d2d5ba3348a2c4fdf8f ]
When we process VF mailboxes, the driver is likely going to also queue
up messages to the switch manager. This
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dick Kennedy
[ Upstream commit 2299e4323d2bf6e0728fdc6b9e8e9704978d2dd7 ]
Warning messages when NVME_TARGET_FC not defined on ppc builds
The lpfc_nvmet_replenish_context() function is only
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marek Szyprowski
[ Upstream commit a99897f550de96841aecb811455a67ad7a4e39a7 ]
Odroid HC1 board has built-in JMicron USB to SATA bridge, which supports
UAS protocol. Compile-in support for it
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Williamson
[ Upstream commit 523184972b282cd9ca17a76f6ca4742394856818 ]
With virtual PCI-Express chipsets, we now see userspace/guest drivers
trying to match the physical MPS setting to
On Thu, Dec 21, 2017 at 10:30 PM, Arnd Bergmann wrote:
> According to the comment added to exynos_dt_pmu_match[] in commit
> 8b283c025443 ("ARM: exynos4/5: convert pmu wakeup to stacked domains"),
> the RTC is not able to wake up the system through the PMU on Exynos5410,
> unlike Exynos5420.
>
>
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Brady
[ Upstream commit c53d11f669c0e7d0daf46a717b6712ad0b09de99 ]
Currently there is a bug in which the PF driver fails to inform clients
of a VF reset which then causes clients to
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 1a935bc3d4ea61556461a9e92a68ca3556232efd upstream.
SYSENTER_stack should have reliable overflow detection, which
means that it needs to be at the bottom of a page, not
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 0f9a48100fba3f189724ae88a450c2261bf91c80 upstream.
The existing code was a mess, mainly because C arrays are nasty. Turn
SYSENTER_stack into a struct, add a helper to
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dick Kennedy
[ Upstream commit e8bcf0ae4c0346fdc78ebefe0eefcaa6a6622d38 ]
Local Reject/Invalid RPI errors seen during discovery.
Temporary RPI cleanup was occurring regardless of SLI rev.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Piggin
[ Upstream commit 80e4d70b06863e0104e5a0dc78aa3710297fbd4b ]
In xmon, touch_nmi_watchdog() is not expected to be checking that
other CPUs have not touched the watchdog, so
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Marcelo Ricardo Leitner
[ Upstream commit 1ae2eaaa229bc350b6f38fbf4ab9c873532aecfb ]
As SCTP supports up to 65535 streams, that can lead to very large
allocations in sctp_stream_init(). As
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 40e7f949e0d9a33968ebde5d67f7e3a47c97742a upstream.
The IST stacks are needed when an IST exception occurs and are accessed
before any kernel code at all runs. Move
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 3386bc8aed825e9f1f65ce38df4b109b2019b71a upstream.
Handling SYSCALL is tricky: the SYSCALL handler is entered with every
single register (except FLAGS), including RSP,
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Emil Tantilov
[ Upstream commit dcfd6b839c998bc9838e2a47f44f37afbdf3099c ]
This patch is resolving Coverity hits where padding in a structure could
be used uninitialized.
- Initialize
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Luca Miccio
[ Upstream commit b5dc5d4d1f4ff9032eb6c21a3c571a1317dc9289 ]
Similarly to CFQ, BFQ has its write-throttling heuristics, and it
is better not to combine them with further
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Stuart Hayes
[ Upstream commit 27d6162944b9b34c32cd5841acd21786637ee743 ]
When creating virtual functions, create the "virtfn%u" and "physfn" links
in sysfs *before* attaching the driver
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Lorenzo Bianconi
[ Upstream commit e72a060151e5bb673af24993665e270fc4f674a7 ]
Introduce register mask for data-ready status register since
pressure sensors (e.g. LPS22HB) export just two
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Lihong Yang
[ Upstream commit 784548c40d6f43eff2297220ad7800dc04be03c6 ]
This patch replaces hash_for_each function with hash_for_each_safe
when calling __i40e_del_filter. The
Even without a PIC/PIT we need the legacy timer interrupt for HPET in
legacy replacement mode.
Cc: Zhang Rui
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/kernel/time.c |9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
--- a/arch/x86/kernel/time.c
+++
Various x86 time keeping patches I've collected over the past week.
Without TSC_KNOWN_FREQ we register the TSC clocksource so late we
first switch to the HPET. Using HPET on large CPU count machines is
undesirable.
Therefore register a tsc-early clocksource using the preliminary
tsc_khz from quick calibration. Then when the final TSC calibration
comes in, we can
Hi!
> > > I don't really object using g_endpoint_config() as a temporary solution;
> > > I'd like to have Laurent's opinion on that though. Another option is to
> > > wait, but we've already waited a looong time (as in total).
> >
> > Laurent, do you have some input here? We have simple "2
Greetings from Dr. mohammad ouattara.
Assalamu`Alaikum.
My Name is Dr. mohammad ouattara, I am a banker by profession. I'm
from Ouagadougou, Burkina Faso, West Africa. My reason for contacting
you is to transfer an abandoned $14.6M to your account.
The owner of this fund died since 2004 with
Zhang Rui reported that a Surface Pro 4 will fail to boot with
lapic=notscdeadline. Part of the problem is that that machine doesn't
have a PIC.
If, for some reason, we fall back to TSC calibration, we rely on the
PIT to be present. Allow TSC calibration to reliably fall back to
HPET.
The below
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 6d9256f0a89eaff97fca6006100bcaea8d1d8bdb upstream.
When we start using an entry trampoline, a #GP from userspace will
be delivered on the entry stack, not on the task
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe JAILLET
[ Upstream commit 18eb86362a52f0af933cc0fd5e37027317eb2d1c ]
Check memory allocation failures and return -ENOMEM in such cases, as
already done for other memory
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Varun Prakash
[ Upstream commit 9b3a081fb62158b50bcc90522ca2423017544367 ]
In case of connection reset Tx skb queue can have some skbs which are
not transmitted so purge Tx skb queue in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sreekanth Reddy
[ Upstream commit 2ce9a3645299ba1752873d333d73f67620f4550b ]
Whenever an I/O for a RAID volume fails with IOCStatus
MPI2_IOCSTATUS_SCSI_IOC_TERMINATED and SCSIStatus equal to
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 9aaefe7b59ae00605256a7d6bd1c1456432495fc upstream.
On 64-bit kernels, we used to assume that TSS.sp0 was the current
top of stack. With the addition of an entry
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Derek Basehore
[ Upstream commit 5d0c49acebc9488e37db95f1d4a55644e545ffe7 ]
This fixes an overflow condition that can happen with high max
brightness and period values in compute_duty_cycle.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Murphy
[ Upstream commit fc7556877d1748ac00958822a0a3bba1d4bd9e0d ]
Change the return error code to EINVAL if the MAC
address is not valid in the set_wol function.
Signed-off-by: Dan
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Shakeel Butt
[ Upstream commit 46bea48ac241fe0b413805952dda74dd0c09ba8b ]
The kvm slabs can consume a significant amount of system memory
and indeed in our production environment we have
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Christian Lamparter
[ Upstream commit 778f81d6cdb7d25360f082ac0384d5103f04eca5 ]
If crypto4xx is used in conjunction with dm-crypt, the available
ring buffer elements are not enough to
On Wed, Nov 29, 2017 at 01:15:43PM +0200, Elena Reshetova wrote:
> atomic_t variables are currently used to implement reference
> counters with the following properties:
> - counter is initialized to 1 using atomic_set()
> - a resource is freed upon counter reaching zero
> - once counter
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
[ Upstream commit 5b64a2965dfdfca8039e93303c64e2b15c19ff0c ]
On some platforms, the interrupt for the PL031 is optional. Avoid
trying to claim the interrupt if it's not
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe Jaillet
[ Upstream commit 616129cc6e75fb4da6681c16c981fa82dfe5e4c7 ]
All error handling paths 'goto err_drop_spawn' except this one.
In order to avoid some resources leak, we
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 72f5e08dbba2d01aa90b592cf76c378ea233b00b upstream.
This has a secondary purpose: it puts the entry stack into a region
with a well-controlled layout. A subsequent
On Fri, Dec 22, 2017 at 10:08:00AM +0100, Dmitry Vyukov wrote:
> You mean the messages themselves are translated?
No, just the webapp thing, which is bad enough. The actual messages are
untouched.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chen-Yu Tsai
[ Upstream commit d51fe3ba9773c8b6fc79f82bbe75d64baf604292 ]
The post-divider for the audio PLL is in bits [29:26], as specified
in the user manual, not [19:16] as currently
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Shashank Sharma
[ Upstream commit f687e25a7a245952349f1f9f9cc238ac5a3be258 ]
>From the CI builds, its been observed that during a driver
reload/insert, dp dual mode read function sometimes
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit c482feefe1aeb150156248ba0fd3e029bc886605 upstream.
The TSS is a fairly juicy target for exploits, and, now that the TSS
is in the cpu_entry_area, it's no longer
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chen-Yu Tsai
[ Upstream commit 4cdbc40d64d4b8303a97e29a52862e4d99502beb ]
The round_rate callback for N-M-factor style clocks does not check if
the requested clock rate is supported by the
On 22/12/17 03:04, Cao Zou wrote:
>
>
> On 12/20/2017 12:20 AM, Lorenzo Pieralisi wrote:
>> On Mon, Dec 18, 2017 at 10:02:20AM +0800, Cao Zou wrote:
>>>
>>> On 12/16/2017 01:20 AM, Marc Zyngier wrote:
On 15/12/17 16:17, Lorenzo Pieralisi wrote:
> [+Marc]
>
> On Thu, Dec 14, 2017
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jens Wiklander
commit f044113113dd95ba73916bde10e804d3cdfa2662 upstream.
The first node supplied to of_find_matching_node() has its reference
counter decreased as part of call to that
This patchset add initial support for Allwinner V3s CSI.
Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface
and CSI1 is used for parallel interface. This is not documented in
datasheet but by testing and guess.
This patchset implement a v4l2 framework driver and add a binding
On 2017-12-22 09:46, Greg Kroah-Hartman wrote:
> 4.9-stable review patch. If anyone has any objections, please let me know.
I don't think this is relevant since the interrupt support code was
added in 4.11 or something like that with
f2114795f721 ("i2c: mux: pca954x: Add interrupt controller
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 79cc74155218316b9a5d28577c7077b2adba8e58 upstream.
There is no generic way to test whether a kernel is running on a specific
hypervisor. But that's required to prevent
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 6cbd2171e89b13377261d15e64384df60ecb530e upstream.
There is currently no way to force CPU bug bits like CPU feature bits. That
makes it impossible to set a bug bit once
On Fri, Dec 22, 2017 at 08:06:03PM +1100, Herbert Xu wrote:
> On Fri, Dec 22, 2017 at 09:41:48AM +0100, Corentin Labbe wrote:
> >
> > It's you that was suggesting using crypto_async_request:
> > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1474434.html
> > "The only wart with this
On 22/12/17 07:38, Cao Zou wrote:
>
>
> On 12/22/2017 11:04 AM, Cao Zou wrote:
>>
>>
>> On 12/20/2017 12:20 AM, Lorenzo Pieralisi wrote:
>>> On Mon, Dec 18, 2017 at 10:02:20AM +0800, Cao Zou wrote:
On 12/16/2017 01:20 AM, Marc Zyngier wrote:
> On 15/12/17 16:17, Lorenzo Pieralisi
Hi Xu YiPing,
On 2017/11/9 11:18, Xu YiPing wrote:
> cortex-a73 pmu driver is supported now. hi3660 is 4*a73 + 4*a53, so it
> should use "cortex-a73-pmu" and "cortex-a53-pmu" instead of "armpmu-v3",
> then we can use the a73 and a53 events in perf tool directly.
>
> Signed-off-by: Xu YiPing
On Fri 22-12-17 09:46:33, Greg KH wrote:
> 4.14-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Shakeel Butt
>
>
> [ Upstream commit 46bea48ac241fe0b413805952dda74dd0c09ba8b ]
>
> The kvm slabs can consume a significant amount of
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 21506525fb8ddb0342f2a2370812d47f6a1f3833 upstream.
The cpu_entry_area will contain stacks. Make sure that KASAN has
appropriate shadow mappings for them.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit bd7dc5a6afac719d8ce4092391eef2c7e83c2a75 upstream.
This causes the MSR_IA32_SYSENTER_CS write to move out of the
paravirt callback. This shouldn't affect Xen PV: Xen
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 3383642c2f9d4f5b4fa37436db4a109a1a10018c upstream.
Let's keep the stack-related logic together rather than open-coding
a comparison in an assertion in the traps code.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit 1e4c4f610f774df6088d7c065b2dd4d22adba698 upstream.
Convert TESTL to TESTB and save 3 bytes per callsite.
No functionality change.
Signed-off-by: Borislav Petkov
Cc:
Hi Leo,
On 2017/12/12 9:12, Leo Yan wrote:
> Thanks a lot for Vincent Guittot careful work to find bug for 'CPU_NAP'
> idle state. From ftrace log we can observe CA73 CPUs can be easily
> waken up from 'CPU_NAP' state but the 'waken up' CPUs doesn't handle
> anything and sleep again; so there
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit d375cf1530595e33961a8844192cddab913650e3 upstream.
On x86_64, we can easily calculate sp0 when needed instead of
storing it in thread_struct.
On x86_32, a similar
Hi Valentin,
On 2017/12/13 14:21, Valentin Schneider wrote:
> The following dt entries are added:
> cpus [0-3] (Cortex A53):
>- capacity-dmips-mhz = <592>;
>
> cpus [4-7] (Cortex A73):
>- capacity-dmips-mhz = <1024>;
>
> Those values were obtained by running dhrystone 2.1 on a
>
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit cd493a6deb8b78eca280d05f7fa73fd69403ae29 upstream.
cpu_current_top_of_stack's initialization forgot about
TOP_OF_KERNEL_STACK_PADDING. This bug didn't matter because
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit aaeed3aeb39c1ba69f0a49baec8cb728121d0a91 upstream.
We currently have CPU 0's GDT at the top of the GDT range and
higher-numbered CPUs at lower addresses. This happens
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 46f5a10a721ce8dce8cc8fe55279b49e1c6b3288 upstream.
The only remaining readers in context switch code or vm86(), and
they all just want to update TSS.sp0 to match the
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 20bb83443ea79087b5e5f8dab4e9d80bb9bf7acb upstream.
In my quest to get rid of thread_struct::sp0, I want to clean up or
remove all of its readers. Two of them are in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 7fb983b4dd569e08564134a850dfd4eb1c63d9b8 upstream.
A future patch will move SYSENTER_stack to the beginning of cpu_tss
to help detect overflow. Before this can happen,
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 4f3789e792296e21405f708cf3cb409d7c7d5683 upstream.
In case something goes wrong with unwind (not unlikely in case of
overflow), print the offending IP where we detected
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit ef8813ab280507972bb57e4b1b502811ad4411e9 upstream.
Currently, the GDT is an ad-hoc array of pages, one per CPU, in the
fixmap. Generalize it to be an array of a new
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 1a79797b58cddfa948420a7553241c79c013e3ca upstream.
This will simplify future changes that want scratch variables early in
the SYSENTER handler -- they'll be able to
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 33a2f1a6c4d7c0a02d1c006fb0379cc5ca3b96bb upstream.
get_stack_info() doesn't currently know about the SYSENTER stack, so
unwinding will fail if we entered the kernel on
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit d3a09104018cf2ad5973dfa8a9c138ef9f5015a3 upstream.
If the stack overflows into a guard page and the ORC unwinder should work
well: by construction, there can't be any
On 12/22/2017 05:32 PM, Marc Zyngier wrote:
On 22/12/17 03:04, Cao Zou wrote:
On 12/20/2017 12:20 AM, Lorenzo Pieralisi wrote:
On Mon, Dec 18, 2017 at 10:02:20AM +0800, Cao Zou wrote:
On 12/16/2017 01:20 AM, Marc Zyngier wrote:
On 15/12/17 16:17, Lorenzo Pieralisi wrote:
[+Marc]
On Thu,
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andi Kleen
commit 2fe1bc1f501d55e5925b4035bcd85781adc76c63 upstream.
[ Note, this is a Git cherry-pick of the following commit:
a47ba4d77e12 ("perf/x86: Enable free running PEBS for
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 6669a692605547892a026445e460bf233958bd7f upstream.
That race has been fixed and code cleaned up for a while now.
Signed-off-by: Andy Lutomirski
Signed-off-by: Thomas
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Josh Poimboeuf
commit b02fcf9ba1211097754b286043cd87a8b4907e75 upstream.
There are at least two unwinder bugs hindering the debugging of
stack-overflow crashes:
- It doesn't deal gracefully
Add binding documentation for Allwinner V3s CSI.
Signed-off-by: Yong Deng
---
.../devicetree/bindings/media/sun6i-csi.txt| 51 ++
1 file changed, 51 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/sun6i-csi.txt
diff --git
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit f16b3da1dc936c0f8121741d0a1731bf242f2f56 upstream.
I'm removing thread_struct::sp0, and Xen's usage of it is slightly
dubious and unnecessary. Use appropriate helpers
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit c2bc66082e1048c7573d72e62f597bdc5ce13fea upstream.
[ Note, this is a Git cherry-pick of the following commit:
76ebbe78f739 ("locking/barriers: Add implicit
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andrey Ryabinin
commit 2aeb07365bcd489620f71390a7d2031cd4dfb83e upstream.
[ Note, this is a Git cherry-pick of the following commit:
d17a1d97dc20: ("x86/mm/kasan: don't use
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Boris Ostrovsky
commit e17f8234538d1ff708673f287a42457c4dee720d upstream.
Commit 1d3e53e8624a ("x86/entry/64: Refactor IRQ stacks and make them
NMI-safe") added DEBUG_ENTRY_ASSERT_IRQS_OFF
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ricardo Neri
commit a8b4db562e7283a1520f9e9730297ecaab7622ea upstream.
[ Note, this is a Git cherry-pick of the following commit: (limited to the
cpufeatures.h file)
3522c2a6a4f3
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Juergen Gross
commit 03b2a320b19f1424e9ac9c21696be9c60b6d0d93 upstream.
The x86_hyper pointer is only used for checking whether a virtual
device is supporting the hypervisor the system is
Current clk_pm_runtime_put is using pm_runtime_put_sync which
is not safe to be called in clk_core_is_enabled as it should
be able to run in atomic context.
Thus use pm_runtime_put instead which is atomic safe.
Cc: Stephen Boyd
Cc: Michael Turquette
Cc: Ulf Hansson
Cc: Marek Szyprowski
According to design doc, .is_enabled should be protected by enable lock.
Then users don't have to protect it against enable/disable operation
in clock drivers.
See: Documentation/clk.txt
"The enable lock is a spinlock and is held across calls to the .enable,
.disable and .is_enabled operations."
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ingo Molnar
commit 1784f9144b143a1e8b19fe94083b040aa559182b upstream.
We'd like to use the 'PTI' acronym for 'Page Table Isolation' - free up the
namespace by renaming the driver header to .
Those comments are invalid anymore. So remove them.
Cc: Stephen Boyd
Signed-off-by: Dong Aisheng
---
drivers/clk/clk.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index d6e2d5c..4675adf 100644
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: James Morse
commit 4f89fa286f6729312e227e7c2d764e8e7b9d340e upstream.
Replace ghes_io{re,un}map_pfn_{nmi,irq}()s use of ioremap_page_range()
with __set_fixmap() as ioremap_page_range() may
Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface
and CSI1 is used for parallel interface. This is not documented in
datasheet but by testing and guess.
This patch implement a v4l2 framework driver for it.
Currently, the driver only support the parallel interface. MIPI-CSI2,
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit d744dcad39094c9187075e274d1cdef79c57c8b5 upstream.
Much of the test design could apply to set_thread_area() (i.e. GDT),
not just modify_ldt(). Add set_thread_area() to
On Thu 21-12-17 15:35:28, Mike Kravetz wrote:
[...]
> You can add,
>
> Reviewed-by: Mike Kravetz
>
> I had some concerns about transferring huge page state during migration
> not specific to this patch, so I did a bunch of testing.
On Fri 22-12-17 08:58:48, Naoya Horiguchi wrote:
[...]
> Yes,
Hi Cyrille
On Wednesday 20 December 2017 08:43 PM, Cyrille Pitchen wrote:
> Hi Vignesh,
>
> Le 07/12/2017 à 07:38, Vignesh R a écrit :
>> Cadence QSPI controller provides direct access mode through which flash
>> can be accessed in a memory-mapped IO mode. This enables read/write to
>> flash
On Fri, Dec 22, 2017 at 10:30 AM, Peter Zijlstra wrote:
> On Fri, Dec 22, 2017 at 10:08:00AM +0100, Dmitry Vyukov wrote:
>
>> You mean the messages themselves are translated?
>
> No, just the webapp thing, which is bad enough. The actual messages are
> untouched.
Then try to open dev console in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ingo Molnar
commit f3a624e901c633593156f7b00ca743a6204a29bc upstream.
Kept this commit separate from the re-tabulation changes, to make
the changes easier to review:
- add better
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 1943dc07b45e347c52c1bfdd4a37e04a86e399aa upstream.
These ops are not endian safe and may break on architectures which have
aligment requirements.
Reverts: cbe96375025e
1101 - 1200 of 1842 matches
Mail list logo
