[PATCH 4.10 080/129] USB: serial: ark3116: fix open error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit b631433b175f1002a31020e09bbfc2e5caecf290 upstream. Fix open error handling which failed to detect errors when reading the MSR and LSR registers,

[PATCH 4.10 080/129] USB: serial: ark3116: fix open error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit b631433b175f1002a31020e09bbfc2e5caecf290 upstream. Fix open error handling which failed to detect errors when reading the MSR and LSR registers, something which could lead

[PATCH 4.10 086/129] USB: serial: sierra: fix bogus alternate-setting assumption

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 16620b483eaf7750413bae472f4363b6b959fcaa upstream. Interface numbers do not change when enabling alternate settings as comment and code in this driver

[PATCH 4.10 088/129] phy: qcom-usb-hs: Add depends on EXTCON

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit 1a09b6a7c10e22c489a8b212dd6862b1fd9674ad upstream. We get the following compile errors if EXTCON is enabled as a module but this driver is

[PATCH 4.10 086/129] USB: serial: sierra: fix bogus alternate-setting assumption

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 16620b483eaf7750413bae472f4363b6b959fcaa upstream. Interface numbers do not change when enabling alternate settings as comment and code in this driver suggested. Remove

[PATCH 4.10 088/129] phy: qcom-usb-hs: Add depends on EXTCON

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit 1a09b6a7c10e22c489a8b212dd6862b1fd9674ad upstream. We get the following compile errors if EXTCON is enabled as a module but this driver is builtin: drivers/built-in.o: In

Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf

On Thu, 11 May 2017 15:27:53 +0200 Gerd Hoffmann wrote: > Hi, > > > While read the framebuffer region we have to tell the vendor driver which > > framebuffer we want to read? There are two framebuffers now in KVMGT that > > is primary and cursor. > > There are two methods

Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf

On Thu, 11 May 2017 15:27:53 +0200 Gerd Hoffmann wrote: > Hi, > > > While read the framebuffer region we have to tell the vendor driver which > > framebuffer we want to read? There are two framebuffers now in KVMGT that > > is primary and cursor. > > There are two methods to implement this:

[PATCH 4.10 089/129] serial: 8250_omap: Fix probe and remove for PM runtime

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 4e0f5cc65098ea32a1e77baae74215b9bd5276b1 upstream. Otherwise the interconnect related code implementing PM runtime will produce these errors on a failed

[PATCH 4.10 085/129] USB: serial: io_edgeport: fix descriptor error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 3c0e25d883d06a1fbd1ad35257e8abaa57befb37 upstream. Make sure to detect short control-message transfers and log an error when reading incomplete

[PATCH 4.10 089/129] serial: 8250_omap: Fix probe and remove for PM runtime

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 4e0f5cc65098ea32a1e77baae74215b9bd5276b1 upstream. Otherwise the interconnect related code implementing PM runtime will produce these errors on a failed probe: omap_uart

[PATCH 4.10 085/129] USB: serial: io_edgeport: fix descriptor error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 3c0e25d883d06a1fbd1ad35257e8abaa57befb37 upstream. Make sure to detect short control-message transfers and log an error when reading incomplete manufacturer and boot

Re: [PATCH] Partially Revert "of: fix sparse warnings in fdt, irq, reserved mem, and resolver code"

On Thu, May 11, 2017 at 5:30 PM, Rob Herring wrote: > A change to function pointers that was meant to address a sparse warning > turned out to cause hundreds of new gcc-7 warnings: > > include/linux/of_irq.h:11:13: error: type qualifiers ignored on function > return type

Re: [PATCH] Partially Revert "of: fix sparse warnings in fdt, irq, reserved mem, and resolver code"

On Thu, May 11, 2017 at 5:30 PM, Rob Herring wrote: > A change to function pointers that was meant to address a sparse warning > turned out to cause hundreds of new gcc-7 warnings: > > include/linux/of_irq.h:11:13: error: type qualifiers ignored on function > return type

