[PATCH 4.14 20/21] xfs: dont call xfs_da_shrink_inode with NULL bp

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit bb3d48dcf86a97dc25fe9fc2c11938e19cb4399a upstream. xfs_attr3_leaf_create may have errored out before instantiating a buffer, for example if the blkno is out of range. In

[PATCH 4.14 18/21] xfs: catch inode allocation state mismatch corruption

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit ee457001ed6c6f31ddad69c24c1da8f377d8472d upstream. We recently came across a V4 filesystem causing memory corruption due to a newly allocated inode being setup twice and

[PATCH 4.14 19/21] xfs: validate cached inodes are free when allocated

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit afca6c5b2595fc44383919fba740c194b0b76aff upstream. A recent fuzzed filesystem image cached random dcache corruption when the reproducer was run. This often showed up as

[PATCH 4.14 16/21] nvmet-fc: fix target sgl list on large transfers

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: James Smart commit d082dc1562a2ff0947b214796f12faaa87e816a9 upstream. The existing code to carve up the sg list expected an sg element-per-page which can be very incorrect with iommu's

[PATCH 4.14 14/21] nvme-pci: allocate device queues storage space at probe

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sagi Grimberg commit 147b27e4bd08406a6abebedbb478b431ec197be1 upstream. It may cause race by setting 'nvmeq' in nvme_init_request() because .init_request is called inside switching io

[PATCH 4.14 06/21] nohz: Fix local_timer_softirq_pending()

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Anna-Maria Gleixner commit 80d20d35af1edd632a5e7a3b9c0ab7ceff92769e upstream. local_timer_softirq_pending() checks whether the timer softirq is pending with: local_softirq_pending() &

[PATCH 4.14 17/21] intel_idle: Graceful probe failure when MWAIT is disabled

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Len Brown commit a4c447533a18ee86e07232d6344ba12b1f9c5077 upstream. When MWAIT is disabled, intel_idle refuses to probe. But it may mis-lead the user by blaming this on the model number:

[PATCH 4.14 07/21] nohz: Fix missing tick reprogram when interrupting an inline softirq

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Frederic Weisbecker commit 0a0e0829f990120cef165bbb804237f400953ec2 upstream. The full nohz tick is reprogrammed in irq_exit() only if the exit is not in a nesting interrupt. This stands as

[PATCH 4.14 15/21] nvme-pci: Fix queue double allocations

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Keith Busch commit 62314e405fa101dbb82563394f9dfc225e3f1167 upstream. The queue count says the highest queue that's been allocated, so don't reallocate a queue lower than that. Fixes:

[PATCH 4.14 21/21] jfs: Fix inconsistency between memory allocation and ea_buf->max_size

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Shankara Pailoor commit 92d34134193e5b129dc24f8d79cb9196626e8d7a upstream. The code is assuming the buffer is max_size length, but we weren't allocating enough space for it. Signed-off-by:

[PATCH 4.14 20/21] xfs: dont call xfs_da_shrink_inode with NULL bp

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit bb3d48dcf86a97dc25fe9fc2c11938e19cb4399a upstream. xfs_attr3_leaf_create may have errored out before instantiating a buffer, for example if the blkno is out of range. In

[PATCH 4.14 18/21] xfs: catch inode allocation state mismatch corruption

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit ee457001ed6c6f31ddad69c24c1da8f377d8472d upstream. We recently came across a V4 filesystem causing memory corruption due to a newly allocated inode being setup twice and

[PATCH 4.14 19/21] xfs: validate cached inodes are free when allocated

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit afca6c5b2595fc44383919fba740c194b0b76aff upstream. A recent fuzzed filesystem image cached random dcache corruption when the reproducer was run. This often showed up as

[PATCH 4.14 16/21] nvmet-fc: fix target sgl list on large transfers

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: James Smart commit d082dc1562a2ff0947b214796f12faaa87e816a9 upstream. The existing code to carve up the sg list expected an sg element-per-page which can be very incorrect with iommu's

[PATCH 4.14 14/21] nvme-pci: allocate device queues storage space at probe

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sagi Grimberg commit 147b27e4bd08406a6abebedbb478b431ec197be1 upstream. It may cause race by setting 'nvmeq' in nvme_init_request() because .init_request is called inside switching io

