Re: [PATCH 3/3] IPI: Avoid to use 2 cache lines for one call_single_data

Peter Zijlstra writes: > On Fri, Aug 04, 2017 at 10:05:55AM +0800, Huang, Ying wrote: >> "Huang, Ying" writes: >> > Peter Zijlstra writes: > >> >> +struct __call_single_data { >> >> struct llist_node llist; >> >>

Re: [PATCH 3/3] IPI: Avoid to use 2 cache lines for one call_single_data

Peter Zijlstra writes: > On Fri, Aug 04, 2017 at 10:05:55AM +0800, Huang, Ying wrote: >> "Huang, Ying" writes: >> > Peter Zijlstra writes: > >> >> +struct __call_single_data { >> >> struct llist_node llist; >> >> smp_call_func_t func; >> >> void *info; >> >> unsigned int flags; >> >>

[PATCH 4.9 001/105] af_key: Add lock to key dump

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

[PATCH 4.9 001/105] af_key: Add lock to key dump

4.9-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.9 008/105] parisc: Extend disabled preemption in copy_user_page

4.9-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit 56008c04ebc099940021b714da2d7779117cf6a7 upstream. It's always bothered me that we only disable preemption in copy_user_page around the call to

[PATCH 4.9 008/105] parisc: Extend disabled preemption in copy_user_page

4.9-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit 56008c04ebc099940021b714da2d7779117cf6a7 upstream. It's always bothered me that we only disable preemption in copy_user_page around the call to flush_dcache_page_asm.

[PATCH 4.9 019/105] KVM: PPC: Book3S HV: Restore critical SPRs to host values on guest exit

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

[PATCH 4.9 017/105] drm/nouveau/disp/nv50-: bump max chans to 21

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ilia Mirkin commit a90e049cacd965dade4dae7263b4d3fd550e78b6 upstream. GP102's cursors go from chan 17..20. Increase the array size to hold their data properly. Fixes:

[PATCH 4.9 017/105] drm/nouveau/disp/nv50-: bump max chans to 21

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ilia Mirkin commit a90e049cacd965dade4dae7263b4d3fd550e78b6 upstream. GP102's cursors go from chan 17..20. Increase the array size to hold their data properly. Fixes: e50fcff15f

[PATCH 4.9 019/105] KVM: PPC: Book3S HV: Restore critical SPRs to host values on guest exit

4.9-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 4.9 018/105] drm/nouveau/bar/gf100: fix access to upper half of BAR2

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 38bcb208f60924a031b9f809f7cd252ea4a94e5f upstream. Bit 30 being set causes the upper half of BAR2 to stay in physical mode, mapped over the end of VRAM,

[PATCH 4.9 018/105] drm/nouveau/bar/gf100: fix access to upper half of BAR2

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 38bcb208f60924a031b9f809f7cd252ea4a94e5f upstream. Bit 30 being set causes the upper half of BAR2 to stay in physical mode, mapped over the end of VRAM, even when the rest of

[PATCH 4.9 021/105] Revert "powerpc/numa: Fix percpu allocations to be NUMA aware"

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

[PATCH 4.9 021/105] Revert "powerpc/numa: Fix percpu allocations to be NUMA aware"

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

[PATCH 4.9 020/105] KVM: PPC: Book3S HV: Save/restore host values of debug registers

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

[PATCH 4.9 020/105] KVM: PPC: Book3S HV: Save/restore host values of debug registers

4.9-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 4.9 026/105] nfc: Fix hangup of RC-S380* in port100_send_ack()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: OGAWA Hirofumi commit 2497128133f8169b24b928852ba6eae34fc495e5 upstream. If port100_send_ack() was called twice or more, it has race to hangup.

[PATCH 4.9 026/105] nfc: Fix hangup of RC-S380* in port100_send_ack()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: OGAWA Hirofumi commit 2497128133f8169b24b928852ba6eae34fc495e5 upstream. If port100_send_ack() was called twice or more, it has race to hangup. port100_send_ack()