[PATCH 4.10 082/129] USB: serial: quatech2: fix control-message error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 8c34cb8ddfe808d557b51da983ff10c02793beb2 upstream. Make sure to detect short control-message transfers when fetching modem and line state in open and

[PATCH 4.10 072/129] usb: host: ohci-exynos: Decrese node refcount on exynos_ehci_get_phy() error paths

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 68bd6fc3cfa98ef253e17307ccafd8ef907b5556 upstream. Returning from for_each_available_child_of_node() loop requires cleaning up node refcount.

[PATCH 4.10 082/129] USB: serial: quatech2: fix control-message error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 8c34cb8ddfe808d557b51da983ff10c02793beb2 upstream. Make sure to detect short control-message transfers when fetching modem and line state in open and when retrieving

[PATCH 4.10 072/129] usb: host: ohci-exynos: Decrese node refcount on exynos_ehci_get_phy() error paths

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 68bd6fc3cfa98ef253e17307ccafd8ef907b5556 upstream. Returning from for_each_available_child_of_node() loop requires cleaning up node refcount. Error paths lacked it

[PATCH 4.10 094/129] scsi: scsi_dh_emc: return success in clariion_std_inquiry()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 4d7d39a18b8b81511f0b893b7d2203790bf8a58b upstream. We accidentally return an uninitialized variable on success. Fixes: b6ff1b14cdf4 ("[SCSI]

[PATCH 4.10 094/129] scsi: scsi_dh_emc: return success in clariion_std_inquiry()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 4d7d39a18b8b81511f0b893b7d2203790bf8a58b upstream. We accidentally return an uninitialized variable on success. Fixes: b6ff1b14cdf4 ("[SCSI] scsi_dh: Update EMC

[PATCH 4.10 081/129] USB: serial: ftdi_sio: fix latency-timer error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit e3e574ad85a208cb179f33720bb5f12b453de33c upstream. Make sure to detect short responses when reading the latency timer to avoid using stale buffer data.

[PATCH 4.10 081/129] USB: serial: ftdi_sio: fix latency-timer error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit e3e574ad85a208cb179f33720bb5f12b453de33c upstream. Make sure to detect short responses when reading the latency timer to avoid using stale buffer data. Note that no heap

[PATCH 4.10 093/129] scsi: mac_scsi: Fix MAC_SCSI=m option when SCSI=m

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 2559a1ef688f933835912c731bed2254146a9b04 upstream. The mac_scsi driver still gets disabled when SCSI=m. This should have been fixed back when I

[PATCH 4.10 093/129] scsi: mac_scsi: Fix MAC_SCSI=m option when SCSI=m

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 2559a1ef688f933835912c731bed2254146a9b04 upstream. The mac_scsi driver still gets disabled when SCSI=m. This should have been fixed back when I enabled the tristate but I

[PATCH 4.10 092/129] scsi: qla2xxx: Fix crash in qla2xxx_eh_abort on bad ptr

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Bill Kuzeja commit 5f7c2beef819d9ea2d1b814edf6f5981420e9cf8 upstream. After a Qlogic card breaks when initializing (test case), the system can crash in

[PATCH 4.10 092/129] scsi: qla2xxx: Fix crash in qla2xxx_eh_abort on bad ptr

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Bill Kuzeja commit 5f7c2beef819d9ea2d1b814edf6f5981420e9cf8 upstream. After a Qlogic card breaks when initializing (test case), the system can crash in qla2xxx_eh_abort if processing anything

[PATCH 4.10 098/129] brcmfmac: Make skb header writable before use

4.10-stable review patch. If anyone has any objections, please let me know. -- From: James Hughes commit 9cc4b7cb86cbcc6330a3faa8cd65268cd2d3c227 upstream. The driver was making changes to the skb_header without ensuring it was writable (i.e.

[PATCH 4.10 098/129] brcmfmac: Make skb header writable before use

4.10-stable review patch. If anyone has any objections, please let me know. -- From: James Hughes commit 9cc4b7cb86cbcc6330a3faa8cd65268cd2d3c227 upstream. The driver was making changes to the skb_header without ensuring it was writable (i.e. uncloned). This patch also

Re: [PATCHv2] arm64/cpufeature: don't use mutex in bringup path

On Thu, May 11, 2017 at 04:37:20PM +0100, Mark Rutland wrote: > On Thu, May 11, 2017 at 04:15:38PM +0100, Suzuki K Poulose wrote: > > On 11/05/17 16:01, Mark Rutland wrote: > > >+static inline bool cpus_have_const_cap(int num) > > >+{ > > >+ if (static_branch_likely(_const_caps_ready)) > > >+

Re: [PATCHv2] arm64/cpufeature: don't use mutex in bringup path

On Thu, May 11, 2017 at 04:37:20PM +0100, Mark Rutland wrote: > On Thu, May 11, 2017 at 04:15:38PM +0100, Suzuki K Poulose wrote: > > On 11/05/17 16:01, Mark Rutland wrote: > > >+static inline bool cpus_have_const_cap(int num) > > >+{ > > >+ if (static_branch_likely(_const_caps_ready)) > > >+

[PATCH 4.10 095/129] scsi: smartpqi: fix time handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit ed10858eadd4988260c6bc7d75fc25176342b5a7 upstream. When we have turned off RTC support, the smartpqi driver fails to build: ERROR: "rtc_time64_to_tm"

[PATCH 4.10 095/129] scsi: smartpqi: fix time handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit ed10858eadd4988260c6bc7d75fc25176342b5a7 upstream. When we have turned off RTC support, the smartpqi driver fails to build: ERROR: "rtc_time64_to_tm"

[PATCH 4.10 090/129] scsi: qedi: Fix possible memory leak in qedi_iscsi_update_conn()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit 8b9b22ba75907dcced88c815a5427ec0b4298aec upstream. 'conn_info' is malloced in qedi_iscsi_update_conn() and should be freed before leaving from the

[PATCH 4.10 090/129] scsi: qedi: Fix possible memory leak in qedi_iscsi_update_conn()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit 8b9b22ba75907dcced88c815a5427ec0b4298aec upstream. 'conn_info' is malloced in qedi_iscsi_update_conn() and should be freed before leaving from the error handling cases,

[PATCH 4.10 073/129] usb: chipidea: Only read/write OTGSC from one place

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit f60f8ccd54e03c1afafb2b20ceb029a0eaf7a134 upstream. With the id and vbus detection done via extcon we need to make sure we poll the status of OTGSC

[PATCH 4.10 073/129] usb: chipidea: Only read/write OTGSC from one place

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit f60f8ccd54e03c1afafb2b20ceb029a0eaf7a134 upstream. With the id and vbus detection done via extcon we need to make sure we poll the status of OTGSC properly by considering

[PATCH 4.10 096/129] MIPS: R2-on-R6 MULTU/MADDU/MSUBU emulation bugfix

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Leonid Yegoshin commit d65e5677ad5b3a49c43f60ec07644dc1f87bbd2e upstream. MIPS instructions MULTU, MADDU and MSUBU emulation requires registers HI/LO to be

[PATCH 4.10 096/129] MIPS: R2-on-R6 MULTU/MADDU/MSUBU emulation bugfix

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Leonid Yegoshin commit d65e5677ad5b3a49c43f60ec07644dc1f87bbd2e upstream. MIPS instructions MULTU, MADDU and MSUBU emulation requires registers HI/LO to be converted to signed 32bits before

[PATCH 4.10 100/129] staging: wlan-ng: add missing byte order conversion

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Igor Pylypiv commit 2c474b8579e9b67ff72b2bcefce9f53c7f4469d4 upstream. Conversion macros le16_to_cpu was removed and that caused new sparse warning sparse output:

[PATCH 4.10 100/129] staging: wlan-ng: add missing byte order conversion

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Igor Pylypiv commit 2c474b8579e9b67ff72b2bcefce9f53c7f4469d4 upstream. Conversion macros le16_to_cpu was removed and that caused new sparse warning sparse output:

Re: [PATCH] efi: remove duplicate 'const' specifiers

Arnd Bergmann wrote: > gcc-7 shows a harmless warning: > > drivers/firmware/efi/libstub/secureboot.c:19:27: error: duplicate 'const' > declaration specifier [-Werror=duplicate-decl-specifier] > static const efi_char16_t const efi_SecureBoot_name[] = { >

Re: [PATCH] efi: remove duplicate 'const' specifiers

Arnd Bergmann wrote: > gcc-7 shows a harmless warning: > > drivers/firmware/efi/libstub/secureboot.c:19:27: error: duplicate 'const' > declaration specifier [-Werror=duplicate-decl-specifier] > static const efi_char16_t const efi_SecureBoot_name[] = { >

Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration

On Tue, 2 May 2017, Luiz Capitulino wrote: > Ah, OK. Got this now. I'll give this patch a try. But I think we want > to hear from Christoph (who worked on reducing the vmstat interruptions > in the past). A bit confused by this one. The vmstat worker is already disabled if there are no updates.

Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration

On Tue, 2 May 2017, Luiz Capitulino wrote: > Ah, OK. Got this now. I'll give this patch a try. But I think we want > to hear from Christoph (who worked on reducing the vmstat interruptions > in the past). A bit confused by this one. The vmstat worker is already disabled if there are no updates.

Re: [PATCH] filesystem-dax: fix broken __dax_zero_page_range() conversion

On Wed, May 10, 2017 at 07:49:47PM -0700, Dan Williams wrote: > The conversion of __dax_zero_page_range() to 'struct dax_operations' > caused it to frequently fail. The mistake was treating the @size > parameter as a dax mapping length rather than just a length of the > clear_pmem() operation. The

Re: [PATCHv2] arm64/cpufeature: don't use mutex in bringup path

On Thu, May 11, 2017 at 04:15:38PM +0100, Suzuki K Poulose wrote: > On 11/05/17 16:01, Mark Rutland wrote: > >+static inline bool cpus_have_const_cap(int num) > >+{ > >+if (static_branch_likely(_const_caps_ready)) > >+return __cpus_have_const_cap(num); > >+else > >+

Re: [PATCH] filesystem-dax: fix broken __dax_zero_page_range() conversion

On Wed, May 10, 2017 at 07:49:47PM -0700, Dan Williams wrote: > The conversion of __dax_zero_page_range() to 'struct dax_operations' > caused it to frequently fail. The mistake was treating the @size > parameter as a dax mapping length rather than just a length of the > clear_pmem() operation. The

Re: [PATCHv2] arm64/cpufeature: don't use mutex in bringup path

On Thu, May 11, 2017 at 04:15:38PM +0100, Suzuki K Poulose wrote: > On 11/05/17 16:01, Mark Rutland wrote: > >+static inline bool cpus_have_const_cap(int num) > >+{ > >+if (static_branch_likely(_const_caps_ready)) > >+return __cpus_have_const_cap(num); > >+else > >+

Re: [PATCH 00/10] fujitsu-laptop: use device-specific data instead of module-wide globals

On Thu, May 11, 2017 at 04:37:30PM +0200, Rafael Wysocki wrote: > On Thursday, May 11, 2017 03:52:11 PM Michał Kępień wrote: > > > On Tuesday, May 09, 2017 09:47:34 AM Darren Hart wrote: > > > > On Tue, May 09, 2017 at 11:35:24AM +0200, Michał Kępień wrote: > > > > > > On Sat, May 06, 2017 at

Re: [PATCH 00/10] fujitsu-laptop: use device-specific data instead of module-wide globals

On Thu, May 11, 2017 at 04:37:30PM +0200, Rafael Wysocki wrote: > On Thursday, May 11, 2017 03:52:11 PM Michał Kępień wrote: > > > On Tuesday, May 09, 2017 09:47:34 AM Darren Hart wrote: > > > > On Tue, May 09, 2017 at 11:35:24AM +0200, Michał Kępień wrote: > > > > > > On Sat, May 06, 2017 at

Re: [PATCH] smp_call_function: use inline helpers instead of macros

On 11/05/2017 17:13, Arnd Bergmann wrote: > A new caller of smp_call_function() passes a local variable as the 'wait' > argument, and that variable is otherwise unused, so we get a warning > in non-SMP configurations: > > virt/kvm/kvm_main.c: In function 'kvm_make_all_cpus_request': >

Re: [patch 3/3] MM: allow per-cpu vmstat_worker configuration

On Wed, May 10, 2017 at 11:34:26AM -0400, Rik van Riel wrote: > On Wed, 2017-05-03 at 15:40 -0300, Marcelo Tosatti wrote: > > Following the reasoning on the last patch in the series, > > this patch allows configuration of the per-CPU vmstat worker: > > it allows the user to disable the per-CPU

Re: [PATCH] smp_call_function: use inline helpers instead of macros

On 11/05/2017 17:13, Arnd Bergmann wrote: > A new caller of smp_call_function() passes a local variable as the 'wait' > argument, and that variable is otherwise unused, so we get a warning > in non-SMP configurations: > > virt/kvm/kvm_main.c: In function 'kvm_make_all_cpus_request': >

Re: [patch 3/3] MM: allow per-cpu vmstat_worker configuration

On Wed, May 10, 2017 at 11:34:26AM -0400, Rik van Riel wrote: > On Wed, 2017-05-03 at 15:40 -0300, Marcelo Tosatti wrote: > > Following the reasoning on the last patch in the series, > > this patch allows configuration of the per-CPU vmstat worker: > > it allows the user to disable the per-CPU

[PATCH] Partially Revert "of: fix sparse warnings in fdt, irq, reserved mem, and resolver code"

A change to function pointers that was meant to address a sparse warning turned out to cause hundreds of new gcc-7 warnings: include/linux/of_irq.h:11:13: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] drivers/of/of_reserved_mem.c: In function

[PATCH] Partially Revert "of: fix sparse warnings in fdt, irq, reserved mem, and resolver code"

A change to function pointers that was meant to address a sparse warning turned out to cause hundreds of new gcc-7 warnings: include/linux/of_irq.h:11:13: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] drivers/of/of_reserved_mem.c: In function

[PATCH] block: xen-blkback: add null check to avoid null pointer dereference

Add null check before calling xen_blkif_put() to avoid potential null pointer dereference. Addresses-Coverity-ID: 1350942 Cc: Juergen Gross Signed-off-by: Gustavo A. R. Silva --- drivers/block/xen-blkback/xenbus.c | 8 +--- 1 file changed, 5

[PATCH] block: xen-blkback: add null check to avoid null pointer dereference

Add null check before calling xen_blkif_put() to avoid potential null pointer dereference. Addresses-Coverity-ID: 1350942 Cc: Juergen Gross Signed-off-by: Gustavo A. R. Silva --- drivers/block/xen-blkback/xenbus.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git

Re: [PATCH 2/3] livepatch/rcu: Warn when system consistency is broken in RCU code

On Thu, May 11, 2017 at 03:52:46PM +0200, Petr Mladek wrote: > Anyway, a crazy idea is to use the livepatch consistency model instead > of RCU to protect the function stack. The model makes sure that all > tasks, including the idle ones, were not running any patched function > (and their ftrace

Re: [PATCH 2/3] livepatch/rcu: Warn when system consistency is broken in RCU code

On Thu, May 11, 2017 at 03:52:46PM +0200, Petr Mladek wrote: > Anyway, a crazy idea is to use the livepatch consistency model instead > of RCU to protect the function stack. The model makes sure that all > tasks, including the idle ones, were not running any patched function > (and their ftrace

Re: [PATCH] pinctrl: use non-devm kmalloc versions for free functions

Hi Linus, On 11/05/17 15:01, Linus Walleij wrote: > On Thu, May 4, 2017 at 1:57 AM, Andre Przywara wrote: > >> When a pinctrl driver gets interrupted during its probe process >> (returning -EPROBE_DEFER), the devres system cleans up all allocated >> resources. During

Re: [PATCH] pinctrl: use non-devm kmalloc versions for free functions

Hi Linus, On 11/05/17 15:01, Linus Walleij wrote: > On Thu, May 4, 2017 at 1:57 AM, Andre Przywara wrote: > >> When a pinctrl driver gets interrupted during its probe process >> (returning -EPROBE_DEFER), the devres system cleans up all allocated >> resources. During this process it calls

[PATCH 4.10 105/129] macsec: dynamically allocate space for sglist

4.10-stable review patch. If anyone has any objections, please let me know. -- From: "Jason A. Donenfeld" [ Upstream commit 5294b83086cc1c35b4efeca03644cf9d12282e5b ] We call skb_cow_data, which is good anyway to ensure we can actually modify the skb as such

[PATCH 4.10 105/129] macsec: dynamically allocate space for sglist

4.10-stable review patch. If anyone has any objections, please let me know. -- From: "Jason A. Donenfeld" [ Upstream commit 5294b83086cc1c35b4efeca03644cf9d12282e5b ] We call skb_cow_data, which is good anyway to ensure we can actually modify the skb as such (another error

[PATCH 4.10 103/129] ALSA: hda - Fix deadlock of controller device lock at unbinding

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit ab949d519601880fd46e8bc1445d6a453bf2dc09 upstream. Imre Deak reported a deadlock of HD-audio driver at unbinding while it's still in probing. Since we

[PATCH 4.10 103/129] ALSA: hda - Fix deadlock of controller device lock at unbinding

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit ab949d519601880fd46e8bc1445d6a453bf2dc09 upstream. Imre Deak reported a deadlock of HD-audio driver at unbinding while it's still in probing. Since we probe the codecs

[PATCH 4.10 102/129] staging: lustre: ptlrpc: avoid warning on missing return

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 74e3bb75315ce62a4567f2871276bab32802e8b4 upstream. The newly added function triggers a harmless warning:

[PATCH 4.10 102/129] staging: lustre: ptlrpc: avoid warning on missing return

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 74e3bb75315ce62a4567f2871276bab32802e8b4 upstream. The newly added function triggers a harmless warning: drivers/staging/lustre/lustre/ptlrpc/pack_generic.c: In function

[PATCH 4.10 107/129] net: adjust skb->truesize in ___pskb_trim()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit c21b48cc1bbf2f5af3ef54ada559f7fadf8b508b ] Andrey found a way to trigger the WARN_ON_ONCE(delta < len) in skb_try_coalesce() using

[PATCH 4.10 107/129] net: adjust skb->truesize in ___pskb_trim()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit c21b48cc1bbf2f5af3ef54ada559f7fadf8b508b ] Andrey found a way to trigger the WARN_ON_ONCE(delta < len) in skb_try_coalesce() using syzkaller and a filter

[PATCH 4.10 106/129] tcp: do not underestimate skb->truesize in tcp_trim_head()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7162fb242cb8322beb558828fd26b33c3e9fc805 ] Andrey found a way to trigger the WARN_ON_ONCE(delta < len) in skb_try_coalesce() using

[PATCH 4.10 106/129] tcp: do not underestimate skb->truesize in tcp_trim_head()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7162fb242cb8322beb558828fd26b33c3e9fc805 ] Andrey found a way to trigger the WARN_ON_ONCE(delta < len) in skb_try_coalesce() using syzkaller and a filter

[PATCH 4.10 074/129] usb: chipidea: Handle extcon events properly

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit a89b94b53371bbfa582787c2fa3378000ea4263d upstream. We're currently emulating the vbus and id interrupts in the OTGSC read API, but we also need to

[PATCH 4.10 110/129] bpf: enhance verifier to understand stack pointer arithmetic

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ Upstream commit 332270fdc8b6fba07d059a9ad44df9e1a2ad4529 ] llvm 4.0 and above generates the code like below: 440: (b7) r1 = 15 441: (05) goto pc+73 515:

[PATCH 4.10 074/129] usb: chipidea: Handle extcon events properly

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit a89b94b53371bbfa582787c2fa3378000ea4263d upstream. We're currently emulating the vbus and id interrupts in the OTGSC read API, but we also need to make sure that if we're

[PATCH 4.10 110/129] bpf: enhance verifier to understand stack pointer arithmetic

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ Upstream commit 332270fdc8b6fba07d059a9ad44df9e1a2ad4529 ] llvm 4.0 and above generates the code like below: 440: (b7) r1 = 15 441: (05) goto pc+73 515: (79) r6 = *(u64

[PATCH 4.10 075/129] USB: serial: keyspan_pda: fix receive sanity checks

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit c528fcb116e61afc379a2e0a0f70906b937f1e2c upstream. Make sure to check for short transfers before parsing the receive buffer to avoid acting on stale

[PATCH 4.10 075/129] USB: serial: keyspan_pda: fix receive sanity checks

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit c528fcb116e61afc379a2e0a0f70906b937f1e2c upstream. Make sure to check for short transfers before parsing the receive buffer to avoid acting on stale data. Fixes:

Re: [PATCH] omapfb: Use devm_kcalloc() in vrfb_probe()

On Thursday, May 11, 2017 04:27:19 PM Bartlomiej Zolnierkiewicz wrote: > > @@ -358,11 +358,7 @@ static int __init vrfb_probe(struct platform_device > > *pdev) > > return PTR_ERR(vrfb_base); > > > > num_ctxs = pdev->num_resources - 1; > > - > > - ctxs = devm_kzalloc(>dev, > >

[PATCH 4.10 111/129] bpf, arm64: fix jit branch offset related to ldimm64

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit ddc665a4bb4b728b4e6ecec8db1b64efa9184b9c ] When the instruction right before the branch destination is a 64 bit load immediate, we

Re: [PATCH] omapfb: Use devm_kcalloc() in vrfb_probe()

On Thursday, May 11, 2017 04:27:19 PM Bartlomiej Zolnierkiewicz wrote: > > @@ -358,11 +358,7 @@ static int __init vrfb_probe(struct platform_device > > *pdev) > > return PTR_ERR(vrfb_base); > > > > num_ctxs = pdev->num_resources - 1; > > - > > - ctxs = devm_kzalloc(>dev, > >

[PATCH 4.10 111/129] bpf, arm64: fix jit branch offset related to ldimm64

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit ddc665a4bb4b728b4e6ecec8db1b64efa9184b9c ] When the instruction right before the branch destination is a 64 bit load immediate, we currently calculate the

[PATCH 4.10 079/129] USB: serial: ti_usb_3410_5052: fix control-message error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 39712e8bfa8d3aa6ce1e60fc9d62c9b076c17a30 upstream. Make sure to detect and return an error on zero-length control-message transfers when reading from the

[PATCH 4.10 079/129] USB: serial: ti_usb_3410_5052: fix control-message error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 39712e8bfa8d3aa6ce1e60fc9d62c9b076c17a30 upstream. Make sure to detect and return an error on zero-length control-message transfers when reading from the device. This

[PATCH 4.10 077/129] USB: serial: ssu100: fix control-message error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 1eac5c244f705182d1552a53e2f74e2775ed95d6 upstream. Make sure to detect short control-message transfers rather than continue with zero-initialised data

[PATCH 4.10 077/129] USB: serial: ssu100: fix control-message error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 1eac5c244f705182d1552a53e2f74e2775ed95d6 upstream. Make sure to detect short control-message transfers rather than continue with zero-initialised data when retrieving

[PATCH 4.10 113/129] net: ipv6: Do not duplicate DAD on link up

4.10-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 6d717134a1a6e1b34a7d0d70e953037bc2642046 ] Andrey reported a warning triggered by the rcu code: [ cut here ]

[PATCH 4.10 113/129] net: ipv6: Do not duplicate DAD on link up

4.10-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 6d717134a1a6e1b34a7d0d70e953037bc2642046 ] Andrey reported a warning triggered by the rcu code: [ cut here ] WARNING: CPU: 1 PID: 5911

[PATCH 4.10 123/129] openvswitch: Set internal device max mtu to ETH_MAX_MTU.

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jarno Rajahalme [ Upstream commit 425df17ce3a26d98f76e2b6b0af2acf4aeb0b026 ] Commit 91572088e3fd ("net: use core MTU range checking in core net infra") changed the openvswitch

[PATCH 4.10 123/129] openvswitch: Set internal device max mtu to ETH_MAX_MTU.

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jarno Rajahalme [ Upstream commit 425df17ce3a26d98f76e2b6b0af2acf4aeb0b026 ] Commit 91572088e3fd ("net: use core MTU range checking in core net infra") changed the openvswitch internal

[PATCH 4.10 125/129] xen: Revert commits da72ff5bfcb0 and 72a9b186292d

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Boris Ostrovsky commit 84d582d236dc1f9085e741affc72e9ba061a67c2 upstream. Recent discussion (http://marc.info/?l=xen-devel=149192184523741) established that commit

[PATCH 4.10 125/129] xen: Revert commits da72ff5bfcb0 and 72a9b186292d

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Boris Ostrovsky commit 84d582d236dc1f9085e741affc72e9ba061a67c2 upstream. Recent discussion (http://marc.info/?l=xen-devel=149192184523741) established that commit 72a9b186292d ("xen: Remove

[PATCH RT v2] futex/rtmutex: Cure RT double blocking issue

RT has a problem when the wait on a futex/rtmutex got interrupted by a timeout or a signal. task->pi_blocked_on is still set when returning from rt_mutex_wait_proxy_lock(). The task must acquire the hash bucket lock after this. If the hash bucket lock is contended then the

[PATCH RT v2] futex/rtmutex: Cure RT double blocking issue

RT has a problem when the wait on a futex/rtmutex got interrupted by a timeout or a signal. task->pi_blocked_on is still set when returning from rt_mutex_wait_proxy_lock(). The task must acquire the hash bucket lock after this. If the hash bucket lock is contended then the

[PATCH 4.10 127/129] drm: mxsfb: drm_dev_alloc() returns error pointers

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit e89e50ac35d9126907a436dabe70f9a8311b9981 upstream. We should be checking for IS_ERR() instead of NULL because drm_dev_alloc() returns error

[PATCH 4.10 127/129] drm: mxsfb: drm_dev_alloc() returns error pointers

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit e89e50ac35d9126907a436dabe70f9a8311b9981 upstream. We should be checking for IS_ERR() instead of NULL because drm_dev_alloc() returns error pointers. Fixes: 45d59d704080

[PATCH 4.10 119/129] ipv6: reorder ip6_route_dev_notifier after ipv6_dev_notf

4.10-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 242d3a49a2a1a71d8eb9f953db1bcaa9d698ce00 ] For each netns (except init_net), we initialize its null entry in 3 places: 1) The template

[PATCH 4.10 119/129] ipv6: reorder ip6_route_dev_notifier after ipv6_dev_notf

4.10-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 242d3a49a2a1a71d8eb9f953db1bcaa9d698ce00 ] For each netns (except init_net), we initialize its null entry in 3 places: 1) The template itself, as we use

[PATCH 4.10 118/129] ipv6: initialize route null entry in addrconf_init()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 2f460933f58eee3393aba64f0f6d14acb08d1724 ] Andrey reported a crash on init_net.ipv6.ip6_null_entry->rt6i_idev since it is always NULL.

[PATCH 4.10 118/129] ipv6: initialize route null entry in addrconf_init()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 2f460933f58eee3393aba64f0f6d14acb08d1724 ] Andrey reported a crash on init_net.ipv6.ip6_null_entry->rt6i_idev since it is always NULL. This is clearly wrong, we

<    5   6   7   8   9   10   11   12   13   14   >