[PATCH 4.14 06/21] nohz: Fix local_timer_softirq_pending()

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Anna-Maria Gleixner commit 80d20d35af1edd632a5e7a3b9c0ab7ceff92769e upstream. local_timer_softirq_pending() checks whether the timer softirq is pending with: local_softirq_pending() &

[PATCH 4.14 08/21] netlink: Dont shift on 64 for ngroups

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Safonov commit 91874ecf32e41b5d86a4cb9d60e0bee50d828058 upstream. It's legal to have 64 groups for netlink_sock. As user-supplied nladdr->nl_groups is __u32, it's possible to

[PATCH 4.14 11/21] ring_buffer: tracing: Inherit the tracing setting to next ring buffer

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 73c8d8945505acdcbae137c2e00a1232e0be709f upstream. Maintain the tracing on/off setting of the ring_buffer when switching to the trace buffer snapshot. Taking a

[PATCH 4.14 09/21] ext4: fix false negatives *and* false positives in ext4_check_descriptors()

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit 44de022c4382541cebdd6de4465d1f4f465ff1dd upstream. Ext4_check_descriptors() was getting called before s_gdb_count was initialized. So for file systems w/o the meta_bg

[PATCH 4.14 08/21] netlink: Dont shift on 64 for ngroups

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Safonov commit 91874ecf32e41b5d86a4cb9d60e0bee50d828058 upstream. It's legal to have 64 groups for netlink_sock. As user-supplied nladdr->nl_groups is __u32, it's possible to

[PATCH 4.14 11/21] ring_buffer: tracing: Inherit the tracing setting to next ring buffer

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 73c8d8945505acdcbae137c2e00a1232e0be709f upstream. Maintain the tracing on/off setting of the ring_buffer when switching to the trace buffer snapshot. Taking a

[PATCH 4.14 09/21] ext4: fix false negatives *and* false positives in ext4_check_descriptors()

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit 44de022c4382541cebdd6de4465d1f4f465ff1dd upstream. Ext4_check_descriptors() was getting called before s_gdb_count was initialized. So for file systems w/o the meta_bg

[PATCH 4.14 10/21] ACPI / PCI: Bail early in acpi_pci_add_bus() if there is no ACPI handle

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov commit a0040c0145945d3bd203df8fa97f6dfa819f3f7d upstream. Hyper-V instances support PCI pass-through which is implemented through PV pci-hyperv driver. When a device is

[PATCH 4.14 10/21] ACPI / PCI: Bail early in acpi_pci_add_bus() if there is no ACPI handle

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov commit a0040c0145945d3bd203df8fa97f6dfa819f3f7d upstream. Hyper-V instances support PCI pass-through which is implemented through PV pci-hyperv driver. When a device is

[PATCH 4.14 03/21] scsi: qla2xxx: Fix ISP recovery on unload

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit b08abbd9f5996309f021684f9ca74da30dcca36a upstream. During unload process, the chip can encounter problem where a FW dump would be captured. For this case, the full reset

[PATCH 4.14 00/21] 4.14.62-stable review

2018-08-07 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.62 release. There are 21 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 Thu Aug 9 17:23:22 UTC 2018. Anything

[PATCH 4.14 03/21] scsi: qla2xxx: Fix ISP recovery on unload

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit b08abbd9f5996309f021684f9ca74da30dcca36a upstream. During unload process, the chip can encounter problem where a FW dump would be captured. For this case, the full reset

[PATCH 4.14 00/21] 4.14.62-stable review

2018-08-07 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.62 release. There are 21 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 Thu Aug 9 17:23:22 UTC 2018. Anything

[PATCH 4.14 05/21] genirq: Make force irq threading setup more robust

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit d1f0301beef5efbfa1fe0f0edbea01863d5d upstream. The support of force threading interrupts which are set up with both a primary and a threaded handler wreckaged the

[PATCH 4.14 01/21] scsi: qla2xxx: Fix unintialized List head crash

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit e3dde080ebbdbb4bda8eee35d770714fee8c59ac upstream. In case of IOCB Queue full or system where memory is low and driver receives large number of RSCN storm, the stale sp