[PATCH 4.9 024/105] smp/hotplug: Move unparking of percpu threads to the control CPU

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 9cd4f1a4e7a858849e889a081a99adff83e08e4c upstream. Vikram reported the following backtrace: BUG: scheduling while atomic: swapper/7/0/0x0002

[PATCH 4.9 024/105] smp/hotplug: Move unparking of percpu threads to the control CPU

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 9cd4f1a4e7a858849e889a081a99adff83e08e4c upstream. Vikram reported the following backtrace: BUG: scheduling while atomic: swapper/7/0/0x0002 CPU: 7 PID: 0

[PATCH 4.9 009/105] parisc: Suspend lockup detectors before system halt

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 56188832a50f09998cb570ba3771a1d25c193c0e upstream. Some machines can't power off the machine, so disable the lockup detectors to avoid this watchdog BUG to

[PATCH 4.9 027/105] nfc: fdp: fix NULL pointer dereference

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee commit b6355fb3f5f40bbce165847d277e64896cab8f95 upstream. We are checking phy after dereferencing it. We can print the debug information after

[PATCH 4.9 009/105] parisc: Suspend lockup detectors before system halt

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller commit 56188832a50f09998cb570ba3771a1d25c193c0e upstream. Some machines can't power off the machine, so disable the lockup detectors to avoid this watchdog BUG to show up every

[PATCH 4.9 027/105] nfc: fdp: fix NULL pointer dereference

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee commit b6355fb3f5f40bbce165847d277e64896cab8f95 upstream. We are checking phy after dereferencing it. We can print the debug information after checking it. If phy is NULL then

[PATCH 4.9 023/105] drm: rcar-du: Simplify and fix probe error handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Laurent Pinchart commit 4f7b0d263833928e947e172eff2d2997179c5cb9 upstream. It isn't safe to call drm_dev_unregister() without first initializing mode

[PATCH 4.9 023/105] drm: rcar-du: Simplify and fix probe error handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Laurent Pinchart commit 4f7b0d263833928e947e172eff2d2997179c5cb9 upstream. It isn't safe to call drm_dev_unregister() without first initializing mode setting with drm_mode_config_init(). This

[PATCH 4.9 022/105] Staging: comedi: comedi_fops: Avoid orphaned proc entry

4.9-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 4.9 022/105] Staging: comedi: comedi_fops: Avoid orphaned proc entry

4.9-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 4.9 031/105] ath10k: fix null deref on wmi-tlv when trying spectral scan

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michal Kazior commit 18ae68fff392e445af3c2d8be9bef8a16e1c72a7 upstream. WMI ops wrappers did not properly check for null function pointers for spectral scan. This

[PATCH 4.9 031/105] ath10k: fix null deref on wmi-tlv when trying spectral scan

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michal Kazior commit 18ae68fff392e445af3c2d8be9bef8a16e1c72a7 upstream. WMI ops wrappers did not properly check for null function pointers for spectral scan. This caused null dereference crash

[PATCH 4.9 032/105] wil6210: fix deadlock when using fw_no_recovery option

4.9-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 4.9 032/105] wil6210: fix deadlock when using fw_no_recovery option

4.9-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 4.9 035/105] mailbox: handle empty message in tx_tick

4.9-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 4.9 034/105] mailbox: skip complete wait event if timer expired

4.9-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 4.9 035/105] mailbox: handle empty message in tx_tick

4.9-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 4.9 034/105] mailbox: skip complete wait event if timer expired

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

[PATCH 4.9 029/105] isdn: Fix a sleep-in-atomic bug

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai commit e8f4ae85439f34bec3b0ab69223a41809dab28c9 upstream. The driver may sleep under a spin lock, the function call path is: isdn_ppp_mp_receive (acquire the

[PATCH 4.9 029/105] isdn: Fix a sleep-in-atomic bug

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai commit e8f4ae85439f34bec3b0ab69223a41809dab28c9 upstream. The driver may sleep under a spin lock, the function call path is: isdn_ppp_mp_receive (acquire the lock)

[PATCH 4.9 033/105] mailbox: always wait in mbox_send_message for blocking Tx mode

4.9-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 4.9 033/105] mailbox: always wait in mbox_send_message for blocking Tx mode

