Re: [RFC PATCH 2/5] sched: Add NOHZ_STATS_KICK

On Thu, Dec 21, 2017 at 05:56:32PM +0100, Vincent Guittot wrote: > In fact, we can't only rely on the tick and newly_idle load balance to > ensure a period update of the blocked load because they can never > happen. I'm confused, why would the ilb not happen?

[PATCH] HID: corsair: Add K70 Vengeance and K70 RAPIDFIRE to supported devices.

K70 Vengence sends garbage keypresses when changing backlight brightness. This hooks to the existing corsair driver, which filters out those invalid keypresses on similar devices in the input mapping code. Signed-off-by: Aaron Bottegal --- drivers/hid/hid-corsair.c | 8

Re: [PATCH 1/1] usb: xhci: dbc: Add SPDX identifiers to dbc files

Lu, On Fri, Dec 22, 2017 at 2:34 AM, Lu Baolu wrote: > Update the xhci dbc files with the correct SPDX license identifiers. > > Fixes: dfba2174dc42 ("usb: xhci: Add DbC support in xHCI driver") > Signed-off-by: Lu Baolu > --- >

[ANNOUNCE] OSPM-summit 2018 - Registrations are open!

Power Management and Scheduling in the Linux Kernel II edition (OSPM-summit 2018) April 16-18, 2018 Scuola Superiore Sant'Anna Pisa, Italy https://marc.info/?l=linux-kernel=151075286322645=2 http://retis.sssup.it/ospm-summit/ --- REGISTRATIONS ARE NOW OPEN! Attending the OSPM-summit is free

[PATCH V2] HID: corsair: Add K70 Vengeance and K70 RAPIDFIRE to

K70 Vengeance sends garbage keypresses when changing backlight brightness. This hooks to the existing corsair driver, which filters out those invalid keypresses on similar devices in the input mapping code. V2: Fix spelling. Signed-off-by: Aaron Bottegal ---

Re: [PATCH] ASoC: max98373: Added Amplifier Driver

