[PATCH 3.16 086/217] sg: fix dxferp in from_to case

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Douglas Gilbert commit 5ecee0a3ee8d74b6950cb41e8989b0c2174568d4 upstream. One of the strange things that the original sg driver did was let the user provide both a data-out buffer (it

[PATCH 3.16 089/217] xtensa: ISS: don't hang if stdin EOF is reached

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit 362014c8d9d51d504c167c44ac280169457732be upstream. Simulator stdin may be connected to a file, when its end is reached kernel hangs in infinite loop inside rs_poll,

[PATCH 3.16 091/217] xen kconfig: don't "select INPUT_XEN_KBDDEV_FRONTEND"

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 13aa38e291bdd4e4018f40dd2f75e464814dcbf3 upstream. The Xen framebuffer driver selects the xen keyboard driver, so the latter will be built-in if

[PATCH 3.16 091/217] xen kconfig: don't "select INPUT_XEN_KBDDEV_FRONTEND"

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 13aa38e291bdd4e4018f40dd2f75e464814dcbf3 upstream. The Xen framebuffer driver selects the xen keyboard driver, so the latter will be built-in if XEN_FBDEV_FRONTEND=y.

[PATCH 3.16 098/217] s390/pci: enforce fmb page boundary rule

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 80c544ded25ac14d7cc3e555abb8ed2c2da99b84 upstream. The function measurement block must not cross a page boundary. Ensure that by raising the

[PATCH 3.16 098/217] s390/pci: enforce fmb page boundary rule

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 80c544ded25ac14d7cc3e555abb8ed2c2da99b84 upstream. The function measurement block must not cross a page boundary. Ensure that by raising the alignment requirement to the

[PATCH 3.16 067/217] ipvs: correct initial offset of Call-ID header search in SIP persistence engine

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Marco Angaroni commit 7617a24f83b5d67f4dab1844956be1cebc44aec8 upstream. The IPVS SIP persistence engine is not able to parse the SIP header "Call-ID" when such

[PATCH 3.16 067/217] ipvs: correct initial offset of Call-ID header search in SIP persistence engine

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Marco Angaroni commit 7617a24f83b5d67f4dab1844956be1cebc44aec8 upstream. The IPVS SIP persistence engine is not able to parse the SIP header "Call-ID" when such header is inserted in the

[PATCH 3.16 044/217] clk: versatile: sp810: support reentrance

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit ec7957a6aa0aaf981fb8356dc47a2cdd01cde03c upstream. Despite care take to allocate clocks state containers the SP810 driver actually just supports

[PATCH 3.16 045/217] md/raid5: Compare apples to apples (or sectors to sectors)

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Jes Sorensen commit e7597e69dec59b65c5525db1626b9d34afdfa678 upstream. 'max_discard_sectors' is in sectors, while 'stripe' is in bytes. This fixes the problem where

[PATCH 3.16 060/217] mtip32xx: Remove unwanted code from taskfile error handler

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Asai Thambi SP commit e35b94738a2f7caa12017f69ef385cb6b8028965 upstream. Remove setting and clearing MTIP_PF_EH_ACTIVE_BIT flag in mtip_handle_tfe() as they are

[PATCH 3.16 041/217] mac80211: fix memory leak

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee commit ea32f065bd3e3e09f0bcb3042f1664caf6b3e233 upstream. On error we jumped to the error label and returned the error code but we missed releasing

[PATCH 3.16 045/217] md/raid5: Compare apples to apples (or sectors to sectors)

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Jes Sorensen commit e7597e69dec59b65c5525db1626b9d34afdfa678 upstream. 'max_discard_sectors' is in sectors, while 'stripe' is in bytes. This fixes the problem where DISCARD would get

[PATCH 3.16 060/217] mtip32xx: Remove unwanted code from taskfile error handler

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Asai Thambi SP commit e35b94738a2f7caa12017f69ef385cb6b8028965 upstream. Remove setting and clearing MTIP_PF_EH_ACTIVE_BIT flag in mtip_handle_tfe() as they are redundant. Also avoid waking

[PATCH 3.16 041/217] mac80211: fix memory leak

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee commit ea32f065bd3e3e09f0bcb3042f1664caf6b3e233 upstream. On error we jumped to the error label and returned the error code but we missed releasing sinfo. Fixes: 5fe74014172d

[PATCH 3.16 044/217] clk: versatile: sp810: support reentrance

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit ec7957a6aa0aaf981fb8356dc47a2cdd01cde03c upstream. Despite care take to allocate clocks state containers the SP810 driver actually just supports creating one instance:

[PATCH 3.16 087/217] jbd2: fix FS corruption possibility in jbd2_journal_destroy() on umount path

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: OGAWA Hirofumi commit c0a2ad9b50dd80eeccd73d9ff962234590d5ec93 upstream. On umount path, jbd2_journal_destroy() writes latest transaction ID (->j_tail_sequence)

[PATCH 3.16 103/217] ath9k: fix buffer overrun for ar9287

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 83d6f1f15f8cce844b0a131cbc63e444620e48b5 upstream. Code that was added back in 2.6.38 has an obvious overflow when accessing a static array, and at the

[PATCH 3.16 087/217] jbd2: fix FS corruption possibility in jbd2_journal_destroy() on umount path

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: OGAWA Hirofumi commit c0a2ad9b50dd80eeccd73d9ff962234590d5ec93 upstream. On umount path, jbd2_journal_destroy() writes latest transaction ID (->j_tail_sequence) to be used at next mount. The

[PATCH 3.16 103/217] ath9k: fix buffer overrun for ar9287

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 83d6f1f15f8cce844b0a131cbc63e444620e48b5 upstream. Code that was added back in 2.6.38 has an obvious overflow when accessing a static array, and at the time it was added

[PATCH 3.16 076/217] perf/x86/intel: Fix PEBS data source interpretation on Nehalem/Westmere

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Andi Kleen commit e17dc65328057c00db7e1bfea249c8771a78b30b upstream. Jiri reported some time ago that some entries in the PEBS data source table in perf do not agree

[PATCH 3.16 076/217] perf/x86/intel: Fix PEBS data source interpretation on Nehalem/Westmere

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Andi Kleen commit e17dc65328057c00db7e1bfea249c8771a78b30b upstream. Jiri reported some time ago that some entries in the PEBS data source table in perf do not agree with the SDM. We

Re: Regression in inv_mpu6050: 4.6.0-rc5

On Tue, Apr 26, 2016 at 11:26:51PM +0100, One Thousand Gnomes wrote: > > This now causes us to crash and burn on the ASUS T100TA Baytrail/T > platforms > I believe this regression has already been patched. Check the latest commits in linux-next.

Re: Regression in inv_mpu6050: 4.6.0-rc5

On Tue, Apr 26, 2016 at 11:26:51PM +0100, One Thousand Gnomes wrote: > > This now causes us to crash and burn on the ASUS T100TA Baytrail/T > platforms > I believe this regression has already been patched. Check the latest commits in linux-next.

[PATCH 3.16 018/217] 8250: use callbacks to access UART_DLL/UART_DLM

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Sebastian Frias commit 0b41ce991052022c030fd868e03877700220b090 upstream. Some UART HW has a single register combining UART_DLL/UART_DLM (this was probably forgotten in the

[PATCH 3.16 071/217] perf/core: Fix perf_sched_count derailment

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit 927a5570855836e5d5859a80ce7e91e963545e8f upstream. The error path in perf_event_open() is such that asking for a sampling event

[PATCH 3.16 134/217] KVM: fix spin_lock_init order on x86

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit e9ad4ec8379ad1ba6f68b8ca1c26b50b5ae0a327 upstream. Moving the initialization earlier is needed in 4.6 because kvm_arch_init_vm is now using mmu_lock,

[PATCH 3.16 018/217] 8250: use callbacks to access UART_DLL/UART_DLM

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Sebastian Frias commit 0b41ce991052022c030fd868e03877700220b090 upstream. Some UART HW has a single register combining UART_DLL/UART_DLM (this was probably forgotten in the change that

[PATCH 3.16 071/217] perf/core: Fix perf_sched_count derailment

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit 927a5570855836e5d5859a80ce7e91e963545e8f upstream. The error path in perf_event_open() is such that asking for a sampling event on a PMU that doesn't generate

[PATCH 3.16 134/217] KVM: fix spin_lock_init order on x86

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit e9ad4ec8379ad1ba6f68b8ca1c26b50b5ae0a327 upstream. Moving the initialization earlier is needed in 4.6 because kvm_arch_init_vm is now using mmu_lock, causing lockdep to

[PATCH 1/3] MAINTAINERS: move ARM/NXP LPC32xx record to ARM section

A record of NXP LPC32xx SoC support is lost between LMxx hwmon drivers and lockdep, rename and move it to a place where all other ARM SoC and machines settle. Note, NXP LPC32xx maintenance is actually about SoC series itself, SoC peripherals and a number of machines powered by LPC32xx SoC, so

[PATCH 3.16 080/217] bcache: fix cache_set_flush() NULL pointer dereference on OOM

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Wheeler commit f8b11260a445169989d01df75d35af0f56178f95 upstream. When bch_cache_set_alloc() fails to kzalloc the cache_set, the asyncronous closure handling

[PATCH 0/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC

Roland Stigge added initial support of NXP LPC32xx SoC series and first boards powered by it, but for a while since v3.18-rc1 the SoC support is unmaintained and became stale. Vladimir Zapolskiy and Sylvain Lemieux expressed interest in continuation of NXP LPC32xx maintenance, reflect this in

[PATCH 2/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC

Roland Stigge added initial support of NXP LPC32xx SoC series and first boards powered by it, but for a while since v3.18-rc1 the SoC support is unmaintained and became stale. Vladimir Zapolskiy and Sylvain Lemieux expressed interest in continuation of NXP LPC32xx maintenance, reflect this in

[PATCH 1/3] MAINTAINERS: move ARM/NXP LPC32xx record to ARM section

A record of NXP LPC32xx SoC support is lost between LMxx hwmon drivers and lockdep, rename and move it to a place where all other ARM SoC and machines settle. Note, NXP LPC32xx maintenance is actually about SoC series itself, SoC peripherals and a number of machines powered by LPC32xx SoC, so

[PATCH 3.16 080/217] bcache: fix cache_set_flush() NULL pointer dereference on OOM

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Wheeler commit f8b11260a445169989d01df75d35af0f56178f95 upstream. When bch_cache_set_alloc() fails to kzalloc the cache_set, the asyncronous closure handling tries to dereference a

[PATCH 0/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC

Roland Stigge added initial support of NXP LPC32xx SoC series and first boards powered by it, but for a while since v3.18-rc1 the SoC support is unmaintained and became stale. Vladimir Zapolskiy and Sylvain Lemieux expressed interest in continuation of NXP LPC32xx maintenance, reflect this in

[PATCH 2/3] MAINTAINERS: add new maintainers of NXP LPC32xx SoC

Roland Stigge added initial support of NXP LPC32xx SoC series and first boards powered by it, but for a while since v3.18-rc1 the SoC support is unmaintained and became stale. Vladimir Zapolskiy and Sylvain Lemieux expressed interest in continuation of NXP LPC32xx maintenance, reflect this in

Re: [PATCH v3 0/2] Support ACPI 6.1 update in NFIT Control Region Structure

On Mon, Apr 25, 2016 at 2:34 PM, Toshi Kani wrote: > ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as > follows. > - Valid Fields, Manufacturing Location, and Manufacturing Date >are added from reserved range. No change in the structure size. > - IDs

Re: [PATCH v3 0/2] Support ACPI 6.1 update in NFIT Control Region Structure

On Mon, Apr 25, 2016 at 2:34 PM, Toshi Kani wrote: > ACPI 6.1, Table 5-133, updates NVDIMM Control Region Structure as > follows. > - Valid Fields, Manufacturing Location, and Manufacturing Date >are added from reserved range. No change in the structure size. > - IDs (SPD values) are

[PATCH 3/3] MAINTAINERS: add ARM/NXP LPC32XX SoC specific drivers to the section

The change adds a list of files for maintenance under NXP LPC32xx section, the listed files are NXP LPC32xx SoC series mach files, DTS files of NXP LPC32xx SoC powered boards and NXP LPC32xx SoC peripheral drivers, most of the peripheral driver file names match 'lpc32xx' pattern. Signed-off-by:

[PATCH 3.16 099/217] rtc: vr41xx: Wire up alarm_irq_enable

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit a25f4a95ec3cded34c1250364eba704c5e4fdac4 upstream. drivers/rtc/rtc-vr41xx.c:229: warning: ‘vr41xx_rtc_alarm_irq_enable’ defined but not used

[PATCH 3.16 099/217] rtc: vr41xx: Wire up alarm_irq_enable

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit a25f4a95ec3cded34c1250364eba704c5e4fdac4 upstream. drivers/rtc/rtc-vr41xx.c:229: warning: ‘vr41xx_rtc_alarm_irq_enable’ defined but not used Apparently the

[PATCH 3/3] MAINTAINERS: add ARM/NXP LPC32XX SoC specific drivers to the section

The change adds a list of files for maintenance under NXP LPC32xx section, the listed files are NXP LPC32xx SoC series mach files, DTS files of NXP LPC32xx SoC powered boards and NXP LPC32xx SoC peripheral drivers, most of the peripheral driver file names match 'lpc32xx' pattern. Signed-off-by:

[PATCH 3.16 097/217] fuse: do not use iocb after it may have been freed

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Robert Doebbelin commit 7cabc61e01a0a8b663bd2b4c982aa53048218734 upstream. There's a race in fuse_direct_IO(), whereby is_sync_kiocb() is called on an iocb that could have

[PATCH 3.16 023/217] usb: retry reset if a device times out

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 264904ccc33c604d4b3141bbd33808152dfac45b upstream. Some devices I got show an inability to operate right after power on if they are already connected.

[PATCH 3.16 097/217] fuse: do not use iocb after it may have been freed

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Robert Doebbelin commit 7cabc61e01a0a8b663bd2b4c982aa53048218734 upstream. There's a race in fuse_direct_IO(), whereby is_sync_kiocb() is called on an iocb that could have been freed if async

[PATCH 3.16 023/217] usb: retry reset if a device times out

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 264904ccc33c604d4b3141bbd33808152dfac45b upstream. Some devices I got show an inability to operate right after power on if they are already connected. They are beyond

[PATCH 3.16 024/217] HID: logitech: fix Dual Action gamepad support

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Grazvydas Ignotas commit 5d74325a2201376a95520a4a38a1ce2c65761c49 upstream. The patch that added Logitech Dual Action gamepad support forgot to update the special driver

[PATCH 3.16 096/217] ALSA: intel8x0: Add clock quirk entry for AD1981B on IBM ThinkPad X41.

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: "Vittorio Gambaletta (VittGam)" commit 4061db03dd71d195b9973ee466f6ed32f6a3fc16 upstream. The clock measurement on the AC'97 audio card found in the IBM ThinkPad X41

[PATCH 3.16 024/217] HID: logitech: fix Dual Action gamepad support

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Grazvydas Ignotas commit 5d74325a2201376a95520a4a38a1ce2c65761c49 upstream. The patch that added Logitech Dual Action gamepad support forgot to update the special driver list for the device.

[PATCH 3.16 096/217] ALSA: intel8x0: Add clock quirk entry for AD1981B on IBM ThinkPad X41.

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: "Vittorio Gambaletta (VittGam)" commit 4061db03dd71d195b9973ee466f6ed32f6a3fc16 upstream. The clock measurement on the AC'97 audio card found in the IBM ThinkPad X41 will often fail, so add a

[PATCH 3.2 100/115] serial: sh-sci: Remove cpufreq notifier to fix crash/deadlock

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit ff1cab374ad98f4b9f408525ca9c08992b4ed784 upstream. The BSP team noticed that there is spin/mutex lock issue on sh-sci when CPUFREQ is used.

[PATCH 3.2 060/115] usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler()

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 894f2fc44f2f3f48c36c973b1123f6ab298be160 upstream. When unexpected situation happened (e.g. tx/rx irq happened while DMAC is used),

[PATCH 3.16 003/217] PCI: imx6: Move PHY reset into imx6_pcie_establish_link()

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Lucas Stach commit 54a47a83421a3b7ee0e0fab7f65d04179bdf59b6 upstream. This adds the PHY reset into a common error path of imx6_pcie_establish_link(), deduplicating

[PATCH 3.2 100/115] serial: sh-sci: Remove cpufreq notifier to fix crash/deadlock

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit ff1cab374ad98f4b9f408525ca9c08992b4ed784 upstream. The BSP team noticed that there is spin/mutex lock issue on sh-sci when CPUFREQ is used. The issue is that the

[PATCH 3.2 060/115] usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler()

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 894f2fc44f2f3f48c36c973b1123f6ab298be160 upstream. When unexpected situation happened (e.g. tx/rx irq happened while DMAC is used), the usbhsf_pkt_handler() was

[PATCH 3.16 003/217] PCI: imx6: Move PHY reset into imx6_pcie_establish_link()

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Lucas Stach commit 54a47a83421a3b7ee0e0fab7f65d04179bdf59b6 upstream. This adds the PHY reset into a common error path of imx6_pcie_establish_link(), deduplicating some of the debug prints.

[PATCH 3.2 111/115] ipv4: l2tp: fix a potential issue in l2tp_ip_recv

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Haishuang Yan [ Upstream commit 5745b8232e942abd5e16e85fa9b27cc21324acf0 ] pskb_may_pull() can change skb->data, so we have to load ptr/optr at the right

[PATCH 3.2 111/115] ipv4: l2tp: fix a potential issue in l2tp_ip_recv

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Haishuang Yan [ Upstream commit 5745b8232e942abd5e16e85fa9b27cc21324acf0 ] pskb_may_pull() can change skb->data, so we have to load ptr/optr at the right place. Signed-off-by: Haishuang Yan

[PATCH 3.16 026/217] HID: fix hid_ignore_special_drivers module parameter

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires commit 4392bf88cabdad5afe5b152d7b9c318e upstream. hid_ignore_special_drivers works fine until hid_scan_report autodetects and

[PATCH 3.16 026/217] HID: fix hid_ignore_special_drivers module parameter

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires commit 4392bf88cabdad5afe5b152d7b9c318e upstream. hid_ignore_special_drivers works fine until hid_scan_report autodetects and reassign devices (for hid-multitouch,

[PATCH 3.2 076/115] parisc: Unbreak handling exceptions from kernel modules

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 2ef4dfd9d9f288943e249b78365a69e3ea3ec072 upstream. Handling exceptions from modules never worked on parisc. It was just masked by the fact that exceptions

[PATCH 3.2 076/115] parisc: Unbreak handling exceptions from kernel modules

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 2ef4dfd9d9f288943e249b78365a69e3ea3ec072 upstream. Handling exceptions from modules never worked on parisc. It was just masked by the fact that exceptions from modules

[PATCH 3.2 037/115] nfsd: fix deadlock secinfo+readdir compound

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit 2f6fc056e899bd0144a08da5cacaecbe8997cd74 upstream. nfsd_lookup_dentry exits with the parent filehandle locked. fh_put also unlocks if necessary

[PATCH 3.2 108/115] farsync: fix off-by-one bug in fst_add_one

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit e725a66c0202b5f36c2f9d59d26a65c53bbf21f7 ] gcc-6 finds an out of bounds access in the fst_add_one function when calculating the end of the mmio

[PATCH 3.2 037/115] nfsd: fix deadlock secinfo+readdir compound

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit 2f6fc056e899bd0144a08da5cacaecbe8997cd74 upstream. nfsd_lookup_dentry exits with the parent filehandle locked. fh_put also unlocks if necessary (nfsd filehandle

[PATCH 3.2 108/115] farsync: fix off-by-one bug in fst_add_one

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit e725a66c0202b5f36c2f9d59d26a65c53bbf21f7 ] gcc-6 finds an out of bounds access in the fst_add_one function when calculating the end of the mmio area:

[PATCH 3.2 063/115] ALSA: usb-audio: Fix double-free in error paths after snd_usb_add_audio_stream() call

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Vladis Dronov commit 836b34a935abc91e13e63053d0a83b24dfb5ea78 upstream. create_fixed_stream_quirk(), snd_usb_parse_audio_interface() and create_uaxx_quirk() functions

[PATCH 3.2 063/115] ALSA: usb-audio: Fix double-free in error paths after snd_usb_add_audio_stream() call

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Vladis Dronov commit 836b34a935abc91e13e63053d0a83b24dfb5ea78 upstream. create_fixed_stream_quirk(), snd_usb_parse_audio_interface() and create_uaxx_quirk() functions allocate the audioformat

[PATCH 3.2 072/115] USB: serial: ftdi_sio: Add support for ICP DAS I-756xU devices

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Josh Boyer commit ea6db90e750328068837bed34cb1302b7a177339 upstream. A Fedora user reports that the ftdi_sio driver works properly for the ICP DAS I-7561U device.

Re: [PATCH] Documentation: fix common spelling mistakes

On Tue, Apr 26, 2016 at 4:44 PM, Paul E. McKenney wrote: > On Tue, Apr 26, 2016 at 04:28:27PM -0700, Kees Cook wrote: >> This fixes several spelling mistakes in the Documentation/ tree, which >> are caught by checkpatch.pl's spell checking. >> >> Signed-off-by: Kees

[PATCH 3.2 072/115] USB: serial: ftdi_sio: Add support for ICP DAS I-756xU devices

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Josh Boyer commit ea6db90e750328068837bed34cb1302b7a177339 upstream. A Fedora user reports that the ftdi_sio driver works properly for the ICP DAS I-7561U device. Further, the user manual for

Re: [PATCH] Documentation: fix common spelling mistakes

On Tue, Apr 26, 2016 at 4:44 PM, Paul E. McKenney wrote: > On Tue, Apr 26, 2016 at 04:28:27PM -0700, Kees Cook wrote: >> This fixes several spelling mistakes in the Documentation/ tree, which >> are caught by checkpatch.pl's spell checking. >> >> Signed-off-by: Kees Cook > > Both "resizeable"

[PATCH 3.2 042/115] raid10: include bio_end_io_list in nr_queued to prevent freeze_array hang

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Shaohua Li commit 23ddba80ebe836476bb2fa1f5ef305dd1c63dc0b upstream. This is the raid10 counterpart of the bug fixed by Nate (raid1: include bio_end_io_list in nr_queued to

[PATCH 3.2 042/115] raid10: include bio_end_io_list in nr_queued to prevent freeze_array hang

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Shaohua Li commit 23ddba80ebe836476bb2fa1f5ef305dd1c63dc0b upstream. This is the raid10 counterpart of the bug fixed by Nate (raid1: include bio_end_io_list in nr_queued to prevent

[PATCH] scripts/spelling.txt: add "fimware" misspelling

A few instances of "fimware" instead of "firmware" were found. Fix these and add it to the spelling.txt file. Reported-by: Randy Dunlap Signed-off-by: Kees Cook --- Looks like spelling.txt changes have been going in through -mm? ---

[PATCH 3.2 038/115] ppp: ensure file->private_data can't be overridden

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault commit e8e56ffd9d2973398b60ece1f1bebb8d67b4d032 upstream. Locking ppp_mutex must be done before dereferencing file->private_data, otherwise it could be

[PATCH 3.16 021/217] ARM: dts: armada-375: use armada-370-sata for SATA

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Lior Amsalem commit b3a7f31eb7375633cd6a742f19488fc5a4208b36 upstream. The Armada 375 has the same SATA IP as Armada 370 and Armada XP, which requires the PHY speed to be

[PATCH] scripts/spelling.txt: add "fimware" misspelling

A few instances of "fimware" instead of "firmware" were found. Fix these and add it to the spelling.txt file. Reported-by: Randy Dunlap Signed-off-by: Kees Cook --- Looks like spelling.txt changes have been going in through -mm? --- drivers/media/usb/dvb-usb/dib0700_core.c | 2 +-

[PATCH 3.2 038/115] ppp: ensure file->private_data can't be overridden

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault commit e8e56ffd9d2973398b60ece1f1bebb8d67b4d032 upstream. Locking ppp_mutex must be done before dereferencing file->private_data, otherwise it could be modified before

[PATCH 3.16 021/217] ARM: dts: armada-375: use armada-370-sata for SATA

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Lior Amsalem commit b3a7f31eb7375633cd6a742f19488fc5a4208b36 upstream. The Armada 375 has the same SATA IP as Armada 370 and Armada XP, which requires the PHY speed to be set in the

[PATCH 3.16 062/217] clk: xgene: Add missing parenthesis when clearing divider value

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Loc Ho commit 0f4c7a138dfefb0ebdbaf56e3ba2acd2958a6605 upstream. In the initial fix for non-zero divider shift value, the parenthesis was missing after the negate operation.

[PATCH 3.16 062/217] clk: xgene: Add missing parenthesis when clearing divider value

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Loc Ho commit 0f4c7a138dfefb0ebdbaf56e3ba2acd2958a6605 upstream. In the initial fix for non-zero divider shift value, the parenthesis was missing after the negate operation. This patch adds

[PATCH 3.16 032/217] ARM: OMAP3: Add cpuidle parameters table for omap3430

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Pali Rohár commit 98f42221501353067251fbf11e732707dbb68ce3 upstream. Based on CPU type choose generic omap3 or omap3430 specific cpuidle parameters. Parameters for

[PATCH 3.16 032/217] ARM: OMAP3: Add cpuidle parameters table for omap3430

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Pali Rohár commit 98f42221501353067251fbf11e732707dbb68ce3 upstream. Based on CPU type choose generic omap3 or omap3430 specific cpuidle parameters. Parameters for omap3430 were measured on

[PATCH 3.16 012/217] crypto: ccp - Limit the amount of information exported

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky commit d1662165ae612ec8b5f94a6b07e65ea58b6dce34 upstream. Since the exported information can be exposed to user-space, instead of exporting the entire

Re: [PATCH v4] mm: SLAB freelist randomization

On Tue, Apr 26, 2016 at 4:17 PM, Andrew Morton wrote: > On Tue, 26 Apr 2016 09:21:10 -0700 Thomas Garnier wrote: > >> Provides an optional config (CONFIG_FREELIST_RANDOM) to randomize the >> SLAB freelist. The list is randomized during

[PATCH 3.2 036/115] ALSA: usb-audio: Add sanity checks for endpoint accesses

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 447d6275f0c21f6cc97a88b3a0c601436a4cdf2a upstream. Add some sanity check codes before actually accessing the endpoint via get_endpoint() in order to avoid

[PATCH 3.2 026/115] sg: fix dxferp in from_to case

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Douglas Gilbert commit 5ecee0a3ee8d74b6950cb41e8989b0c2174568d4 upstream. One of the strange things that the original sg driver did was let the user provide both a

[PATCH 3.16 012/217] crypto: ccp - Limit the amount of information exported

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky commit d1662165ae612ec8b5f94a6b07e65ea58b6dce34 upstream. Since the exported information can be exposed to user-space, instead of exporting the entire request context only export

Re: [PATCH v4] mm: SLAB freelist randomization

On Tue, Apr 26, 2016 at 4:17 PM, Andrew Morton wrote: > On Tue, 26 Apr 2016 09:21:10 -0700 Thomas Garnier wrote: > >> Provides an optional config (CONFIG_FREELIST_RANDOM) to randomize the >> SLAB freelist. The list is randomized during initialization of a new set >> of pages. The order on

[PATCH 3.2 036/115] ALSA: usb-audio: Add sanity checks for endpoint accesses

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 447d6275f0c21f6cc97a88b3a0c601436a4cdf2a upstream. Add some sanity check codes before actually accessing the endpoint via get_endpoint() in order to avoid the invalid

[PATCH 3.2 026/115] sg: fix dxferp in from_to case

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Douglas Gilbert commit 5ecee0a3ee8d74b6950cb41e8989b0c2174568d4 upstream. One of the strange things that the original sg driver did was let the user provide both a data-out buffer (it followed

[PATCH 3.16 085/217] drm/radeon: Don't drop DP 2.7 Ghz link setup on some cards.

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Mario Kleiner commit 459ee1c3fd097ab56ababd8ff4bb7ef6a792de33 upstream. As observed on Apple iMac10,1, DCE-3.2, RV-730, link rate of 2.7 Ghz is not selected,

[PATCH 3.16 085/217] drm/radeon: Don't drop DP 2.7 Ghz link setup on some cards.

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Mario Kleiner commit 459ee1c3fd097ab56ababd8ff4bb7ef6a792de33 upstream. As observed on Apple iMac10,1, DCE-3.2, RV-730, link rate of 2.7 Ghz is not selected, because the args.v1.ucConfig flag

[PATCH 3.2 070/115] xen/events: Mask a moving irq

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Boris Ostrovsky commit ff1e22e7a638a0782f54f81a6c9cb139aca2da35 upstream. Moving an unmasked irq may result in irq handler being invoked on both source and target

[PATCH 3.2 070/115] xen/events: Mask a moving irq

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Boris Ostrovsky commit ff1e22e7a638a0782f54f81a6c9cb139aca2da35 upstream. Moving an unmasked irq may result in irq handler being invoked on both source and target CPUs. With 2-level this can

[PATCH 3.2 034/115] ath9k: fix buffer overrun for ar9287

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 83d6f1f15f8cce844b0a131cbc63e444620e48b5 upstream. Code that was added back in 2.6.38 has an obvious overflow when accessing a static array, and at the time

[PATCH 3.2 034/115] ath9k: fix buffer overrun for ar9287

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 83d6f1f15f8cce844b0a131cbc63e444620e48b5 upstream. Code that was added back in 2.6.38 has an obvious overflow when accessing a static array, and at the time it was added

<    2   3   4   5   6   7   8   9   10   11   >