4.9-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 4.9 028/105] net: phy: Do not perform software reset for Generic PHY

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli commit 0878fff1f42c18e448ab5b8b4f6a3eb32365b5b6 upstream. The Generic PHY driver is a catch-all PHY driver and it should preserve whatever prior

[PATCH 4.9 028/105] net: phy: Do not perform software reset for Generic PHY

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli commit 0878fff1f42c18e448ab5b8b4f6a3eb32365b5b6 upstream. The Generic PHY driver is a catch-all PHY driver and it should preserve whatever prior initialization has been done

[PATCH 4.9 030/105] isdn/i4l: fix buffer overflow

4.9-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 4.9 030/105] isdn/i4l: fix buffer overflow

4.9-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 4.9 036/105] sched/cgroup: Move sched_online_group() back into css_online() to fix crash

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit 96b777452d8881480fd5be50112f791c17db4b6b upstream. Commit: 2f5177f0fd7e ("sched/cgroup: Fix/cleanup cgroup teardown/init") .. moved

[PATCH 4.9 037/105] RDMA/uverbs: Fix the check for port number

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ismail, Mustafa commit 5a7a88f1b488e4ee49eb3d5b82612d4d9ffdf2c3 upstream. The port number is only valid if IB_QP_PORT is set in the mask. So only check port number if

[PATCH 4.9 036/105] sched/cgroup: Move sched_online_group() back into css_online() to fix crash

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konstantin Khlebnikov commit 96b777452d8881480fd5be50112f791c17db4b6b upstream. Commit: 2f5177f0fd7e ("sched/cgroup: Fix/cleanup cgroup teardown/init") .. moved sched_online_group() from

[PATCH 4.9 037/105] RDMA/uverbs: Fix the check for port number

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ismail, Mustafa commit 5a7a88f1b488e4ee49eb3d5b82612d4d9ffdf2c3 upstream. The port number is only valid if IB_QP_PORT is set in the mask. So only check port number if it is valid to prevent

[PATCH 4.9 038/105] ipmi/watchdog: fix watchdog timeout set on reboot

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

[PATCH 4.9 038/105] ipmi/watchdog: fix watchdog timeout set on reboot

4.9-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 4.9 039/105] dentry name snapshots

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

[PATCH 4.9 039/105] dentry name snapshots

4.9-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 4.9 015/105] md/raid5: add thread_group worker async_tx_issue_pending_all

4.9-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] selftests: kselftest framework: add error counter

Some tests track errors in addition to test failures. Add ksft_error counter, ksft_get_error_cnt(), and ksft_test_result_error() API to get the counter value and print error message. Update ksft_print_cnts(), and ksft_test_num() to include error counter. Signed-off-by: Shuah Khan

[PATCH 4.9 015/105] md/raid5: add thread_group worker async_tx_issue_pending_all

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

[PATCH] selftests: kselftest framework: add error counter

Some tests track errors in addition to test failures. Add ksft_error counter, ksft_get_error_cnt(), and ksft_test_result_error() API to get the counter value and print error message. Update ksft_print_cnts(), and ksft_test_num() to include error counter. Signed-off-by: Shuah Khan ---

[PATCH 4.9 012/105] NFSv4.1: Fix a race where CB_NOTIFY_LOCK fails to wake a waiter

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Coddington commit b7dbcc0e433f0f61acb89ed9861ec996be4f2b38 upstream. nfs4_retry_setlk() sets the task's state to TASK_INTERRUPTIBLE within the same region

[PATCH 4.9 012/105] NFSv4.1: Fix a race where CB_NOTIFY_LOCK fails to wake a waiter

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Coddington commit b7dbcc0e433f0f61acb89ed9861ec996be4f2b38 upstream. nfs4_retry_setlk() sets the task's state to TASK_INTERRUPTIBLE within the same region protected by the

[PATCH 4.9 014/105] KVM: PPC: Book3S HV: Enable TM before accessing TM registers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit e47057151422a67ce08747176fa21cb3b526a2c9 upstream. Commit 46a704f8409f ("KVM: PPC: Book3S HV: Preserve userspace HTM state properly", 2017-06-15) added