Ryan, On Fri, Dec 22, 2017 at 2:43 AM, Ryan Lee wrote: > Signed-off-by: Ryan Lee > --- > > Created max98373 amplifier driver. > > --- /dev/null > +++ b/sound/soc/codecs/max98373.c > @@ -0,0 +1,996 @@ > +/* > + * max98373.c --

Re: [PATCH] crypto: exynos - Icrease the priority of the driver

On Tue, Dec 05, 2017 at 05:20:46PM +0100, Łukasz Stelmach wrote: > exynos-rng is one of many implementations of stdrng. With priority as > low as 100 it isn't selected, if software implementations (DRBG) are > available. The value 300 was selected to give the PRNG priority before > software

[PATCH 4.9 030/104] pinctrl: st: add irq_request/release_resources callbacks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Patrice Chotard [ Upstream commit e855fa9a65c40788b5069abb0d094537daa22e05 ] When using GPIO as IRQ source, the GPIO must be configured in INPUT. Callbacks dedicated

[PATCH 4.9 077/104] scsi: mpt3sas: Fix IO error occurs on pulling out a drive from RAID1 volume created on two SATA drive

4.9-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

[PATCH 4.9 064/104] xhci: plat: Register shutdown for xhci_plat

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adam Wallis [ Upstream commit b07c12517f2aed0add8ce18146bb426b14099392 ] Shutdown should be called for xhci_plat devices especially for situations where kexec might be

[PATCH 4.9 065/104] netfilter: nfnetlink_queue: fix secctx memory leak

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Liping Zhang [ Upstream commit 77c1c03c5b8ef28e55bb0aff29b1e006037ca645 ] We must call security_release_secctx to free the memory returned by security_secid_to_secctx,

[PATCH 4.9 060/104] virtio-balloon: use actual number of stats for stats queue buffers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ladi Prosek [ Upstream commit 9646b26e85896ef0256e66649f7937f774dc18a6 ] The virtio balloon driver contained a not-so-obvious invariant that update_balloon_stats has to

[PATCH 4.9 058/104] net: ipconfig: fix ic_close_devs() use-after-free

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mark Rutland [ Upstream commit ffefb6f4d6ad699a2b5484241bc46745a53235d0 ] Our chosen ic_dev may be anywhere in our list of ic_devs, and we may free it before attempting

[PATCH 4.9 041/104] s390/qeth: size calculation outbound buffers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 7d969d2e8890f546c8cec634b3aa5f57d4eef883 ] Depending on the device type, hard_start_xmit() builds different output buffer formats.

Re: [PATCH v3 04/21] fpga: add device feature list support

On Thu, Dec 21, 2017 at 03:22:42PM +0800, Wu Hao wrote: > On Wed, Dec 20, 2017 at 06:58:01PM -0600, Alan Tull wrote: > > On Wed, Dec 20, 2017 at 4:29 PM, Alan Tull wrote: > > > On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote: > > > > > > Hi Hao, > > > > > >> +

[PATCH 4.9 025/104] netfilter: nfnl_cthelper: Fix memory leak

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jeffy Chen [ Upstream commit f83bf8da1135ca635aac8f062cad3f001fcf3a26 ] We have memory leaks of nf_conntrack_helper & expect_policy. Signed-off-by: Jeffy Chen

Re: [PATCH v3 2/3] hwrng: exynos - add Samsung Exynos True RNG driver

On Mon, Dec 04, 2017 at 01:53:50PM +0100, Łukasz Stelmach wrote: > Add support for True Random Number Generator found in Samsung Exynos > 5250+ SoCs. > > Signed-off-by: Łukasz Stelmach This doesn't build for me: CC [M] drivers/char/hw_random/exynos-trng.o

Re: [PATCH v20 3/7 RESEND] xbitmap: add more operations

On 12/21/2017 10:37 PM, Tetsuo Handa wrote: Matthew Wilcox wrote: +/** + * xb_find_set - find the next set bit in a range of bits + * @xb: the xbitmap to search from + * @offset: the offset in the range to start searching + * @size: the size of the range + * + * Returns: the found bit or, @size

Re: general protection fault in finish_task_switch

On Fri, Dec 22, 2017 at 9:36 AM, Peter Zijlstra wrote: > On Fri, Dec 22, 2017 at 09:26:28AM +0100, Dmitry Vyukov wrote: >> I think this is another manifestation of "KASAN: use-after-free Read >> in __schedule": >>

[PATCH 3.18 00/38] 3.18.90-stable review

This is the start of the stable review cycle for the 3.18.90 release. There are 38 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sun Dec 24 08:44:40 UTC 2017. Anything

[PATCH 4.4 18/78] arm: kprobes: Fix the return address of multiple kretprobes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu [ Upstream commit 06553175f585b52509c7df37d6f4a50aacb7b211 ] This is arm port of commit 737480a0d525 ("kprobes/x86: Fix the return address of multiple

[PATCH 4.4 12/78] x86/mm, sched/core: Turn off IRQs in switch_mm()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 078194f8e9fe3cf54c8fd8bded48a1db5bd8eb8a upstream. Potential races between switch_mm() and TLB-flush or LDT-flush IPIs could be very messy. AFAICT the

[PATCH 3.18 26/38] ARM: dma-mapping: disallow dma_get_sgtable() for non-kernel managed memory

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Russell King [ Upstream commit 916a008b4b8ecc02fbd035cfb133773dba1ff3d7 ] dma_get_sgtable() tries to create a scatterlist table containing valid struct page

[PATCH 3.18 21/38] netfilter: nfnl_cthelper: fix a race when walk the nf_ct_helper_hash table

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Liping Zhang [ Upstream commit 83d90219a5df8d950855ce73229a97b63605c317 ] The nf_ct_helper_hash table is protected by nf_ct_helper_mutex, while nfct_helper operation is

[PATCH 3.18 32/38] scsi: cxgb4i: fix Tx skb leak

3.18-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

[PATCH 3.18 07/38] usb: gadget: f_uvc: Sanity check wMaxPacketSize for SuperSpeed

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Roger Quadros [ Upstream commit 16bb05d98c904a4f6c5ce7e2d992299f794acbf2 ] As per USB3.0 Specification "Table 9-20. Standard Endpoint Descriptor", for interrupt and

[PATCH 4.4 13/78] ARM: Hide finish_arch_post_lock_switch() from modules

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt commit ef0491ea17f8019821c7e9c8e801184ecf17f85a upstream. The introduction of switch_mm_irqs_off() brought back an old bug regarding the use of

[PATCH 3.18 30/38] net: phy: at803x: Change error to EINVAL for invalid MAC

3.18-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.

[PATCH 3.18 31/38] PCI: Avoid bus reset if bridge itself is broken

3.18-stable review patch. If anyone has any objections, please let me know. -- From: David Daney [ Upstream commit 357027786f3523d26f42391aa4c075b8495e5d28 ] When checking to see if a PCI bus can safely be reset, we previously checked to see if any of

[PATCH 3.18 19/38] i40e: Do not enable NAPI on q_vectors that have no rings

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Duyck [ Upstream commit 13a8cd191a2b470cfd435b3b57dbd21aa65ff78c ] When testing the epoll w/ busy poll code I found that I could get into a state where

[PATCH 3.18 24/38] isdn: kcapi: avoid uninitialized data

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit af109a2cf6a9a6271fa420ae2d64d72d86c92b7d ] gcc-7 points out that the AVMB1_ADDCARD ioctl results in an unintialized value ending up in the

[PATCH 3.18 18/38] net: Do not allow negative values for busy_read and busy_poll sysctl interfaces

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Duyck [ Upstream commit 95f255211396958c718aef8c45e3923b5211ea7b ] This change basically codifies what I think was already the limitations on the

[PATCH 4.4 15/78] x86/irq: Do not substract irq_tlb_count from irq_call_count

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Aaron Lu commit 82ba4faca1bffad429f15c90c980ffd010366c25 upstream. Since commit: 52aec3308db8 ("x86/tlb: replace INVALIDATE_TLB_VECTOR by CALL_FUNCTION_VECTOR") the

[PATCH 4.14 038/159] x86/entry/64: Simplify reg restore code in the standard IRET paths

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit e872045bfd9c465a8555bab4b8567d56a4d2d3bb upstream. The old code restored all the registers with movq instead of pop. In theory, this was done because

[PATCH 4.14 026/159] x86/xen: Drop 5-level paging support code from the XEN_PV code

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 773dd2fca581b0a80e5a2cc8ee67e5a79cba upstream. It was decided 5-level paging is not going to be supported in XEN_PV. Let's drop

[PATCH 4.14 030/159] x86/mm/64: Rename the register_page_bootmem_memmap() size parameter to nr_pages

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Baoquan He commit 15670bfe19905b1dcbb63137f40d718b59d84479 upstream. register_page_bootmem_memmap()'s 3rd 'size' parameter is named in a somewhat misleading fashion - rename

[PATCH 4.14 027/159] ACPI / APEI: remove the unused dead-code for SEA/NMI notification type

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dongjiu Geng commit c49870e89f4d2c21c76ebe90568246bb0f3572b7 upstream. For the SEA notification, the two functions ghes_sea_add() and ghes_sea_remove() are only called

[PATCH 4.14 025/159] x86/xen: Provide pre-built page tables only for CONFIG_XEN_PV=y and CONFIG_XEN_PVH=y

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 4375c29985f155d7eb2346615d84e62d1b673682 upstream. Looks like we only need pre-built page tables in the CONFIG_XEN_PV=y and

[PATCH 4.14 015/159] bitops: Add clear/set_bit32() to linux/bitops.h

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andi Kleen commit cbe96375025e14fc76f9ed42ee5225120d7210f8 upstream. Add two simple wrappers around set_bit/clear_bit() that accept the common case of an u32 array. This

[PATCH 4.14 056/159] x86/cpuid: Replace set/clear_bit32()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 06dd688ddda5819025e014b79aea9af6ab475fa2 upstream. Peter pointed out that the set/clear_bit32() variants are broken in various aspects. Replace

[PATCH 4.14 010/159] ACPI / APEI: adjust a local variable type in ghes_ioremap_pfn_irq()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich commit 095f613c6b386a1704b73a549e9ba66c1d5381ae upstream. Match up with what 7edda0886b ("acpi: apei: handle SEA notification type for ARMv8") did for

Re: [PATCH v3 0/6] cpufreq: schedutil: fixes for flags updates

On Thu, Dec 21, 2017 at 04:13:17PM +0530, Viresh Kumar wrote: > On 21-12-17, 11:39, Peter Zijlstra wrote: > > The difference is that we apply the per-cpu boost on the per-cpu util > > value and _then_ find the overall maximum. > > > > Instead of finding the overall maximum and then apply the

Re: [PATCH v3 2/3] hwrng: exynos - add Samsung Exynos True RNG driver

Hi, On 2017-12-22 09:24, Herbert Xu wrote: On Mon, Dec 04, 2017 at 01:53:50PM +0100, Łukasz Stelmach wrote: Add support for True Random Number Generator found in Samsung Exynos 5250+ SoCs. Signed-off-by: Łukasz Stelmach This doesn't build for me: CC [M]

[PATCH] staging: pi433: fix CamelCase for maxMinus variables

Fixes checkpatch warnings: CHECK: Avoid CamelCase: CHECK: Avoid CamelCase: CHECK: Avoid CamelCase: CHECK: Avoid CamelCase: CHECK: Avoid CamelCase: Signed-off-by: Valentin Vidic --- drivers/staging/pi433/Documentation/pi433.txt | 10 +-

Re: general protection fault in finish_task_switch

On Thu, Dec 21, 2017 at 7:42 PM, Linus Torvalds wrote: > On Wed, Dec 20, 2017 at 8:03 AM, syzbot > > wrote: >> Hello, >> >> syzkaller hit the following crash on >>

Re: [PATCH 02/45] drivers: crypto: remove duplicate includes

On Tue, Dec 05, 2017 at 07:27:22AM +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. > > Signed-off-by: Pravin Shedge Patch applied.

Re: general protection fault in finish_task_switch

On Fri, Dec 22, 2017 at 09:26:28AM +0100, Dmitry Vyukov wrote: > I think this is another manifestation of "KASAN: use-after-free Read > in __schedule": > https://groups.google.com/forum/#!msg/syzkaller-bugs/-8JZhr4W8AY/FpPFh8EqAQAJ > +Eric already mailed a fix for it (indeed new bug in kvm code).

Re: [PATCH] crypto: pcrypt - fix freeing pcrypt instances

On Wed, Dec 20, 2017 at 02:28:25PM -0800, Eric Biggers wrote: > From: Eric Biggers > > pcrypt is using the old way of freeing instances, where the ->free() > method specified in the 'struct crypto_template' is passed a pointer to > the 'struct crypto_instance'. But the

Re: stable-rc/linux-4.9.y build: 183 builds: 179 failed, 4 passed, 179 errors (v4.9.71-115-gd4b9c892aea4)

On Thu, Dec 21, 2017 at 10:19:27AM -0800, Eduardo Valentin wrote: > On Thu, Dec 21, 2017 at 03:49:20PM +0100, gregkh wrote: > > On Thu, Dec 21, 2017 at 12:33:45PM +0100, Arnd Bergmann wrote: > > > On Thu, Dec 21, 2017 at 12:06 PM, kernelci.org bot > > > wrote: > > > >

[PATCH 4.9 070/104] backlight: pwm_bl: Fix overflow condition

4.9-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

[PATCH 4.9 071/104] crypto: crypto4xx - increase context and scatter ring buffer elements

4.9-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

[PATCH 4.9 103/104] platform/x86: asus-wireless: send an EV_SYN/SYN_REPORT between state changes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Hutterer commit bff5bf9db1c9453ffd0a78abed3e2d040c092fd9 upstream. Sending the switch state change twice within the same frame is invalid evdev protocol and

[PATCH 4.9 068/104] cpuidle: powernv: Pass correct drv->cpumask for registration

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vaidyanathan Srinivasan [ Upstream commit 293d264f13cbde328d5477f49e3103edbc1dc191 ] drv->cpumask defaults to cpu_possible_mask in __cpuidle_driver_init(). On

[PATCH 4.14 005/159] x86/head: Fix head ELF function annotations

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Josh Poimboeuf commit 015a2ea5478680fc5216d56b7ff306f2a74efaf9 upstream. These functions aren't callable C-type functions, so don't annotate them as such. Signed-off-by:

[PATCH 4.14 016/159] x86/cpuid: Add generic table for CPUID dependencies

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andi Kleen commit 0b00de857a648dafe7020878c7a27cf776f5edf4 upstream. Some CPUID features depend on other features. Currently it's possible to to clear dependent

[PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 upstream. Size of the mem_section[] array depends on the size of the physical address

[PATCH 4.14 021/159] objtool: Print top level commands on incorrect usage

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kamalesh Babulal commit 6a93bb7e4a7d6670677d5b0eb980936eb9cc5d2e upstream. Print top-level objtool commands, along with the error on incorrect command line usage.

[PATCH 4.14 019/159] x86/fpu: Remove the explicit clearing of XSAVE dependent features

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andi Kleen commit 73e3a7d2a7c3be29a5a22b85026f6cfa5664267f upstream. Clearing a CPU feature with setup_clear_cpu_cap() clears all features which depend on it. Expressing

Re: [PATCH][next] soundwire: intel: fix missing assignment to ret

On Fri, Dec 22, 2017 at 08:15:22AM +0100, Greg KH wrote: > On Fri, Dec 22, 2017 at 09:01:49AM +0530, Vinod Koul wrote: > > On Thu, Dec 21, 2017 at 11:32:10PM +, Colin King wrote: > > > From: Colin Ian King > > > > > > Currently the return status ret is being checked

Re: [RFC PATCH 2/5] sched: Add NOHZ_STATS_KICK

On 22 December 2017 at 08:59, Peter Zijlstra wrote: > On Thu, Dec 21, 2017 at 05:56:32PM +0100, Vincent Guittot wrote: >> In fact, we can't only rely on the tick and newly_idle load balance to >> ensure a period update of the blocked load because they can never >> happen. >

[PATCH V2] KVM/Eventfd: Avoid crash when assign and deassign specific eventfd in parallel.

Syzroot reports crash in kvm_irqfd_assign() is caused by use-after-free. Because kvm_irqfd_assign() and kvm_irqfd_deassign() can't run in parallel for one specific eventfd. When assign path hasn't been finished after irqfd has been added to kvm->irqfds.items list, another thead may deassign the

RE: [usb gadget]use dev_kfree_skb_irq instead of dev_kfree_skb

Hi, > -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Friday, December 22, 2017 3:50 PM > To: Lipengcheng > Cc: ba...@kernel.org; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [usb gadget]use dev_kfree_skb_irq instead of dev_kfree_skb

Re: [PATCH v2] ARM: dts: sunxi: Add sid for a83t

On Thu, Dec 21, 2017 at 07:09:03PM +0100, Emmanuel Vadot wrote: > > Hi Maxime, > > On Thu, 21 Dec 2017 16:26:30 +0100 > Maxime Ripard wrote: > > > Hi, > > > > On Thu, Dec 21, 2017 at 09:19:24AM -0600, Kyle Evans wrote: > > > On Thu, Dec 21, 2017 at 8:55 AM,

Re: [PATCH v3 2/3] hwrng: exynos - add Samsung Exynos True RNG driver

On Fri, Dec 22, 2017 at 09:29:38AM +0100, Marek Szyprowski wrote: > Hi, > > On 2017-12-22 09:24, Herbert Xu wrote: > >On Mon, Dec 04, 2017 at 01:53:50PM +0100, Łukasz Stelmach wrote: > >>Add support for True Random Number Generator found in Samsung Exynos > >>5250+ SoCs. > >> > >>Signed-off-by:

[PATCH 4.9 028/104] tipc: fix nametbl deadlock at tipc_nametbl_unsubscribe

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ying Xue [ Upstream commit 557d054c01da0337ca81de9e9d9206d57245b57e ] Until now, tipc_nametbl_unsubscribe() is called at subscriptions reference count cleanup. Usually

[PATCH 4.9 084/104] tracing: Exclude generic fields from histograms

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tom Zanussi [ Upstream commit a15f7fc20389a8827d5859907568b201234d4b79 ] There are a small number of 'generic fields' (comm/COMM/cpu/CPU) that are found by

[PATCH 4.9 088/104] scsi: lpfc: PLOGI failures during NPIV testing

4.9-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

[PATCH 4.9 087/104] scsi: lpfc: Fix secure firmware updates

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dick Kennedy [ Upstream commit 184fc2b9a8bcbda9c14d0a1e7fbecfc028c7702e ] Firmware update fails with: status x17 add_status x56 on the final write If multiple DMA

[PATCH 4.9 095/104] rtc: set the alarm to the next expiring timer

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexandre Belloni [ Upstream commit 74717b28cb32e1ad3c1042cafd76b264c8c0f68d ] If there is any non expired timer in the queue, the RTC alarm is never

[PATCH 4.9 098/104] thermal/drivers/hisi: Fix missing interrupt enablement

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Lezcano commit c176b10b025acee4dc8f2ab1cd64eb73b5ccef53 upstream. The interrupt for the temperature threshold is not enabled at the end of the probe function,

[PATCH 4.9 066/104] Btrfs: fix an integer overflow check

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 457ae7268b29c33dee1c0feb143a15f6029d177b ] This isn't super serious because you need CAP_ADMIN to run this code. I added this

[PATCH 4.14 090/159] x86/entry/64: Use a per-CPU trampoline stack for IDT entries

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 7f2590a110b837af5679d08fc25c6227c5a8c497 upstream. Historically, IDT entries from usermode have always gone directly to the running task's kernel

[PATCH 4.14 110/159] PCI: Avoid bus reset if bridge itself is broken

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Daney [ Upstream commit 357027786f3523d26f42391aa4c075b8495e5d28 ] When checking to see if a PCI bus can safely be reset, we previously checked to see if any of

[PATCH 4.14 122/159] ip_gre: check packet length and mtu correctly in erspan tx

4.14-stable review patch. If anyone has any objections, please let me know. -- From: William Tu [ Upstream commit f192970de860d3ab90aa9e2a22853201a57bde78 ] Similarly to early patch for erspan_xmit(), the ARPHDR_ETHER device is the length of the whole

[PATCH 4.14 091/159] x86/entry/64: Return to userspace from the trampoline stack

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 3e3b9293d392c577b62e24e4bc9982320438e749 upstream. By itself, this is useless. It gives us the ability to run some final code before exit that cannnot

[PATCH 4.14 094/159] x86/entry/64: Remove the SYSENTER stack canary

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit 7fbbd5cbebf118a9e09f5453f686656a167c3d1c upstream. Now that the SYSENTER stack has a guard page, there's no need for a canary to detect overflow after

[PATCH 4.14 137/159] scsi: lpfc: Fix secure firmware updates

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dick Kennedy [ Upstream commit 184fc2b9a8bcbda9c14d0a1e7fbecfc028c7702e ] Firmware update fails with: status x17 add_status x56 on the final write If multiple DMA

[PATCH 4.14 135/159] ASoC: codecs: msm8916-wcd-analog: fix module autoload

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Dechesne [ Upstream commit 46d69e141d479585c105a4d5b2337cd2ce6967e5 ] If the driver is built as a module, autoload won't work because the module alias

[PATCH 4.14 121/159] md: always set THREAD_WAKEUP and wake up wqueue if thread existed

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Guoqing Jiang [ Upstream commit d1d90147c9680aaec4a5757932c2103c42c9c23b ] Since commit 4ad23a976413 ("MD: use per-cpu counter for writes_pending"), the wait_queue is only

[PATCH 4.14 136/159] fm10k: fix mis-ordered parameters in declaration for .ndo_set_vf_bw

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jacob Keller [ Upstream commit 3e256ac5b1ec307e5dd5a4c99fbdbc651446c738 ] We've had support for setting both a minimum and maximum bandwidth via .ndo_set_vf_bw

[PATCH 4.14 154/159] IB/opa_vnic: Properly return the total MACs in UC MAC list

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Niranjana Vishwanathapura [ Upstream commit b77eb45e0d9c324245d165656ab3b38b6f386436 ] Do not include EM specified MAC address in total MACs of the UC

[PATCH 4.14 144/159] ibmvnic: Set state UP

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mick Tarsel [ Upstream commit e876a8a7e9dd89dc88c12ca2e81beb478dbe9897 ] State is initially reported as UNKNOWN. Before register call netif_carrier_off(). Once

[PATCH 4.14 150/159] rtc: set the alarm to the next expiring timer

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexandre Belloni [ Upstream commit 74717b28cb32e1ad3c1042cafd76b264c8c0f68d ] If there is any non expired timer in the queue, the RTC alarm is never

[PATCH 4.14 149/159] tcp: fix under-evaluated ssthresh in TCP Vegas

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hoang Tran [ Upstream commit cf5d74b85ef40c202c76d90959db4d850f301b95 ] With the commit 76174004a0f19785 (tcp: do not slow start when cwnd equals ssthresh), the

Re: [PATCH 2/2] crypto: seqiv - Remove unused alg/spawn variable

On Tue, Dec 12, 2017 at 07:30:14PM +, Corentin Labbe wrote: > This patch remove two unused variable and some dead "code" using it. > > Fixes: 92932d03c2b3 ("crypto: seqiv - Remove AEAD compatibility code") > > Signed-off-by: Corentin Labbe Patch applied. Thanks. --

Re: [PATCH 1/2] crypto: echainiv - Remove unused alg/spawn variable

On Tue, Dec 12, 2017 at 07:30:13PM +, Corentin Labbe wrote: > This patch remove two unused variable and some dead "code" using it. > > Fixes: 66008d4230f6 ("crypto: echainiv - Remove AEAD compatibility code") > Signed-off-by: Corentin Labbe Patch applied. Thanks. --

Re: Cgroups v2 thread mode "domain invalid" state

Hi Tejun, On 22 December 2017 at 01:15, Tejun Heo wrote: > Hello, > > On Wed, Dec 20, 2017 at 09:32:04PM +0100, Michael Kerrisk (man-pages) wrote: >> I did find the July 2017 mail thread >> "[PATCH 5/6] cgroup: implement cgroup v2 thread support" >>

[PATCH 4.14 131/159] ASoC: img-parallel-out: Add pm_runtime_get/put to set_fmt callback

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ed Blake [ Upstream commit c70458890ff15d858bd347fa9f563818bcd6e457 ] Add pm_runtime_get_sync and pm_runtime_put calls to set_fmt callback function. This fixes a bus

Re: [PATCH 2/2] sched/wait: add wait_event_idle_exclusive_lifo()

On Fri, Dec 22, 2017 at 02:11:04PM +1100, NeilBrown wrote: > wait_event_*_exclusive() adds new waiters to the end of the > quest, while non-exclusive wait_event adds to the head. > > This ensures that a wake_up will wake all non-exclusive > waiters and at most one exclusive wait, but it means

Re: [PATCH] crypto: chcr: select CRYPTO_GF128MUL

On Tue, Dec 05, 2017 at 11:10:26AM +0100, Arnd Bergmann wrote: > Without the gf128mul library support, we can run into a link > error: > > drivers/crypto/chelsio/chcr_algo.o: In function `chcr_update_tweak': > chcr_algo.c:(.text+0x7e0): undefined reference to `gf128mul_x8_ble' > > This adds a

Re: [PATCH] crypto: chacha20poly1305 - validate the digest size

On Mon, Dec 11, 2017 at 12:15:17PM -0800, Eric Biggers wrote: > From: Eric Biggers > > If the rfc7539 template was instantiated with a hash algorithm with > digest size larger than 16 bytes (POLY1305_DIGEST_SIZE), then the digest > overran the 'tag' buffer in 'struct

Re: [alsa-devel] [PATCH v5 10/15] soundwire: Add sysfs for SoundWire DisCo properties

On Fri, Dec 22, 2017 at 01:56:56PM +0530, Vinod Koul wrote: > On Wed, Dec 13, 2017 at 05:59:22PM +0100, Greg Kroah-Hartman wrote: > > On Wed, Dec 13, 2017 at 10:22:46PM +0530, Vinod Koul wrote: > > > On Wed, Dec 13, 2017 at 05:28:21PM +0100, Greg Kroah-Hartman wrote: > > > > On Wed, Dec 13, 2017

[PATCH 4.4 50/78] isdn: kcapi: avoid uninitialized data

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit af109a2cf6a9a6271fa420ae2d64d72d86c92b7d ] gcc-7 points out that the AVMB1_ADDCARD ioctl results in an unintialized value ending up in the

[PATCH 4.4 49/78] KVM: pci-assign: do not map smm memory slot pages in vt-d page tables

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Herongguang (Stephen)" [ Upstream commit 0292e169b2d9c8377a168778f0b16eadb1f578fd ] or VM memory are not put thus leaked in kvm_iommu_unmap_memslots() when destroy

[PATCH 4.4 45/78] irda: vlsi_ir: fix check for DMA mapping errors

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Khoroshilov [ Upstream commit 6ac3b77a67513ff86b684aa256ea01c0e5b5 ] vlsi_alloc_ring() checks for DMA mapping errors by comparing returned address with zero,

[PATCH 4.4 58/78] rtc: pl031: make interrupt optional

4.4-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

[PATCH 4.4 47/78] netfilter: nf_nat_snmp: Fix panic when snmp_trap_helper fails to register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gao Feng [ Upstream commit 75c689dca98851d65ef5a27e5ce26b625b68751c ] In the commit 93557f53e1fb ("netfilter: nf_conntrack: nf_conntrack snmp helper"), the snmp_helper is

[PATCH 4.4 02/78] cxl: Check if vphb exists before iterating over AFU devices

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vaibhav Jain commit 12841f87b7a8ceb3d54f171660f72a86941bfcb3 upstream. During an eeh a kernel-oops is reported if no vPHB is allocated to the AFU. This happens as

[PATCH 4.4 09/78] sched/core: Add switch_mm_irqs_off() and use it in the scheduler

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit f98db6013c557c216da5038d9c52045be55cd039 upstream. By default, this is the same thing as switch_mm(). x86 will override it as an optimization.

[PATCH 4.4 39/78] r8152: prevent the driver from transmitting packets with carrier off

4.4-stable review patch. If anyone has any objections, please let me know. -- From: hayeswang [ Upstream commit 2f25abe6bac573928a990ccbdac75873add8127e ] The linking status may be changed when autosuspend. And, after autoresume, the driver may try to

  1   2   3   4   5   6   7   8   9   10   >