[PATCH 4.14 05/21] genirq: Make force irq threading setup more robust

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit d1f0301beef5efbfa1fe0f0edbea01863d5d upstream. The support of force threading interrupts which are set up with both a primary and a threaded handler wreckaged the

[PATCH 4.14 01/21] scsi: qla2xxx: Fix unintialized List head crash

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit e3dde080ebbdbb4bda8eee35d770714fee8c59ac upstream. In case of IOCB Queue full or system where memory is low and driver receives large number of RSCN storm, the stale sp

[PATCH 4.14 02/21] scsi: qla2xxx: Fix NPIV deletion by calling wait_for_sess_deletion

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit efa93f48fa9d423fda166bc3b6c0cbb09682492e upstream. Add wait for session deletion to finish before freeing an NPIV scsi host. Fixes: 726b85487067 ("qla2xxx: Add framework

[PATCH 4.17 18/18] jfs: Fix inconsistency between memory allocation and ea_buf->max_size

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Shankara Pailoor commit 92d34134193e5b129dc24f8d79cb9196626e8d7a upstream. The code is assuming the buffer is max_size length, but we weren't allocating enough space for it. Signed-off-by:

[PATCH 4.14 02/21] scsi: qla2xxx: Fix NPIV deletion by calling wait_for_sess_deletion

2018-08-07 Thread Greg Kroah-Hartman
4.14-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit efa93f48fa9d423fda166bc3b6c0cbb09682492e upstream. Add wait for session deletion to finish before freeing an NPIV scsi host. Fixes: 726b85487067 ("qla2xxx: Add framework

[PATCH 4.17 18/18] jfs: Fix inconsistency between memory allocation and ea_buf->max_size

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Shankara Pailoor commit 92d34134193e5b129dc24f8d79cb9196626e8d7a upstream. The code is assuming the buffer is max_size length, but we weren't allocating enough space for it. Signed-off-by:

[PATCH 4.17 10/18] nohz: Fix missing tick reprogram when interrupting an inline softirq

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Frederic Weisbecker commit 0a0e0829f990120cef165bbb804237f400953ec2 upstream. The full nohz tick is reprogrammed in irq_exit() only if the exit is not in a nesting interrupt. This stands as

[PATCH 4.17 10/18] nohz: Fix missing tick reprogram when interrupting an inline softirq

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Frederic Weisbecker commit 0a0e0829f990120cef165bbb804237f400953ec2 upstream. The full nohz tick is reprogrammed in irq_exit() only if the exit is not in a nesting interrupt. This stands as

[PATCH 4.17 12/18] ring_buffer: tracing: Inherit the tracing setting to next ring buffer

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 73c8d8945505acdcbae137c2e00a1232e0be709f upstream. Maintain the tracing on/off setting of the ring_buffer when switching to the trace buffer snapshot. Taking a

[PATCH 4.17 14/18] Btrfs: fix file data corruption after cloning a range and fsync

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit bd3599a0e142cd73edd3b6801068ac3f48ac771a upstream. When we clone a range into a file we can end up dropping existing extent maps (or trimming them) and replacing them

[PATCH 4.17 15/18] Partially revert "block: fail op_is_write() requests to read-only partitions"

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit a32e236eb93e62a0f692e79b7c3c9636689559b9 upstream. It turns out that commit 721c7fc701c7 ("block: fail op_is_write() requests to read-only partitions"), while obviously

[PATCH 4.17 14/18] Btrfs: fix file data corruption after cloning a range and fsync

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit bd3599a0e142cd73edd3b6801068ac3f48ac771a upstream. When we clone a range into a file we can end up dropping existing extent maps (or trimming them) and replacing them

[PATCH 4.17 12/18] ring_buffer: tracing: Inherit the tracing setting to next ring buffer

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 73c8d8945505acdcbae137c2e00a1232e0be709f upstream. Maintain the tracing on/off setting of the ring_buffer when switching to the trace buffer snapshot. Taking a

[PATCH 4.17 15/18] Partially revert "block: fail op_is_write() requests to read-only partitions"

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit a32e236eb93e62a0f692e79b7c3c9636689559b9 upstream. It turns out that commit 721c7fc701c7 ("block: fail op_is_write() requests to read-only partitions"), while obviously

[PATCH 4.17 17/18] xfs: validate cached inodes are free when allocated

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit afca6c5b2595fc44383919fba740c194b0b76aff upstream. A recent fuzzed filesystem image cached random dcache corruption when the reproducer was run. This often showed up as

[PATCH 4.17 16/18] xfs: dont call xfs_da_shrink_inode with NULL bp

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit bb3d48dcf86a97dc25fe9fc2c11938e19cb4399a upstream. xfs_attr3_leaf_create may have errored out before instantiating a buffer, for example if the blkno is out of range. In

[PATCH 4.17 00/18] 4.17.14-stable review

2018-08-07 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.17.14 release. There are 18 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 Thu Aug 9 17:23:05 UTC 2018. Anything

[PATCH 4.17 11/18] netlink: Dont shift on 64 for ngroups

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Safonov commit 91874ecf32e41b5d86a4cb9d60e0bee50d828058 upstream. It's legal to have 64 groups for netlink_sock. As user-supplied nladdr->nl_groups is __u32, it's possible to

[PATCH 4.17 17/18] xfs: validate cached inodes are free when allocated

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit afca6c5b2595fc44383919fba740c194b0b76aff upstream. A recent fuzzed filesystem image cached random dcache corruption when the reproducer was run. This often showed up as

[PATCH 4.17 16/18] xfs: dont call xfs_da_shrink_inode with NULL bp

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit bb3d48dcf86a97dc25fe9fc2c11938e19cb4399a upstream. xfs_attr3_leaf_create may have errored out before instantiating a buffer, for example if the blkno is out of range. In

[PATCH 4.17 00/18] 4.17.14-stable review

2018-08-07 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.17.14 release. There are 18 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 Thu Aug 9 17:23:05 UTC 2018. Anything

[PATCH 4.17 11/18] netlink: Dont shift on 64 for ngroups

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Safonov commit 91874ecf32e41b5d86a4cb9d60e0bee50d828058 upstream. It's legal to have 64 groups for netlink_sock. As user-supplied nladdr->nl_groups is __u32, it's possible to

[PATCH 4.17 08/18] perf/x86/intel/uncore: Fix hardcoded index of Broadwell extra PCI devices

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Kan Liang commit 156c8b58ef5cfd97245928c95669fd4cb0f9c388 upstream. Masayoshi Mizuma reported that a warning message is shown while a CPU is hot-removed on Broadwell servers: WARNING: CPU:

[PATCH 4.17 07/18] genirq: Make force irq threading setup more robust

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit d1f0301beef5efbfa1fe0f0edbea01863d5d upstream. The support of force threading interrupts which are set up with both a primary and a threaded handler wreckaged the

[PATCH 4.17 09/18] nohz: Fix local_timer_softirq_pending()

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Anna-Maria Gleixner commit 80d20d35af1edd632a5e7a3b9c0ab7ceff92769e upstream. local_timer_softirq_pending() checks whether the timer softirq is pending with: local_softirq_pending() &

[PATCH 4.17 08/18] perf/x86/intel/uncore: Fix hardcoded index of Broadwell extra PCI devices

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Kan Liang commit 156c8b58ef5cfd97245928c95669fd4cb0f9c388 upstream. Masayoshi Mizuma reported that a warning message is shown while a CPU is hot-removed on Broadwell servers: WARNING: CPU:

[PATCH 4.17 07/18] genirq: Make force irq threading setup more robust

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit d1f0301beef5efbfa1fe0f0edbea01863d5d upstream. The support of force threading interrupts which are set up with both a primary and a threaded handler wreckaged the

[PATCH 4.17 09/18] nohz: Fix local_timer_softirq_pending()

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Anna-Maria Gleixner commit 80d20d35af1edd632a5e7a3b9c0ab7ceff92769e upstream. local_timer_softirq_pending() checks whether the timer softirq is pending with: local_softirq_pending() &

[PATCH 4.17 04/18] scsi: qla2xxx: Fix ISP recovery on unload

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit b08abbd9f5996309f021684f9ca74da30dcca36a upstream. During unload process, the chip can encounter problem where a FW dump would be captured. For this case, the full reset

[PATCH 4.17 05/18] scsi: qla2xxx: Return error when TMF returns

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Anil Gurumurthy commit b4146c4929ef61d5afca011474d59d0918a0cd82 upstream. Propagate the task management completion status properly to avoid unnecessary waits for commands to complete. Fixes:

[PATCH 4.17 06/18] jfs: Fix usercopy whitelist for inline inode data

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 961b33c244e5ba1543ae26270a1ba29f29c2db83 upstream. Bart Massey reported what turned out to be a usercopy whitelist false positive in JFS when symlink contents exceeded 128

[PATCH 4.17 04/18] scsi: qla2xxx: Fix ISP recovery on unload

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit b08abbd9f5996309f021684f9ca74da30dcca36a upstream. During unload process, the chip can encounter problem where a FW dump would be captured. For this case, the full reset

[PATCH 4.17 05/18] scsi: qla2xxx: Return error when TMF returns

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Anil Gurumurthy commit b4146c4929ef61d5afca011474d59d0918a0cd82 upstream. Propagate the task management completion status properly to avoid unnecessary waits for commands to complete. Fixes:

[PATCH 4.17 06/18] jfs: Fix usercopy whitelist for inline inode data

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 961b33c244e5ba1543ae26270a1ba29f29c2db83 upstream. Bart Massey reported what turned out to be a usercopy whitelist false positive in JFS when symlink contents exceeded 128

[PATCH 4.17 03/18] scsi: qla2xxx: Fix driver unload by shutting down chip

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit 45235022da9925b2b070c0139629233173e50089 upstream. Use chip shutdown at the start of unload to stop all DMA + traffic and bring down the laser. This prevents any link

[PATCH 4.17 02/18] scsi: qla2xxx: Fix NPIV deletion by calling wait_for_sess_deletion

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit efa93f48fa9d423fda166bc3b6c0cbb09682492e upstream. Add wait for session deletion to finish before freeing an NPIV scsi host. Fixes: 726b85487067 ("qla2xxx: Add framework

[PATCH 4.17 03/18] scsi: qla2xxx: Fix driver unload by shutting down chip

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit 45235022da9925b2b070c0139629233173e50089 upstream. Use chip shutdown at the start of unload to stop all DMA + traffic and bring down the laser. This prevents any link

[PATCH 4.17 02/18] scsi: qla2xxx: Fix NPIV deletion by calling wait_for_sess_deletion

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit efa93f48fa9d423fda166bc3b6c0cbb09682492e upstream. Add wait for session deletion to finish before freeing an NPIV scsi host. Fixes: 726b85487067 ("qla2xxx: Add framework

[PATCH 4.17 01/18] scsi: qla2xxx: Fix unintialized List head crash

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit e3dde080ebbdbb4bda8eee35d770714fee8c59ac upstream. In case of IOCB Queue full or system where memory is low and driver receives large number of RSCN storm, the stale sp

[PATCH 4.17 01/18] scsi: qla2xxx: Fix unintialized List head crash

2018-08-07 Thread Greg Kroah-Hartman
4.17-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit e3dde080ebbdbb4bda8eee35d770714fee8c59ac upstream. In case of IOCB Queue full or system where memory is low and driver receives large number of RSCN storm, the stale sp

Re: [PATCH v2] proc: add percpu populated pages count to meminfo

2018-08-07 Thread Tejun Heo
Hello, Dennis. On Tue, Aug 07, 2018 at 11:47:23AM -0700, Dennis Zhou wrote: > From: "Dennis Zhou (Facebook)" > > Currently, percpu memory only exposes allocation and utilization > information via debugfs. This more or less is only really useful for > understanding the fragmentation and

Re: [PATCH v2] proc: add percpu populated pages count to meminfo

2018-08-07 Thread Tejun Heo
Hello, Dennis. On Tue, Aug 07, 2018 at 11:47:23AM -0700, Dennis Zhou wrote: > From: "Dennis Zhou (Facebook)" > > Currently, percpu memory only exposes allocation and utilization > information via debugfs. This more or less is only really useful for > understanding the fragmentation and

Re: [PATCH 4/9] dt-bindings: reset: Add binding constants for Actions Semi S900 RMU

2018-08-07 Thread Rob Herring
On Sat, Jul 28, 2018 at 12:15:22AM +0530, Manivannan Sadhasivam wrote: > Add device tree binding constants for Actions Semi S900 SoC Reset > Management Unit (RMU). > > Signed-off-by: Manivannan Sadhasivam > --- > .../dt-bindings/reset/actions,s900-reset.h| 65 +++ > 1 file

Re: [PATCH 4/9] dt-bindings: reset: Add binding constants for Actions Semi S900 RMU

2018-08-07 Thread Rob Herring
On Sat, Jul 28, 2018 at 12:15:22AM +0530, Manivannan Sadhasivam wrote: > Add device tree binding constants for Actions Semi S900 SoC Reset > Management Unit (RMU). > > Signed-off-by: Manivannan Sadhasivam > --- > .../dt-bindings/reset/actions,s900-reset.h| 65 +++ > 1 file

Re: [PATCH 3/9] dt-bindings: reset: Add binding constants for Actions Semi S700 RMU

2018-08-07 Thread Rob Herring
On Sat, Jul 28, 2018 at 12:15:21AM +0530, Manivannan Sadhasivam wrote: > Add device tree binding constants for Actions Semi S700 SoC Reset > Management Unit (RMU). > > Signed-off-by: Manivannan Sadhasivam > --- > .../dt-bindings/reset/actions,s700-reset.h| 34 +++ > 1 file

Re: [PATCH 3/9] dt-bindings: reset: Add binding constants for Actions Semi S700 RMU

2018-08-07 Thread Rob Herring
On Sat, Jul 28, 2018 at 12:15:21AM +0530, Manivannan Sadhasivam wrote: > Add device tree binding constants for Actions Semi S700 SoC Reset > Management Unit (RMU). > > Signed-off-by: Manivannan Sadhasivam > --- > .../dt-bindings/reset/actions,s700-reset.h| 34 +++ > 1 file

Re: [PATCH 2/9] dt-bindings: clock: Add reset controller bindings for Actions Semi Owl SoCs

2018-08-07 Thread Rob Herring
On Sat, Jul 28, 2018 at 12:15:20AM +0530, Manivannan Sadhasivam wrote: > Add Reset Controller bindings to clock bindings for Actions Semi Owl > SoCs, S700 and S900. > > Signed-off-by: Manivannan Sadhasivam > --- > Documentation/devicetree/bindings/clock/actions,owl-cmu.txt | 2 ++ > 1 file

Re: [PATCH 2/9] dt-bindings: clock: Add reset controller bindings for Actions Semi Owl SoCs

2018-08-07 Thread Rob Herring
On Sat, Jul 28, 2018 at 12:15:20AM +0530, Manivannan Sadhasivam wrote: > Add Reset Controller bindings to clock bindings for Actions Semi Owl > SoCs, S700 and S900. > > Signed-off-by: Manivannan Sadhasivam > --- > Documentation/devicetree/bindings/clock/actions,owl-cmu.txt | 2 ++ > 1 file

[PATCH v2] proc: add percpu populated pages count to meminfo

2018-08-07 Thread Dennis Zhou
From: "Dennis Zhou (Facebook)" Currently, percpu memory only exposes allocation and utilization information via debugfs. This more or less is only really useful for understanding the fragmentation and allocation information at a per-chunk level with a few global counters. This is also gated

[PATCH v2] proc: add percpu populated pages count to meminfo

2018-08-07 Thread Dennis Zhou
From: "Dennis Zhou (Facebook)" Currently, percpu memory only exposes allocation and utilization information via debugfs. This more or less is only really useful for understanding the fragmentation and allocation information at a per-chunk level with a few global counters. This is also gated

Re: [PATCH 0/9] Add Reset Controller support for Actions Semi Owl SoCs

2018-08-07 Thread Rob Herring
On Mon, Jul 30, 2018 at 08:41:31PM +0530, Manivannan Sadhasivam wrote: > Hi Andreas, > > On Mon, Jul 30, 2018 at 12:26:07PM +0200, Andreas Färber wrote: > > Hi Mani, > > > > Am 27.07.2018 um 20:45 schrieb Manivannan Sadhasivam: > > > This patchset adds Reset Controller (RMU) support for Actions

Re: [PATCH 0/9] Add Reset Controller support for Actions Semi Owl SoCs

2018-08-07 Thread Rob Herring
On Mon, Jul 30, 2018 at 08:41:31PM +0530, Manivannan Sadhasivam wrote: > Hi Andreas, > > On Mon, Jul 30, 2018 at 12:26:07PM +0200, Andreas Färber wrote: > > Hi Mani, > > > > Am 27.07.2018 um 20:45 schrieb Manivannan Sadhasivam: > > > This patchset adds Reset Controller (RMU) support for Actions

Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake

2018-08-07 Thread Andi Kleen
On Tue, Aug 07, 2018 at 07:48:51PM +0200, Peter Zijlstra wrote: > On Tue, Aug 07, 2018 at 10:35:42AM -0700, Dave Hansen wrote: > > On 08/07/2018 10:17 AM, kan.li...@linux.intel.com wrote: > > > Denverton and Gemini Lake are platform names and should not be used for > > > Processor Family stuff.

Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake

2018-08-07 Thread Andi Kleen
On Tue, Aug 07, 2018 at 07:48:51PM +0200, Peter Zijlstra wrote: > On Tue, Aug 07, 2018 at 10:35:42AM -0700, Dave Hansen wrote: > > On 08/07/2018 10:17 AM, kan.li...@linux.intel.com wrote: > > > Denverton and Gemini Lake are platform names and should not be used for > > > Processor Family stuff.

Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake

2018-08-07 Thread Andi Kleen
On Tue, Aug 07, 2018 at 10:17:27AM -0700, kan.li...@linux.intel.com wrote: > From: Kan Liang > > Denverton and Gemini Lake are platform names and should not be used for > Processor Family stuff. The microarchitecture codename should be used. > > DENVERTON is Goldmont server SoC. Rename

Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake

2018-08-07 Thread Andi Kleen
On Tue, Aug 07, 2018 at 10:17:27AM -0700, kan.li...@linux.intel.com wrote: > From: Kan Liang > > Denverton and Gemini Lake are platform names and should not be used for > Processor Family stuff. The microarchitecture codename should be used. > > DENVERTON is Goldmont server SoC. Rename

Re: [PATCH] rtmutex: Drop pointless static qualifier in rt_mutex_adjust_prio_chain()

2018-08-07 Thread kbuild test robot
Hi Mao, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on tip/locking/core] [also build test WARNING on v4.18-rc8 next-20180807] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day

Re: [PATCH] rtmutex: Drop pointless static qualifier in rt_mutex_adjust_prio_chain()

2018-08-07 Thread kbuild test robot
Hi Mao, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on tip/locking/core] [also build test WARNING on v4.18-rc8 next-20180807] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day

Re: [PATCH 2/3] x86/mm/pti: Don't clear permissions in pti_clone_pmd()

2018-08-07 Thread Dave Hansen
On 08/07/2018 03:24 AM, Joerg Roedel wrote: > The function sets the global-bit on cloned PMD entries, > which only makes sense when the permissions are identical > between the user and the kernel page-table. > > Further, only write-permissions are cleared for entry-text > and kernel-text

Re: [PATCH 2/3] x86/mm/pti: Don't clear permissions in pti_clone_pmd()

2018-08-07 Thread Dave Hansen
On 08/07/2018 03:24 AM, Joerg Roedel wrote: > The function sets the global-bit on cloned PMD entries, > which only makes sense when the permissions are identical > between the user and the kernel page-table. > > Further, only write-permissions are cleared for entry-text > and kernel-text

Re: [PATCH] x86/pkeys: Explicitly treat PK #PF on kernel address as a bad area

2018-08-07 Thread Dave Hansen
On 08/07/2018 10:29 AM, Sean Christopherson wrote: > if (unlikely(fault_in_kernel_space(address))) { > + /* > + * We should never encounter a protection keys fault on a > + * kernel address as kernel address are always mapped with > + *

Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake

2018-08-07 Thread Dave Hansen
On 08/07/2018 10:48 AM, Peter Zijlstra wrote: > On Tue, Aug 07, 2018 at 10:35:42AM -0700, Dave Hansen wrote: >> On 08/07/2018 10:17 AM, kan.li...@linux.intel.com wrote: >>> Denverton and Gemini Lake are platform names and should not be used for >>> Processor Family stuff. The microarchitecture

Re: [PATCH] x86/pkeys: Explicitly treat PK #PF on kernel address as a bad area

2018-08-07 Thread Dave Hansen
On 08/07/2018 10:29 AM, Sean Christopherson wrote: > if (unlikely(fault_in_kernel_space(address))) { > + /* > + * We should never encounter a protection keys fault on a > + * kernel address as kernel address are always mapped with > + *

Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake

2018-08-07 Thread Dave Hansen
On 08/07/2018 10:48 AM, Peter Zijlstra wrote: > On Tue, Aug 07, 2018 at 10:35:42AM -0700, Dave Hansen wrote: >> On 08/07/2018 10:17 AM, kan.li...@linux.intel.com wrote: >>> Denverton and Gemini Lake are platform names and should not be used for >>> Processor Family stuff. The microarchitecture

Re: [PATCH] tracing: Partial revert of "tracing: Centralize preemptirq tracepoints and unify their usage"

2018-08-07 Thread Steven Rostedt
On Tue, 7 Aug 2018 12:35:08 +0200 Peter Zijlstra wrote: > On Mon, Aug 06, 2018 at 09:54:32PM -0400, Steven Rostedt wrote: > > > > [ Peter, you OK with this patch? It just makes lockdep call its helper > > functions directly like it did before. ] > > Yeah, I suppose :-) Can I add your

Re: [PATCH] tracing: Partial revert of "tracing: Centralize preemptirq tracepoints and unify their usage"

2018-08-07 Thread Steven Rostedt
On Tue, 7 Aug 2018 12:35:08 +0200 Peter Zijlstra wrote: > On Mon, Aug 06, 2018 at 09:54:32PM -0400, Steven Rostedt wrote: > > > > [ Peter, you OK with this patch? It just makes lockdep call its helper > > functions directly like it did before. ] > > Yeah, I suppose :-) Can I add your

Re: [PATCH v3 RESEND 2/2] tpm: add support for nonblocking operation

2018-08-07 Thread Jason Gunthorpe
On Mon, Aug 06, 2018 at 04:05:48PM -0700, James Bottomley wrote: > > @@ -118,25 +155,48 @@ ssize_t tpm_common_write(struct file *file, > > const char __user *buf, > >    * the char dev is held open. > >    */ > >   if (tpm_try_get_ops(priv->chip)) { > > -

Re: [PATCH v3 RESEND 2/2] tpm: add support for nonblocking operation

2018-08-07 Thread Jason Gunthorpe
On Mon, Aug 06, 2018 at 04:05:48PM -0700, James Bottomley wrote: > > @@ -118,25 +155,48 @@ ssize_t tpm_common_write(struct file *file, > > const char __user *buf, > >    * the char dev is held open. > >    */ > >   if (tpm_try_get_ops(priv->chip)) { > > -

Re: [PATCH 4/4] remoteproc: qcom: q6v5-pil: Add PDC restart for modem on SDM845 SoCs

2018-08-07 Thread Rob Herring
On Fri, Jul 27, 2018 at 08:58:11PM +0530, Sibi Sankar wrote: > In the presence of a PDC block working with subsystem RSC, > assert/deassert PDC restart in modem start/stop path. > > Signed-off-by: Sibi Sankar > --- > .../bindings/remoteproc/qcom,q6v5.txt | 4 +++ Please split bindings

Re: [PATCH 4/4] remoteproc: qcom: q6v5-pil: Add PDC restart for modem on SDM845 SoCs

2018-08-07 Thread Rob Herring
On Fri, Jul 27, 2018 at 08:58:11PM +0530, Sibi Sankar wrote: > In the presence of a PDC block working with subsystem RSC, > assert/deassert PDC restart in modem start/stop path. > > Signed-off-by: Sibi Sankar > --- > .../bindings/remoteproc/qcom,q6v5.txt | 4 +++ Please split bindings

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