[PATCH 4.9 014/105] KVM: PPC: Book3S HV: Enable TM before accessing TM registers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit e47057151422a67ce08747176fa21cb3b526a2c9 upstream. Commit 46a704f8409f ("KVM: PPC: Book3S HV: Preserve userspace HTM state properly", 2017-06-15) added code to read

[PATCH 4.9 016/105] drm/vmwgfx: Fix gcc-7.1.1 warning

4.9-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 4.9 016/105] drm/vmwgfx: Fix gcc-7.1.1 warning

4.9-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 4.9 041/105] pstore: Allow prz to control need for locking

4.9-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 4.9 041/105] pstore: Allow prz to control need for locking

4.9-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 4.9 042/105] pstore: Correctly initialize spinlock and flags

4.9-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 4.9 011/105] NFS: invalidate file size when taking a lock.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 442ce0499c0535f8972b68fa1fda357357a5c953 upstream. Prior to commit ca0daa277aca ("NFS: Cache aggressively when file is open for writing"), NFS would

[PATCH 4.9 042/105] pstore: Correctly initialize spinlock and flags

4.9-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 4.9 011/105] NFS: invalidate file size when taking a lock.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 442ce0499c0535f8972b68fa1fda357357a5c953 upstream. Prior to commit ca0daa277aca ("NFS: Cache aggressively when file is open for writing"), NFS would revalidate, or invalidate,

[PATCH 4.9 007/105] parisc: Prevent TLB speculation on flushed pages on CPUs that only support equivalent aliases

4.9-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit ae7a609c34b6fb12328c553b5f9aab26ae74a28e upstream. Helge noticed that we flush the TLB page in flush_cache_page but not in flush_cache_range or

[PATCH 4.9 007/105] parisc: Prevent TLB speculation on flushed pages on CPUs that only support equivalent aliases

4.9-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit ae7a609c34b6fb12328c553b5f9aab26ae74a28e upstream. Helge noticed that we flush the TLB page in flush_cache_page but not in flush_cache_range or flush_cache_mm. For a

[PATCH 4.9 040/105] [media] v4l: s5c73m3: fix negation operator

4.9-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 4.9 040/105] [media] v4l: s5c73m3: fix negation operator

4.9-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 4.9 043/105] pstore: Use dynamic spinlock initializer

4.9-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 4.9 043/105] pstore: Use dynamic spinlock initializer

4.9-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 4.9 055/105] net/mlx4_core: Use-after-free causes a resource leak in flow-steering detach

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit 3b01fe7f91c8e4f9afc4fae3c5af72c14958d2d8 ] mlx4_QP_FLOW_STEERING_DETACH_wrapper first removes the steering rule (which results in

[PATCH 4.9 044/105] net: skb_needs_check() accepts CHECKSUM_NONE for tx

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 6e7bc478c9a006c701c14476ec9d389a484b4864 upstream. My recent change missed fact that UFO would perform a complete UDP checksum before segmenting in

[PATCH 4.9 055/105] net/mlx4_core: Use-after-free causes a resource leak in flow-steering detach

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit 3b01fe7f91c8e4f9afc4fae3c5af72c14958d2d8 ] mlx4_QP_FLOW_STEERING_DETACH_wrapper first removes the steering rule (which results in freeing the rule

[PATCH 4.9 044/105] net: skb_needs_check() accepts CHECKSUM_NONE for tx

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 6e7bc478c9a006c701c14476ec9d389a484b4864 upstream. My recent change missed fact that UFO would perform a complete UDP checksum before segmenting in frags. In this case

[PATCH 4.9 046/105] x86/mce/AMD: Make the init code more robust

4.9-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 4.9 056/105] net/mlx4: Remove BUG_ON from ICM allocation routine

4.9-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 4.9 060/105] drm/msm: Verify that MSM_SUBMIT_BO_FLAGS are set

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

[PATCH 4.9 046/105] x86/mce/AMD: Make the init code more robust

4.9-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 4.9 056/105] net/mlx4: Remove BUG_ON from ICM allocation routine

4.9-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 4.9 060/105] drm/msm: Verify that MSM_SUBMIT_BO_FLAGS are set

