[PATCH 4.4 76/91] Btrfs: adjust outstanding_extents counter properly when dio write is split

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo [ Upstream commit c2931667c83ded6504b3857e99cc45b21fa496fb ] Currently how btrfs dio deals with split dio write is not good enough if dio write is split into

[PATCH 4.4 76/91] Btrfs: adjust outstanding_extents counter properly when dio write is split

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo [ Upstream commit c2931667c83ded6504b3857e99cc45b21fa496fb ] Currently how btrfs dio deals with split dio write is not good enough if dio write is split into several segments due to

[GIT PULL] clk fixes for v4.13-rc4

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877: Linux v4.13-rc1 (2017-07-15 15:22:10 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus for you to fetch changes up to

[GIT PULL] clk fixes for v4.13-rc4

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877: Linux v4.13-rc1 (2017-07-15 15:22:10 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git tags/clk-fixes-for-linus for you to fetch changes up to

[PATCH 3.18 01/50] af_key: Add lock to key dump

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Yuejie Shi commit 89e357d83c06b6fac581c3ca7f0ee3ae7e67109e upstream. A dump may come in the middle of another dump, modifying its dump structure members. This race

[PATCH 3.18 01/50] af_key: Add lock to key dump

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Yuejie Shi commit 89e357d83c06b6fac581c3ca7f0ee3ae7e67109e upstream. A dump may come in the middle of another dump, modifying its dump structure members. This race condition will result in

[PATCH 4.4 83/91] arm64: mm: fix show_pte KERN_CONT fallout

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Rutland [ Upstream commit 6ef4fb387d50fa8f3bffdffc868b57e981cdd709 ] Recent changes made KERN_CONT mandatory for continued lines. In the absence of KERN_CONT, a

[PATCH 3.18 02/50] pstore: Make spinlock per zone instead of global

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Joel Fernandes commit 109704492ef637956265ec2eb72ae7b3b39eb6f4 upstream. Currently pstore has a global spinlock for all zones. Since the zones are independent and modify

[PATCH 4.4 83/91] arm64: mm: fix show_pte KERN_CONT fallout

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mark Rutland [ Upstream commit 6ef4fb387d50fa8f3bffdffc868b57e981cdd709 ] Recent changes made KERN_CONT mandatory for continued lines. In the absence of KERN_CONT, a newline may be implicit

[PATCH 3.18 02/50] pstore: Make spinlock per zone instead of global

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Joel Fernandes commit 109704492ef637956265ec2eb72ae7b3b39eb6f4 upstream. Currently pstore has a global spinlock for all zones. Since the zones are independent and modify different areas of

[PATCH 3.18 04/50] powerpc/pseries: Fix of_node_put() underflow during reconfig remove

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Laurent Vivier commit 4fd1bd443e80b12f0a01a45fb9a793206b41cb72 upstream. As for commit 68baf692c435 ("powerpc/pseries: Fix of_node_put() underflow during DLPAR remove"),

[PATCH 3.18 03/50] net: reduce skb_warn_bad_offload() noise

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit b2504a5dbef3305ef41988ad270b0e8ec289331c upstream. Dmitry reported warnings occurring in __skb_gso_segment() [1] All SKB_GSO_DODGY producers can

[PATCH 3.18 04/50] powerpc/pseries: Fix of_node_put() underflow during reconfig remove

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Laurent Vivier commit 4fd1bd443e80b12f0a01a45fb9a793206b41cb72 upstream. As for commit 68baf692c435 ("powerpc/pseries: Fix of_node_put() underflow during DLPAR remove"), the call to

[PATCH 3.18 03/50] net: reduce skb_warn_bad_offload() noise

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit b2504a5dbef3305ef41988ad270b0e8ec289331c upstream. Dmitry reported warnings occurring in __skb_gso_segment() [1] All SKB_GSO_DODGY producers can allow user space to feed

Re: [PATCH v4 4/5] squashfs: Add zstd support

Signed-off-by: Sean Purcell On Fri, Aug 4, 2017 at 4:19 PM, Nick Terrell wrote: > Add zstd compression and decompression support to SquashFS. zstd is a > great fit for SquashFS because it can compress at ratios approaching xz, > while decompressing twice as fast

Re: [PATCH v4 4/5] squashfs: Add zstd support

Signed-off-by: Sean Purcell On Fri, Aug 4, 2017 at 4:19 PM, Nick Terrell wrote: > Add zstd compression and decompression support to SquashFS. zstd is a > great fit for SquashFS because it can compress at ratios approaching xz, > while decompressing twice as fast as zlib. For SquashFS in

[PATCH 4.4 85/91] sh_eth: enable RX descriptor word 0 shift on SH7734

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sergei Shtylyov [ Upstream commit 71eae1ca77fd6be218d8a952d97bba827e56516d ] The RX descriptor word 0 on SH7734 has the RFS[9:0] field in bits 16-25 (bits

[PATCH 3.18 08/50] KVM: PPC: Book3S HV: Reload HTM registers explicitly

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras Commit 46a704f8409f ("KVM: PPC: Book3S HV: Preserve userspace HTM state properly", 2017-06-15) added code which assumes that the kernel is able to handle a TM

[PATCH 4.4 85/91] sh_eth: enable RX descriptor word 0 shift on SH7734

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sergei Shtylyov [ Upstream commit 71eae1ca77fd6be218d8a952d97bba827e56516d ] The RX descriptor word 0 on SH7734 has the RFS[9:0] field in bits 16-25 (bits 0-15 usually used for that are

[PATCH 3.18 08/50] KVM: PPC: Book3S HV: Reload HTM registers explicitly

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras Commit 46a704f8409f ("KVM: PPC: Book3S HV: Preserve userspace HTM state properly", 2017-06-15) added code which assumes that the kernel is able to handle a TM (transactional

[PATCH 3.18 05/50] md/raid5: add thread_group worker async_tx_issue_pending_all

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ofer Heifetz commit 7e96d559634b73a8158ee99a7abece2eacec2668 upstream. Since thread_group worker and raid5d kthread are not in sync, if worker writes stripe before raid5d

[PATCH 3.18 05/50] md/raid5: add thread_group worker async_tx_issue_pending_all

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ofer Heifetz commit 7e96d559634b73a8158ee99a7abece2eacec2668 upstream. Since thread_group worker and raid5d kthread are not in sync, if worker writes stripe before raid5d then requests will

[PATCH 3.18 00/50] 3.18.64-stable review

This is the start of the stable review cycle for the 3.18.64 release. There are 50 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 Aug 6 23:15:34 UTC 2017. Anything

[PATCH 3.18 00/50] 3.18.64-stable review

This is the start of the stable review cycle for the 3.18.64 release. There are 50 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 Aug 6 23:15:34 UTC 2017. Anything

Re: [PATCH] intel-vbtn: match power button on press rather than release

On Friday, August 4, 2017 7:29:53 PM CEST Darren Hart wrote: > On Fri, Aug 04, 2017 at 12:00:06PM -0500, Mario Limonciello wrote: > > This fixes a problem where the system gets stuck in a loop > > unable to wakeup via power button in s2idle. > > > > The problem happens because: > > - press power

Re: [PATCH] intel-vbtn: match power button on press rather than release

On Friday, August 4, 2017 7:29:53 PM CEST Darren Hart wrote: > On Fri, Aug 04, 2017 at 12:00:06PM -0500, Mario Limonciello wrote: > > This fixes a problem where the system gets stuck in a loop > > unable to wakeup via power button in s2idle. > > > > The problem happens because: > > - press power

[PATCH 3.18 10/50] Revert "powerpc/numa: Fix percpu allocations to be NUMA aware"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 138bb14846a5856747694ae9ef565c9eb4533a1e which is commit ba4a648f12f4cd0a8003dd229b6ca8a53348ee4b upstream. Michal Hocko

[PATCH 3.18 10/50] Revert "powerpc/numa: Fix percpu allocations to be NUMA aware"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 138bb14846a5856747694ae9ef565c9eb4533a1e which is commit ba4a648f12f4cd0a8003dd229b6ca8a53348ee4b upstream. Michal Hocko writes: JFYI. We have

[PATCH 3.18 19/50] isdn/i4l: fix buffer overflow

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Annie Cherkaev commit 9f5af546e6acc30f075828cb58c7f09665033967 upstream. This fixes a potential buffer overflow in isdn_net.c caused by an unbounded strcpy. [ ISDN

[PATCH 3.18 19/50] isdn/i4l: fix buffer overflow

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Annie Cherkaev commit 9f5af546e6acc30f075828cb58c7f09665033967 upstream. This fixes a potential buffer overflow in isdn_net.c caused by an unbounded strcpy. [ ISDN seems to be effectively

[PATCH 3.18 21/50] mailbox: always wait in mbox_send_message for blocking Tx mode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla commit c61b781ee084e69855477d23dd33e7e6caad652c upstream. There exists a race when msg_submit return immediately as there was an active request being

[PATCH 3.18 06/50] drm/vmwgfx: Fix gcc-7.1.1 warning

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit fcfffdd8f98ac305285dca568b5065ef86be6458 upstream. The current code does not look correct, and the reason for it is probably lost. Since this now

[PATCH 3.18 21/50] mailbox: always wait in mbox_send_message for blocking Tx mode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla commit c61b781ee084e69855477d23dd33e7e6caad652c upstream. There exists a race when msg_submit return immediately as there was an active request being processed which may have

[PATCH 3.18 06/50] drm/vmwgfx: Fix gcc-7.1.1 warning

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit fcfffdd8f98ac305285dca568b5065ef86be6458 upstream. The current code does not look correct, and the reason for it is probably lost. Since this now generates a compiler

[PATCH 3.18 20/50] wil6210: fix deadlock when using fw_no_recovery option

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lior David commit dfb5b098e0f40b68aa07f2ec55f4dd762efefbfa upstream. When FW crashes with no_fw_recovery option, driver waits for manual recovery with wil->mutex

[PATCH 3.18 22/50] mailbox: skip complete wait event if timer expired

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla commit cc6eeaa3029a6dbcb4ad41b1f92876483bd88965 upstream. If a wait_for_completion_timeout() call returns due to a timeout, complete() can get called after

[PATCH 3.18 20/50] wil6210: fix deadlock when using fw_no_recovery option

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lior David commit dfb5b098e0f40b68aa07f2ec55f4dd762efefbfa upstream. When FW crashes with no_fw_recovery option, driver waits for manual recovery with wil->mutex held, this can easily create

[PATCH 3.18 22/50] mailbox: skip complete wait event if timer expired

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla commit cc6eeaa3029a6dbcb4ad41b1f92876483bd88965 upstream. If a wait_for_completion_timeout() call returns due to a timeout, complete() can get called after returning from the

[PATCH 3.18 23/50] mailbox: handle empty message in tx_tick

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla commit cb710ab1d8a23f68ff8f45aedf3e552bb90e70de upstream. We already check if the message is empty before calling the client tx_done callback. Calling

[PATCH 3.18 24/50] mpt3sas: Dont overreach ioc->reply_post[] during initialization

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Calvin Owens commit 5ec8a1753bc29efa7e4b1391d691c9c719b30257 upstream. In _base_make_ioc_operational(), we walk ioc->reply_queue_list and pull a pointer out of successive

[PATCH 3.18 23/50] mailbox: handle empty message in tx_tick

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sudeep Holla commit cb710ab1d8a23f68ff8f45aedf3e552bb90e70de upstream. We already check if the message is empty before calling the client tx_done callback. Calling completion on a wait event

[PATCH 3.18 24/50] mpt3sas: Dont overreach ioc->reply_post[] during initialization

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Calvin Owens commit 5ec8a1753bc29efa7e4b1391d691c9c719b30257 upstream. In _base_make_ioc_operational(), we walk ioc->reply_queue_list and pull a pointer out of successive elements of

[PATCH 3.18 28/50] net: sctp: fix race for one-to-many sockets in sendmsgs auto associate

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit 2061dcd6bff8b774b4fac8b0739b6be3f87bc9f2 upstream. I.e. one-to-many sockets in SCTP are not required to explicitly call into connect(2) or

[PATCH 3.18 27/50] ipv6: fix possible deadlock in ip6_fl_purge / ip6_fl_gc

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jan Stancek commit 4762fb980465463734f02c67c67f40beb8903f73 upstream. Use spin_lock_bh in ip6_fl_purge() to prevent following potentially deadlock scenario between

[PATCH 3.18 11/50] Staging: comedi: comedi_fops: Avoid orphaned proc entry

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Cheah Kok Cheong commit bf279ece37d2a3eaaa9813fcd7a1d8a81eb29c20 upstream. Move comedi_proc_init to the end to avoid orphaned proc entry if module loading failed.

[PATCH 3.18 28/50] net: sctp: fix race for one-to-many sockets in sendmsgs auto associate

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit 2061dcd6bff8b774b4fac8b0739b6be3f87bc9f2 upstream. I.e. one-to-many sockets in SCTP are not required to explicitly call into connect(2) or sctp_connectx(2) prior to

[PATCH 3.18 27/50] ipv6: fix possible deadlock in ip6_fl_purge / ip6_fl_gc

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jan Stancek commit 4762fb980465463734f02c67c67f40beb8903f73 upstream. Use spin_lock_bh in ip6_fl_purge() to prevent following potentially deadlock scenario between ip6_fl_purge() and

[PATCH 3.18 11/50] Staging: comedi: comedi_fops: Avoid orphaned proc entry

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Cheah Kok Cheong commit bf279ece37d2a3eaaa9813fcd7a1d8a81eb29c20 upstream. Move comedi_proc_init to the end to avoid orphaned proc entry if module loading failed. Signed-off-by: Cheah Kok

[PATCH 3.18 30/50] net, sched: fix soft lockup in tc_classify

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit 628185cfddf1dfb701c4efe2cfd72cf5b09f5702 upstream. Shahar reported a soft lockup in tc_classify(), where we run into an endless loop when walking

[PATCH 3.18 30/50] net, sched: fix soft lockup in tc_classify

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit 628185cfddf1dfb701c4efe2cfd72cf5b09f5702 upstream. Shahar reported a soft lockup in tc_classify(), where we run into an endless loop when walking the classifier chain

[PATCH 3.18 25/50] kaweth: fix firmware download

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 60bcabd080f53561efa9288be45c128feda1a8bb upstream. This fixes the oops discovered by the Umap2 project and Alan Stern. The intf member needs to be set

[PATCH 3.18 29/50] sh_eth: Fix ethtool operation crash when net device is down

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 4f9dce230b32eec45cec8c28cae61efdfa2f7d57 upstream. The driver connects and disconnects the PHY device whenever the net device is brought up

[PATCH 3.18 25/50] kaweth: fix firmware download

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 60bcabd080f53561efa9288be45c128feda1a8bb upstream. This fixes the oops discovered by the Umap2 project and Alan Stern. The intf member needs to be set before the firmware

[PATCH 3.18 29/50] sh_eth: Fix ethtool operation crash when net device is down

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 4f9dce230b32eec45cec8c28cae61efdfa2f7d57 upstream. The driver connects and disconnects the PHY device whenever the net device is brought up and down. The ethtool

[PATCH 3.18 31/50] ipmi/watchdog: fix watchdog timeout set on reboot

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Valentin Vidic commit 860f01e96981a68553f3ca49f574ff14fe955e72 upstream. systemd by default starts watchdog on reboot and sets the timer to

[PATCH 3.18 31/50] ipmi/watchdog: fix watchdog timeout set on reboot

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Valentin Vidic commit 860f01e96981a68553f3ca49f574ff14fe955e72 upstream. systemd by default starts watchdog on reboot and sets the timer to ShutdownWatchdogSec=10min. Reboot handler in

[PATCH 3.18 33/50] [media] v4l: s5c73m3: fix negation operator

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrzej Hajda commit a2370ba2752538404e363346b339869c9973aeac upstream. Bool values should be negated using logical operators. Using bitwise operators results in

[PATCH 3.18 33/50] [media] v4l: s5c73m3: fix negation operator

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andrzej Hajda commit a2370ba2752538404e363346b339869c9973aeac upstream. Bool values should be negated using logical operators. Using bitwise operators results in unexpected and possibly

[PATCH 3.18 32/50] dentry name snapshots

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 49d31c2f389acfe83417083e1208422b4091cd9e upstream. take_dentry_name_snapshot() takes a safe snapshot of dentry name; if the name is a short one, it

[PATCH 3.18 34/50] pstore: Allow prz to control need for locking

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Joel Fernandes commit 663deb47880f2283809669563c5a52ac7c6aef1a upstream. In preparation of not locking at all for certain buffers depending on if there's contention, make

[PATCH 3.18 32/50] dentry name snapshots

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 49d31c2f389acfe83417083e1208422b4091cd9e upstream. take_dentry_name_snapshot() takes a safe snapshot of dentry name; if the name is a short one, it gets copied into

[PATCH 3.18 34/50] pstore: Allow prz to control need for locking

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Joel Fernandes commit 663deb47880f2283809669563c5a52ac7c6aef1a upstream. In preparation of not locking at all for certain buffers depending on if there's contention, make locking optional

[PATCH 3.18 12/50] Bluetooth: bnep: bnep_add_connection() should verify that its dealing with l2cap socket

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 71bb99a02b32b4cc4265118e85f6035ca72923f0 upstream. same story as cmtp Signed-off-by: Al Viro Signed-off-by: Marcel Holtmann

[PATCH 3.18 12/50] Bluetooth: bnep: bnep_add_connection() should verify that its dealing with l2cap socket

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 71bb99a02b32b4cc4265118e85f6035ca72923f0 upstream. same story as cmtp Signed-off-by: Al Viro Signed-off-by: Marcel Holtmann Signed-off-by: Greg Kroah-Hartman ---

[PATCH 3.18 38/50] tpm: fix a kernel memory leak in tpm-sysfs.c

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Sakkinen commit 13b47cfcfc60495cde216eef4c01040d76174cbe upstream. While cleaning up sysfs callback that prints EK we discovered a kernel memory leak.

[PATCH 3.18 26/50] kaweth: fix oops upon failed memory allocation

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 575ced7f8090c1a4e91e2daf8da9352a6a1fc7a7 upstream. Just return an error upon failure. Signed-off-by: Oliver Neukum Signed-off-by:

[PATCH 3.18 38/50] tpm: fix a kernel memory leak in tpm-sysfs.c

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jarkko Sakkinen commit 13b47cfcfc60495cde216eef4c01040d76174cbe upstream. While cleaning up sysfs callback that prints EK we discovered a kernel memory leak. This commit fixes the issue by

[PATCH 3.18 26/50] kaweth: fix oops upon failed memory allocation

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 575ced7f8090c1a4e91e2daf8da9352a6a1fc7a7 upstream. Just return an error upon failure. Signed-off-by: Oliver Neukum Signed-off-by: David S. Miller Signed-off-by: Amit

[PATCH 3.18 40/50] r8169: add support for RTL8168 series add-on card.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chun-Hao Lin [ Upstream commit 610c908773d30907c950ca3b2ee8ac4b2813537b ] This chip is the same as RTL8168, but its device id is 0x8161. Signed-off-by: Chun-Hao Lin

[PATCH 3.18 40/50] r8169: add support for RTL8168 series add-on card.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chun-Hao Lin [ Upstream commit 610c908773d30907c950ca3b2ee8ac4b2813537b ] This chip is the same as RTL8168, but its device id is 0x8161. Signed-off-by: Chun-Hao Lin Signed-off-by: David S.

[PATCH 3.18 42/50] ipv6: Should use consistent conditional judgement for ip6 fragment between __ip6_append_data and ip6_finish_output

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Zheng Li [ Upstream commit e4c5e13aa45c23692e4acf56f0b3533f328199b2 ] There is an inconsistent conditional judgement between __ip6_append_data and ip6_finish_output

[PATCH 3.18 39/50] x86/mce/AMD: Make the init code more robust

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner [ Upstream commit 0dad3a3014a0b9e72521ff44f17e0054f43dcdea ] If mce_device_init() fails then the mce device pointer is NULL and the AMD mce code happily

[PATCH 3.18 42/50] ipv6: Should use consistent conditional judgement for ip6 fragment between __ip6_append_data and ip6_finish_output

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Zheng Li [ Upstream commit e4c5e13aa45c23692e4acf56f0b3533f328199b2 ] There is an inconsistent conditional judgement between __ip6_append_data and ip6_finish_output functions, the variable

[PATCH 3.18 39/50] x86/mce/AMD: Make the init code more robust

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner [ Upstream commit 0dad3a3014a0b9e72521ff44f17e0054f43dcdea ] If mce_device_init() fails then the mce device pointer is NULL and the AMD mce code happily dereferences it. Add

[PATCH 3.18 36/50] pstore: Use dynamic spinlock initializer

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit e9a330c4289f2ba1ca4bf98c2b430ab165a8931b upstream. The per-prz spinlock should be using the dynamic initializer so that lockdep can correctly track it.

[PATCH 3.18 36/50] pstore: Use dynamic spinlock initializer

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit e9a330c4289f2ba1ca4bf98c2b430ab165a8931b upstream. The per-prz spinlock should be using the dynamic initializer so that lockdep can correctly track it. Without this, under

[PATCH 3.18 35/50] pstore: Correctly initialize spinlock and flags

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 76d5692a58031696e282384cbd893832bc92bd76 upstream. The ram backend wasn't always initializing its spinlock correctly. Since it was coming from kzalloc

[PATCH 3.18 35/50] pstore: Correctly initialize spinlock and flags

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 76d5692a58031696e282384cbd893832bc92bd76 upstream. The ram backend wasn't always initializing its spinlock correctly. Since it was coming from kzalloc memory, though, it was

[PATCH 3.18 44/50] drm/msm: Ensure that the hardware write pointer is valid

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Crouse [ Upstream commit 88b333b0ed790f9433ff542b163bf972953b74d3 ] Currently the value written to CP_RB_WPTR is calculated on the fly as (rb->next -

[PATCH 3.18 44/50] drm/msm: Ensure that the hardware write pointer is valid

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Crouse [ Upstream commit 88b333b0ed790f9433ff542b163bf972953b74d3 ] Currently the value written to CP_RB_WPTR is calculated on the fly as (rb->next - rb->start). But as the code is

[PATCH 3.18 43/50] net/mlx4: Remove BUG_ON from ICM allocation routine

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit c1d5f8ff80ea84768f5fae1ca9d1abfbb5e6bbaa ] This patch removes BUG_ON() macro from mlx4_alloc_icm_coherent() by checking DMA address

[PATCH 3.18 43/50] net/mlx4: Remove BUG_ON from ICM allocation routine

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit c1d5f8ff80ea84768f5fae1ca9d1abfbb5e6bbaa ] This patch removes BUG_ON() macro from mlx4_alloc_icm_coherent() by checking DMA address alignment in advance and

[PATCH 3.18 46/50] vfio-pci: use 32-bit comparisons for register address for gcc-4.5

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 45e869714489431625c569d21fc952428d761476 ] Using ancient compilers (gcc-4.5 or older) on ARM, we get a link failure with the vfio-pci driver:

[PATCH 3.18 46/50] vfio-pci: use 32-bit comparisons for register address for gcc-4.5

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 45e869714489431625c569d21fc952428d761476 ] Using ancient compilers (gcc-4.5 or older) on ARM, we get a link failure with the vfio-pci driver: ERROR:

[PATCH 3.18 45/50] drm/msm: Verify that MSM_SUBMIT_BO_FLAGS are set

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Crouse [ Upstream commit a6cb3b864b21b7345f824a4faa12b723c8aaf099 ] For every submission buffer object one of MSM_SUBMIT_BO_WRITE and MSM_SUBMIT_BO_READ must

Re: [PATCH v2 2/5] fs, xfs: introduce FALLOC_FL_SEAL_BLOCK_MAP

On Thu, Aug 03, 2017 at 07:28:17PM -0700, Dan Williams wrote: > diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c > index fe0f8f7f4bb7..46d8eb9e19fc 100644 > --- a/fs/xfs/xfs_bmap_util.c > +++ b/fs/xfs/xfs_bmap_util.c > @@ -1393,6 +1393,107 @@ xfs_zero_file_space( > > } > > +/*

[PATCH 3.18 14/50] Bluetooth: cmtp: cmtp_add_connection() should verify that its dealing with l2cap socket

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 96c26653ce65bf84f3212f8b00d4316c1efcbf4c upstream. ... rather than relying on ciptool(8) never passing it anything else. Give it e.g. an AF_UNIX

Re: [PATCH v2 2/5] fs, xfs: introduce FALLOC_FL_SEAL_BLOCK_MAP

On Thu, Aug 03, 2017 at 07:28:17PM -0700, Dan Williams wrote: > diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c > index fe0f8f7f4bb7..46d8eb9e19fc 100644 > --- a/fs/xfs/xfs_bmap_util.c > +++ b/fs/xfs/xfs_bmap_util.c > @@ -1393,6 +1393,107 @@ xfs_zero_file_space( > > } > > +/*

[PATCH 3.18 14/50] Bluetooth: cmtp: cmtp_add_connection() should verify that its dealing with l2cap socket

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 96c26653ce65bf84f3212f8b00d4316c1efcbf4c upstream. ... rather than relying on ciptool(8) never passing it anything else. Give it e.g. an AF_UNIX connected socket (from

[PATCH 3.18 45/50] drm/msm: Verify that MSM_SUBMIT_BO_FLAGS are set

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Crouse [ Upstream commit a6cb3b864b21b7345f824a4faa12b723c8aaf099 ] For every submission buffer object one of MSM_SUBMIT_BO_WRITE and MSM_SUBMIT_BO_READ must be set (and nothing

[PATCH 3.18 13/50] Bluetooth: Fix potential NULL dereference

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hedberg commit 88d9077c27d0c1a7c022d9dc987640beecf23560 upstream. The bnep_get_device function may be triggered by an ioctl just after a connection has gone

[PATCH 3.18 13/50] Bluetooth: Fix potential NULL dereference

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hedberg commit 88d9077c27d0c1a7c022d9dc987640beecf23560 upstream. The bnep_get_device function may be triggered by an ioctl just after a connection has gone down. In such a case the

[PATCH 3.18 17/50] string: provide strscpy()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chris Metcalf commit 30035e45753b708e7d47a98398500ca005e02b86 upstream. The strscpy() API is intended to be used instead of strlcpy(), and instead of most uses of

[PATCH 3.18 17/50] string: provide strscpy()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chris Metcalf commit 30035e45753b708e7d47a98398500ca005e02b86 upstream. The strscpy() API is intended to be used instead of strlcpy(), and instead of most uses of strncpy(). - Unlike

[PATCH 3.18 09/50] KVM: PPC: Book3S HV: Save/restore host values of debug registers

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 7ceaa6dcd8c6f59588428cec37f3c8093dd1011f upstream. At present, HV KVM on POWER8 and POWER9 machines loses any instruction or data breakpoint set in

[PATCH 3.18 07/50] KVM: PPC: Book3S HV: Restore critical SPRs to host values on guest exit

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 4c3bb4ccd074e1a0552078c0bf94c662367a1658 upstream. This restores several special-purpose registers (SPRs) to sane values on guest exit that were

[PATCH 3.18 09/50] KVM: PPC: Book3S HV: Save/restore host values of debug registers

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 7ceaa6dcd8c6f59588428cec37f3c8093dd1011f upstream. At present, HV KVM on POWER8 and POWER9 machines loses any instruction or data breakpoint set in the host whenever a

[PATCH 3.18 07/50] KVM: PPC: Book3S HV: Restore critical SPRs to host values on guest exit

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 4c3bb4ccd074e1a0552078c0bf94c662367a1658 upstream. This restores several special-purpose registers (SPRs) to sane values on guest exit that were missed before. TAR and

[PATCH 3.18 18/50] strscpy: zero any trailing garbage bytes in the destination

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chris Metcalf commit 990486c8af044f89bddfbde1d1cf9fde449bedbf upstream. It's possible that the destination can be shadowed in userspace (as, for example, the perf buffers

[PATCH 3.18 18/50] strscpy: zero any trailing garbage bytes in the destination

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Chris Metcalf commit 990486c8af044f89bddfbde1d1cf9fde449bedbf upstream. It's possible that the destination can be shadowed in userspace (as, for example, the perf buffers are now). So we

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