4.9-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 else).

[PATCH 4.9 013/105] crypto: authencesn - Fix digest_null crash

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 41cdf7a45389e01991ee31e3301ed83cb3e3f7dc upstream. When authencesn is used together with digest_null a crash will occur on the decrypt path.

[PATCH 4.9 013/105] crypto: authencesn - Fix digest_null crash

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit 41cdf7a45389e01991ee31e3301ed83cb3e3f7dc upstream. When authencesn is used together with digest_null a crash will occur on the decrypt path. This is because normally we

[PATCH 4.9 061/105] vfio-pci: use 32-bit comparisons for register address for gcc-4.5

4.9-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 4.9 061/105] vfio-pci: use 32-bit comparisons for register address for gcc-4.5

4.9-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 4.9 059/105] drm/msm: Put back the vaddr in submit_reloc()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Crouse [ Upstream commit 6490abc4bc35fa4f3bdb9c7e49096943c50e29ea ] The error cases in submit_reloc() need to put back the virtual address of the bo before

[PATCH 4.9 059/105] drm/msm: Put back the vaddr in submit_reloc()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jordan Crouse [ Upstream commit 6490abc4bc35fa4f3bdb9c7e49096943c50e29ea ] The error cases in submit_reloc() need to put back the virtual address of the bo before failling. Add a single

[PATCH 4.9 062/105] irqchip/keystone: Fix "scheduling while atomic" on rt

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Strashko, Grygorii" [ Upstream commit 2f884e6e688a0deb69e6c9552e51aef8b7e3f5f1 ] The below call chain generates "scheduling while atomic" backtrace and causes

[PATCH 4.9 063/105] ASoC: tlv320aic3x: Mark the RESET register as volatile

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi [ Upstream commit 63c3194b82530bd71fd49db84eb7ab656b8d404a ] The RESET register only have one self clearing bit and it should not be cached. If it is

[PATCH 4.9 064/105] spi: dw: Make debugfs name unique between instances

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Phil Reid [ Upstream commit 13288bdf4adbaa6bd1267f10044c1bc25d90ce7f ] Some system have multiple dw devices. Currently the driver uses a fixed name for the debugfs

[PATCH 4.9 062/105] irqchip/keystone: Fix "scheduling while atomic" on rt

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Strashko, Grygorii" [ Upstream commit 2f884e6e688a0deb69e6c9552e51aef8b7e3f5f1 ] The below call chain generates "scheduling while atomic" backtrace and causes system crash when Keystone 2

[PATCH 4.9 063/105] ASoC: tlv320aic3x: Mark the RESET register as volatile

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi [ Upstream commit 63c3194b82530bd71fd49db84eb7ab656b8d404a ] The RESET register only have one self clearing bit and it should not be cached. If it is cached, when we sync the

[PATCH 4.9 064/105] spi: dw: Make debugfs name unique between instances

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Phil Reid [ Upstream commit 13288bdf4adbaa6bd1267f10044c1bc25d90ce7f ] Some system have multiple dw devices. Currently the driver uses a fixed name for the debugfs dir. Append dev name to the

[PATCH 4.9 057/105] net/mlx4_core: Fix raw qp flow steering rules under SRIOV

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit 10b1c04e92229ebeb38ccd0dcf2b6d3ec73c0575 ] Demoting simple flow steering rule priority (for DPDK) was achieved by wrapping FW

[PATCH 4.9 057/105] net/mlx4_core: Fix raw qp flow steering rules under SRIOV

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit 10b1c04e92229ebeb38ccd0dcf2b6d3ec73c0575 ] Demoting simple flow steering rule priority (for DPDK) was achieved by wrapping FW commands

[PATCH 4.9 058/105] drm/msm: Ensure that the hardware write pointer is valid

4.9-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 4.9 065/105] ASoC: nau8825: fix invalid configuration in Pre-Scalar of FLL

4.9-stable review patch. If anyone has any objections, please let me know. -- From: John Hsu [ Upstream commit a1792cda51300e15b03549cccf0b09f3be82e697 ] The clk_ref_div is not configured in the correct position of the register. The patch fixes that

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