Re: [lockdep] b09be676e0 BUG: unable to handle kernel NULL pointer dereference at 000001f2

On Wed, Oct 11, 2017 at 09:56:05AM +0900, Byungchul Park wrote: > Thank you very much for explaining it in detail. > > But let's shift a viewpoint. Precisely, I didn't want to work on locks > but *waiters* becasue dependancies causing deadlocks only can be created > by waiters - nevertheless I

[PATCH] of: overlay: move resolve phandles into of_overlay_apply()

From: Frank Rowand Move more code into of_overlay_apply() so that it does not have to be duplicated by each caller of of_overlay_apply(). The test in of_resolve_phandles() that the overlay tree is detached is temporarily disabled so that old style overlay unittests do not fail. Signed-off-by:

[GIT PULL for-4.4 03/25] irqchip/crossbar: Fix incorrect type of local variables

From: Franck Demathieu [ Upstream commit b28ace12661fbcfd90959c1e84ff5a85113a82a1 ] The max and entry variables are unsigned according to the dt-bindings. Fix following 3 sparse issues (-Wtypesign): drivers/irqchip/irq-crossbar.c:222:52: warning: incorrect type in

[GIT PULL for-4.9 44/48] drm/nouveau/gr/gf100-: fix ccache error logging

From: Ben Skeggs [ Upstream commit 1894054dc1b6e4395048b2c0f28832a3f4320fd3 ] Signed-off-by: Ben Skeggs Signed-off-by: Sasha Levin --- drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c | 2 +- 1 file changed, 1 insertion(+), 1

[GIT PULL for-4.4 03/25] irqchip/crossbar: Fix incorrect type of local variables

From: Franck Demathieu [ Upstream commit b28ace12661fbcfd90959c1e84ff5a85113a82a1 ] The max and entry variables are unsigned according to the dt-bindings. Fix following 3 sparse issues (-Wtypesign): drivers/irqchip/irq-crossbar.c:222:52: warning: incorrect type in argument 3 (different

[GIT PULL for-4.9 44/48] drm/nouveau/gr/gf100-: fix ccache error logging

From: Ben Skeggs [ Upstream commit 1894054dc1b6e4395048b2c0f28832a3f4320fd3 ] Signed-off-by: Ben Skeggs Signed-off-by: Sasha Levin --- drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[GIT PULL for-4.9 32/48] i2c: at91: ensure state is restored after suspending

From: Alexandre Belloni [ Upstream commit e3ccc921b7d8fd1fcd10a00720e09823d8078666 ] When going to suspend, the I2C registers may be lost because the power to VDDcore is cut. Restore them when resuming. Signed-off-by: Alexandre Belloni

[GIT PULL for-4.9 32/48] i2c: at91: ensure state is restored after suspending

From: Alexandre Belloni [ Upstream commit e3ccc921b7d8fd1fcd10a00720e09823d8078666 ] When going to suspend, the I2C registers may be lost because the power to VDDcore is cut. Restore them when resuming. Signed-off-by: Alexandre Belloni Acked-by: Ludovic Desroches Signed-off-by: Wolfram Sang

[GIT PULL for-4.9 45/48] regulator: core: Resolve supplies before disabling unused regulators

From: Javier Martinez Canillas [ Upstream commit 3827b64dba27ebadb4faf51f2c91143e01ba1f6d ] After commit 66d228a2bf03 ("regulator: core: Don't use regulators as supplies until the parent is bound"), input supplies aren't resolved if the input supplies parent device has

[GIT PULL for-4.9 45/48] regulator: core: Resolve supplies before disabling unused regulators

From: Javier Martinez Canillas [ Upstream commit 3827b64dba27ebadb4faf51f2c91143e01ba1f6d ] After commit 66d228a2bf03 ("regulator: core: Don't use regulators as supplies until the parent is bound"), input supplies aren't resolved if the input supplies parent device has not been bound. This

[GIT PULL for-4.4 06/25] net/mlx4_en: fix overflow in mlx4_en_init_timestamp()

From: Eric Dumazet [ Upstream commit 47d3a07528ecbbccf53bc4390d70b4e3d1c04fcf ] The cited commit makes a great job of finding optimal shift/multiplier values assuming a 10 seconds wrap around, but forgot to change the overflow_period computation. It overflows in

[GIT PULL for-4.4 06/25] net/mlx4_en: fix overflow in mlx4_en_init_timestamp()

From: Eric Dumazet [ Upstream commit 47d3a07528ecbbccf53bc4390d70b4e3d1c04fcf ] The cited commit makes a great job of finding optimal shift/multiplier values assuming a 10 seconds wrap around, but forgot to change the overflow_period computation. It overflows in cyclecounter_cyc2ns(), and the

[GIT PULL for-4.9 34/48] ceph: fix bogus endianness change in ceph_ioctl_set_layout

From: Jeff Layton [ Upstream commit 24c149ad6914d349d8b64749f20f3f8ea5031fe0 ] sparse says: fs/ceph/ioctl.c:100:28: warning: cast to restricted __le64 preferred_osd is a __s64 so we don't need to do any conversion. Also, just remove the cast in ceph_ioctl_get_layout as

[GIT PULL for-4.9 34/48] ceph: fix bogus endianness change in ceph_ioctl_set_layout

From: Jeff Layton [ Upstream commit 24c149ad6914d349d8b64749f20f3f8ea5031fe0 ] sparse says: fs/ceph/ioctl.c:100:28: warning: cast to restricted __le64 preferred_osd is a __s64 so we don't need to do any conversion. Also, just remove the cast in ceph_ioctl_get_layout as it's not needed.

[GIT PULL for-4.9 35/48] ceph: clean up unsafe d_parent accesses in build_dentry_path

From: Jeff Layton [ Upstream commit c6b0b656ca24ede6657abb4a2cd910fa9c1879ba ] While we hold a reference to the dentry when build_dentry_path is called, we could end up racing with a rename that changes d_parent. Handle that situation correctly, by using the rcu_read_lock to

[GIT PULL for-4.9 35/48] ceph: clean up unsafe d_parent accesses in build_dentry_path

From: Jeff Layton [ Upstream commit c6b0b656ca24ede6657abb4a2cd910fa9c1879ba ] While we hold a reference to the dentry when build_dentry_path is called, we could end up racing with a rename that changes d_parent. Handle that situation correctly, by using the rcu_read_lock to ensure that the

[GIT PULL for-4.4 10/25] f2fs: do not wait for writeback in write_begin

From: Jaegeuk Kim [ Upstream commit 86d54795c94532075d862aa0a79f0c981dab4bdd ] Otherwise we can get livelock like below. [79880.428136] dbench D0 18405 18404 0x [79880.428139] Call Trace: [79880.428142] __schedule+0x219/0x6b0 [79880.428144]

[GIT PULL for-4.9 48/48] cpufreq: CPPC: add ACPI_PROCESSOR dependency

From: Arnd Bergmann [ Upstream commit a578884fa0d2768f13d37c6591a9e1ed600482d3 ] Without the Kconfig dependency, we can get this warning: warning: ACPI_CPPC_CPUFREQ selects ACPI_CPPC_LIB which has unmet direct dependencies (ACPI && ACPI_PROCESSOR) Fixes: 5477fb3bd1e8 (ACPI /

[GIT PULL for-4.9 36/48] uapi: fix linux/rds.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit feb0869d90e51ce8b6fd8a46588465b1b5a26d09 ] Consistently use types from linux/types.h to fix the following linux/rds.h userspace compilation errors: /usr/include/linux/rds.h:106:2: error: unknown type name 'uint8_t' uint8_t

[GIT PULL for-4.4 10/25] f2fs: do not wait for writeback in write_begin

From: Jaegeuk Kim [ Upstream commit 86d54795c94532075d862aa0a79f0c981dab4bdd ] Otherwise we can get livelock like below. [79880.428136] dbench D0 18405 18404 0x [79880.428139] Call Trace: [79880.428142] __schedule+0x219/0x6b0 [79880.428144] schedule+0x36/0x80

[GIT PULL for-4.9 48/48] cpufreq: CPPC: add ACPI_PROCESSOR dependency

From: Arnd Bergmann [ Upstream commit a578884fa0d2768f13d37c6591a9e1ed600482d3 ] Without the Kconfig dependency, we can get this warning: warning: ACPI_CPPC_CPUFREQ selects ACPI_CPPC_LIB which has unmet direct dependencies (ACPI && ACPI_PROCESSOR) Fixes: 5477fb3bd1e8 (ACPI / CPPC: Add a

[GIT PULL for-4.9 36/48] uapi: fix linux/rds.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit feb0869d90e51ce8b6fd8a46588465b1b5a26d09 ] Consistently use types from linux/types.h to fix the following linux/rds.h userspace compilation errors: /usr/include/linux/rds.h:106:2: error: unknown type name 'uint8_t' uint8_t name[32];

[GIT PULL for-4.4 05/25] mac80211: fix power saving clients handling in iwlwifi

From: Emmanuel Grumbach [ Upstream commit d98937f4ea713d21e0fcc345919f86c877dd8d6f ] iwlwifi now supports RSS and can't let mac80211 track the PS state based on the Rx frames since they can come out of order. iwlwifi is now advertising AP_LINK_PS, and uses explicit

[GIT PULL for-4.4 05/25] mac80211: fix power saving clients handling in iwlwifi

From: Emmanuel Grumbach [ Upstream commit d98937f4ea713d21e0fcc345919f86c877dd8d6f ] iwlwifi now supports RSS and can't let mac80211 track the PS state based on the Rx frames since they can come out of order. iwlwifi is now advertising AP_LINK_PS, and uses explicit notifications to teach

[GIT PULL for-4.9 38/48] IB/hfi1: Use static CTLE with Preset 6 for integrated HFIs

From: Easwar Hariharan [ Upstream commit 39e2afa8d042a53d855137d4c5a689a6f5492b39 ] After extended testing, it was found that the previous PCIe Gen 3 recipe, which used adaptive CTLE with Preset 4, could cause an NMI/Surprise Link Down in about 1 in 100 to 1 in 1000

[GIT PULL for-4.9 37/48] uapi: fix linux/mroute6.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit 72aa107df6a275cf03359934ca5799a2be7a1bf7 ] Include to fix the following linux/mroute6.h userspace compilation errors: /usr/include/linux/mroute6.h:80:22: error: field 'mf6cc_origin' has incomplete type struct sockaddr_in6

[GIT PULL for-4.9 37/48] uapi: fix linux/mroute6.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit 72aa107df6a275cf03359934ca5799a2be7a1bf7 ] Include to fix the following linux/mroute6.h userspace compilation errors: /usr/include/linux/mroute6.h:80:22: error: field 'mf6cc_origin' has incomplete type struct sockaddr_in6 mf6cc_origin; /* Origin

[GIT PULL for-4.9 38/48] IB/hfi1: Use static CTLE with Preset 6 for integrated HFIs

From: Easwar Hariharan [ Upstream commit 39e2afa8d042a53d855137d4c5a689a6f5492b39 ] After extended testing, it was found that the previous PCIe Gen 3 recipe, which used adaptive CTLE with Preset 4, could cause an NMI/Surprise Link Down in about 1 in 100 to 1 in 1000 power cycles on some

Re: mmotm 2016-08-02-15-53 uploaded

Hi Andrew and Vitaly, I do agree that patch ee8f7fcbe638 ("ocfs2/dlm: continue to purge recovery lockres when recovery master goes down", 2016-08-02) introduced an issue. It makes DLM recovery can't pick up a new master for an existed lock resource whose owner died seconds ago. But this patch

Re: mmotm 2016-08-02-15-53 uploaded

Hi Andrew and Vitaly, I do agree that patch ee8f7fcbe638 ("ocfs2/dlm: continue to purge recovery lockres when recovery master goes down", 2016-08-02) introduced an issue. It makes DLM recovery can't pick up a new master for an existed lock resource whose owner died seconds ago. But this patch

[GIT PULL for-4.4 04/25] mac80211_hwsim: check HWSIM_ATTR_RADIO_NAME length

From: Johannes Berg [ Upstream commit ff4dd73dd2b4806419f8ff65cbce11d5019548d0 ] Unfortunately, the nla policy was defined to have HWSIM_ATTR_RADIO_NAME as an NLA_STRING, rather than NLA_NUL_STRING, so we can't use it as a NUL-terminated string in the kernel. Rather

[GIT PULL for-4.4 04/25] mac80211_hwsim: check HWSIM_ATTR_RADIO_NAME length

From: Johannes Berg [ Upstream commit ff4dd73dd2b4806419f8ff65cbce11d5019548d0 ] Unfortunately, the nla policy was defined to have HWSIM_ATTR_RADIO_NAME as an NLA_STRING, rather than NLA_NUL_STRING, so we can't use it as a NUL-terminated string in the kernel. Rather than break the API,

[GIT PULL for-4.4 08/25] iio: adc: xilinx: Fix error handling

From: Christophe JAILLET [ Upstream commit ca1c39ef76376b67303d01f94fe98bb68bb3861a ] Reorder error handling labels in order to match the way resources have been allocated. Signed-off-by: Christophe JAILLET Acked-by: Lars-Peter

[GIT PULL for-4.4 08/25] iio: adc: xilinx: Fix error handling

From: Christophe JAILLET [ Upstream commit ca1c39ef76376b67303d01f94fe98bb68bb3861a ] Reorder error handling labels in order to match the way resources have been allocated. Signed-off-by: Christophe JAILLET Acked-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron Signed-off-by: Sasha

Re: [PATCH] Makefile: enable dochelp run from main make level

On 10/10/17 17:54, Masahiro Yamada wrote: > 2017-10-11 5:09 GMT+09:00 Shuah Khan : >> On 10/07/2017 05:24 AM, Masahiro Yamada wrote: >>> 2017-10-03 8:44 GMT+09:00 Shuah Khan : Change to enable dochelp run from main make level to make it easier

Re: [PATCH] Makefile: enable dochelp run from main make level

On 10/10/17 17:54, Masahiro Yamada wrote: > 2017-10-11 5:09 GMT+09:00 Shuah Khan : >> On 10/07/2017 05:24 AM, Masahiro Yamada wrote: >>> 2017-10-03 8:44 GMT+09:00 Shuah Khan : Change to enable dochelp run from main make level to make it easier to use it. Signed-off-by: Shuah

Re: [PATCH 4.9 000/105] 4.9.55-stable review

On 10/10/2017 01:49 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.55 release. > There are 105 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

Re: [PATCH 4.9 000/105] 4.9.55-stable review

On 10/10/2017 01:49 PM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.55 release. > There are 105 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

[GIT PULL for-4.9 40/48] target/iscsi: Fix unsolicited data seq_end_offset calculation

From: Varun Prakash [ Upstream commit 4d65491c269729a1e3b375c45e73213f49103d33 ] In case of unsolicited data for the first sequence seq_end_offset must be set to minimum of total data length and FirstBurstLength, so do not add cmd->write_data_done to the min of total data

[GIT PULL for-4.9 46/48] btmrvl: avoid double-disable_irq() race

From: Jeffy Chen [ Upstream commit 9af02d86e11dc409e5c3de46e81c0a492ba58905 ] It's much the same as what we did for mwifiex in: b9da4d2 mwifiex: avoid double-disable_irq() race "We have a race where the wakeup IRQ might be in flight while we're calling

[GIT PULL for-4.9 40/48] target/iscsi: Fix unsolicited data seq_end_offset calculation

From: Varun Prakash [ Upstream commit 4d65491c269729a1e3b375c45e73213f49103d33 ] In case of unsolicited data for the first sequence seq_end_offset must be set to minimum of total data length and FirstBurstLength, so do not add cmd->write_data_done to the min of total data length and

[GIT PULL for-4.9 46/48] btmrvl: avoid double-disable_irq() race

From: Jeffy Chen [ Upstream commit 9af02d86e11dc409e5c3de46e81c0a492ba58905 ] It's much the same as what we did for mwifiex in: b9da4d2 mwifiex: avoid double-disable_irq() race "We have a race where the wakeup IRQ might be in flight while we're calling mwifiex_disable_wake() from resume().

[GIT PULL for-4.4 22/25] uapi: fix linux/mroute6.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit 72aa107df6a275cf03359934ca5799a2be7a1bf7 ] Include to fix the following linux/mroute6.h userspace compilation errors: /usr/include/linux/mroute6.h:80:22: error: field 'mf6cc_origin' has incomplete type struct sockaddr_in6

[GIT PULL for-4.4 22/25] uapi: fix linux/mroute6.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit 72aa107df6a275cf03359934ca5799a2be7a1bf7 ] Include to fix the following linux/mroute6.h userspace compilation errors: /usr/include/linux/mroute6.h:80:22: error: field 'mf6cc_origin' has incomplete type struct sockaddr_in6 mf6cc_origin; /* Origin

[GIT PULL for-4.4 21/25] uapi: fix linux/rds.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit feb0869d90e51ce8b6fd8a46588465b1b5a26d09 ] Consistently use types from linux/types.h to fix the following linux/rds.h userspace compilation errors: /usr/include/linux/rds.h:106:2: error: unknown type name 'uint8_t' uint8_t

[GIT PULL for-4.4 17/25] scsi: scsi_dh_emc: return success in clariion_std_inquiry()

From: Dan Carpenter [ Upstream commit 4d7d39a18b8b81511f0b893b7d2203790bf8a58b ] We accidentally return an uninitialized variable on success. Fixes: b6ff1b14cdf4 ("[SCSI] scsi_dh: Update EMC handler") Signed-off-by: Dan Carpenter

[GIT PULL for-4.4 21/25] uapi: fix linux/rds.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit feb0869d90e51ce8b6fd8a46588465b1b5a26d09 ] Consistently use types from linux/types.h to fix the following linux/rds.h userspace compilation errors: /usr/include/linux/rds.h:106:2: error: unknown type name 'uint8_t' uint8_t name[32];

[GIT PULL for-4.4 17/25] scsi: scsi_dh_emc: return success in clariion_std_inquiry()

From: Dan Carpenter [ Upstream commit 4d7d39a18b8b81511f0b893b7d2203790bf8a58b ] We accidentally return an uninitialized variable on success. Fixes: b6ff1b14cdf4 ("[SCSI] scsi_dh: Update EMC handler") Signed-off-by: Dan Carpenter Reviewed-by: Hannes Reinecke Signed-off-by: Martin K. Petersen

Re: [PATCH] KVM: X86: clear page flags when freeing kvm mmapping page

Cc mm community. 2017-10-11 3:26 GMT+08:00 Peng Hao : > When freeing mmapped kvm_run several pages, the pages will have page > flags PG_dirty and PG_referenced. It will result to bad page report > when allocating pages. > I just encounter once like this; > BUG: Bad page state

Re: [PATCH] KVM: X86: clear page flags when freeing kvm mmapping page

Cc mm community. 2017-10-11 3:26 GMT+08:00 Peng Hao : > When freeing mmapped kvm_run several pages, the pages will have page > flags PG_dirty and PG_referenced. It will result to bad page report > when allocating pages. > I just encounter once like this; > BUG: Bad page state in process

[GIT PULL for-4.4 13/25] net/mlx4_core: Fix VF overwrite of module param which disables DMFS on new probed PFs

From: Majd Dibbiny [ Upstream commit 95f1ba9a24af9769f6e20dfe9a77c863f253f311 ] In the VF driver, module parameter mlx4_log_num_mgm_entry_size was mistakenly overwritten -- and in a manner which overrode the device-managed flow steering option encoded in the parameter.

[GIT PULL for-4.4 13/25] net/mlx4_core: Fix VF overwrite of module param which disables DMFS on new probed PFs

From: Majd Dibbiny [ Upstream commit 95f1ba9a24af9769f6e20dfe9a77c863f253f311 ] In the VF driver, module parameter mlx4_log_num_mgm_entry_size was mistakenly overwritten -- and in a manner which overrode the device-managed flow steering option encoded in the parameter. log_num_mgm_entry_size

[GIT PULL for-4.4 12/25] sparc64: Migrate hvcons irq to panicked cpu

From: Vijay Kumar [ Upstream commit 7dd4fcf5b70694dc961eb6b954673e4fc9730dbd ] On panic, all other CPUs are stopped except the one which had hit panic. To keep console alive, we need to migrate hvcons irq to panicked CPU. Signed-off-by: Vijay Kumar

Re: [PATCH] Makefile: enable dochelp run from main make level

2017-10-11 5:09 GMT+09:00 Shuah Khan : > On 10/07/2017 05:24 AM, Masahiro Yamada wrote: >> 2017-10-03 8:44 GMT+09:00 Shuah Khan : >>> Change to enable dochelp run from main make level to make it easier to >>> use it. >>> >>> Signed-off-by: Shuah

[GIT PULL for-4.4 12/25] sparc64: Migrate hvcons irq to panicked cpu

From: Vijay Kumar [ Upstream commit 7dd4fcf5b70694dc961eb6b954673e4fc9730dbd ] On panic, all other CPUs are stopped except the one which had hit panic. To keep console alive, we need to migrate hvcons irq to panicked CPU. Signed-off-by: Vijay Kumar Signed-off-by: David S. Miller

Re: [PATCH] Makefile: enable dochelp run from main make level

2017-10-11 5:09 GMT+09:00 Shuah Khan : > On 10/07/2017 05:24 AM, Masahiro Yamada wrote: >> 2017-10-03 8:44 GMT+09:00 Shuah Khan : >>> Change to enable dochelp run from main make level to make it easier to >>> use it. >>> >>> Signed-off-by: Shuah Khan >>> --- >>> Makefile | 2 +- >>> 1 file

Re: [lockdep] b09be676e0 BUG: unable to handle kernel NULL pointer dereference at 000001f2

On Tue, Oct 10, 2017 at 09:22:26AM -0700, Linus Torvalds wrote: > On Mon, Oct 9, 2017 at 10:48 PM, Byungchul Park > wrote: > >> > >> The place where the release is done should simply be special. > >> > >> Because we should *not* encourage the whole "acquire by one

Re: [lockdep] b09be676e0 BUG: unable to handle kernel NULL pointer dereference at 000001f2

On Tue, Oct 10, 2017 at 09:22:26AM -0700, Linus Torvalds wrote: > On Mon, Oct 9, 2017 at 10:48 PM, Byungchul Park > wrote: > >> > >> The place where the release is done should simply be special. > >> > >> Because we should *not* encourage the whole "acquire by one context, > >> release by

[GIT PULL for-3.18 06/13] Btrfs: send, fix failure to rename top level inode due to name collision

From: Robbie Ko [ Upstream commit 4dd9920d991745c4a16f53a8f615f706fbe4b3f7 ] Under certain situations, an incremental send operation can fail due to a premature attempt to create a new top level inode (a direct child of the subvolume/snapshot root) whose name collides

[GIT PULL for-3.18 06/13] Btrfs: send, fix failure to rename top level inode due to name collision

From: Robbie Ko [ Upstream commit 4dd9920d991745c4a16f53a8f615f706fbe4b3f7 ] Under certain situations, an incremental send operation can fail due to a premature attempt to create a new top level inode (a direct child of the subvolume/snapshot root) whose name collides with another inode that

[GIT PULL for-3.18 05/13] iio: adc: xilinx: Fix error handling

From: Christophe JAILLET [ Upstream commit ca1c39ef76376b67303d01f94fe98bb68bb3861a ] Reorder error handling labels in order to match the way resources have been allocated. Signed-off-by: Christophe JAILLET Acked-by: Lars-Peter

[GIT PULL for-3.18 05/13] iio: adc: xilinx: Fix error handling

From: Christophe JAILLET [ Upstream commit ca1c39ef76376b67303d01f94fe98bb68bb3861a ] Reorder error handling labels in order to match the way resources have been allocated. Signed-off-by: Christophe JAILLET Acked-by: Lars-Peter Clausen Signed-off-by: Jonathan Cameron Signed-off-by: Sasha

[GIT PULL for-4.4 15/25] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

From: Eric Ren [ Upstream commit 439a36b8ef38657f765b80b775e2885338d72451 ] We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by

[GIT PULL for-4.4 15/25] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

From: Eric Ren [ Upstream commit 439a36b8ef38657f765b80b775e2885338d72451 ] We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by writing code

[GIT PULL for-4.9 39/48] IB/hfi1: Allocate context data on memory node

From: Sebastian Sanchez [ Upstream commit b448bf9a0df6093dbadac36979a55ce4e012a677 ] There are some memory allocation calls in hfi1_create_ctxtdata() that do not use the numa function parameter. This can cause cache lines to be filled over QPI. Reviewed-by: Mike

[GIT PULL for-4.9 39/48] IB/hfi1: Allocate context data on memory node

From: Sebastian Sanchez [ Upstream commit b448bf9a0df6093dbadac36979a55ce4e012a677 ] There are some memory allocation calls in hfi1_create_ctxtdata() that do not use the numa function parameter. This can cause cache lines to be filled over QPI. Reviewed-by: Mike Marciniszyn Signed-off-by:

[GIT PULL for-3.18 03/13] irqchip/crossbar: Fix incorrect type of local variables

From: Franck Demathieu [ Upstream commit b28ace12661fbcfd90959c1e84ff5a85113a82a1 ] The max and entry variables are unsigned according to the dt-bindings. Fix following 3 sparse issues (-Wtypesign): drivers/irqchip/irq-crossbar.c:222:52: warning: incorrect type in

[GIT PULL for-3.18 03/13] irqchip/crossbar: Fix incorrect type of local variables

From: Franck Demathieu [ Upstream commit b28ace12661fbcfd90959c1e84ff5a85113a82a1 ] The max and entry variables are unsigned according to the dt-bindings. Fix following 3 sparse issues (-Wtypesign): drivers/irqchip/irq-crossbar.c:222:52: warning: incorrect type in argument 3 (different

[GIT PULL for-4.4 00/25] Commits for v4.4 LTS

Hi Greg, The following commits were sent for review 7+ days ago, and comments were addressed. Please pull for v4.4 LTS. === The following changes since commit c030c36a88cdc54a5d657c0a2ee630ba495d5538: Linux 4.4.91 (2017-10-08 10:24:24 +0200) are available in the git repository at:

[GIT PULL for-4.4 00/25] Commits for v4.4 LTS

Hi Greg, The following commits were sent for review 7+ days ago, and comments were addressed. Please pull for v4.4 LTS. === The following changes since commit c030c36a88cdc54a5d657c0a2ee630ba495d5538: Linux 4.4.91 (2017-10-08 10:24:24 +0200) are available in the git repository at:

[GIT PULL for-3.18 04/13] netfilter: nf_ct_expect: Change __nf_ct_expect_check() return value.

From: Jarno Rajahalme [ Upstream commit 4b86c459c7bee3acaf92f0e2b4c6ac803eaa1a58 ] Commit 4dee62b1b9b4 ("netfilter: nf_ct_expect: nf_ct_expect_insert() returns void") inadvertently changed the successful return value of nf_ct_expect_related_report() from 0 to 1 due to

[GIT PULL for-3.18 04/13] netfilter: nf_ct_expect: Change __nf_ct_expect_check() return value.

From: Jarno Rajahalme [ Upstream commit 4b86c459c7bee3acaf92f0e2b4c6ac803eaa1a58 ] Commit 4dee62b1b9b4 ("netfilter: nf_ct_expect: nf_ct_expect_insert() returns void") inadvertently changed the successful return value of nf_ct_expect_related_report() from 0 to 1 due to __nf_ct_expect_check()

[GIT PULL for-4.4 24/25] nfsd/callback: Cleanup callback cred on shutdown

From: Kinglong Mee [ Upstream commit f7d1ddbe7648af7460d23688c8c131342eb43b3a ] The rpccred gotten from rpc_lookup_machine_cred() should be put when state is shutdown. Signed-off-by: Kinglong Mee Signed-off-by: J. Bruce Fields

[GIT PULL for-4.4 24/25] nfsd/callback: Cleanup callback cred on shutdown

From: Kinglong Mee [ Upstream commit f7d1ddbe7648af7460d23688c8c131342eb43b3a ] The rpccred gotten from rpc_lookup_machine_cred() should be put when state is shutdown. Signed-off-by: Kinglong Mee Signed-off-by: J. Bruce Fields Signed-off-by: Sasha Levin --- fs/nfsd/nfs4callback.c | 8

[GIT PULL for-4.4 23/25] target/iscsi: Fix unsolicited data seq_end_offset calculation

From: Varun Prakash [ Upstream commit 4d65491c269729a1e3b375c45e73213f49103d33 ] In case of unsolicited data for the first sequence seq_end_offset must be set to minimum of total data length and FirstBurstLength, so do not add cmd->write_data_done to the min of total data

Re: [PATCH 09/12] of: overlay: avoid race condition between applying multiple overlays

On 10/10/17 14:06, Rob Herring wrote: > On Tue, Oct 10, 2017 at 2:39 PM, Frank Rowand wrote: >> On 10/10/17 11:40, Rob Herring wrote: >>> On Wed, Oct 04, 2017 at 08:29:59PM -0700, Frank Rowand wrote: On 10/04/17 08:19, Rob Herring wrote: > On Mon, Oct 2, 2017 at

[GIT PULL for-4.4 23/25] target/iscsi: Fix unsolicited data seq_end_offset calculation

From: Varun Prakash [ Upstream commit 4d65491c269729a1e3b375c45e73213f49103d33 ] In case of unsolicited data for the first sequence seq_end_offset must be set to minimum of total data length and FirstBurstLength, so do not add cmd->write_data_done to the min of total data length and

Re: [PATCH 09/12] of: overlay: avoid race condition between applying multiple overlays

On 10/10/17 14:06, Rob Herring wrote: > On Tue, Oct 10, 2017 at 2:39 PM, Frank Rowand wrote: >> On 10/10/17 11:40, Rob Herring wrote: >>> On Wed, Oct 04, 2017 at 08:29:59PM -0700, Frank Rowand wrote: On 10/04/17 08:19, Rob Herring wrote: > On Mon, Oct 2, 2017 at 10:53 PM, wrote: >>

[GIT PULL for-4.9 43/48] powerpc/perf: Add restrictions to PMC5 in power9 DD1

From: Madhavan Srinivasan [ Upstream commit 8d911904f3ce412b20874a9c95f82009dcbb007c ] PMC5 on POWER9 DD1 may not provide right counts in all sampling scenarios, hence use PM_INST_DISP event instead in PMC2 or PMC3 in preference. Signed-off-by: Madhavan Srinivasan

[GIT PULL for-4.9 43/48] powerpc/perf: Add restrictions to PMC5 in power9 DD1

From: Madhavan Srinivasan [ Upstream commit 8d911904f3ce412b20874a9c95f82009dcbb007c ] PMC5 on POWER9 DD1 may not provide right counts in all sampling scenarios, hence use PM_INST_DISP event instead in PMC2 or PMC3 in preference. Signed-off-by: Madhavan Srinivasan Signed-off-by: Michael

[GIT PULL for-3.18 01/13] locking/lockdep: Add nest_lock integrity test

From: Peter Zijlstra [ Upstream commit 7fb4a2cea6b18dab56d609530d077f168169ed6b ] Boqun reported that hlock->references can overflow. Add a debug test for that to generate a clear error when this happens. Without this, lockdep is likely to report a mysterious failure on

[GIT PULL for-3.18 01/13] locking/lockdep: Add nest_lock integrity test

From: Peter Zijlstra [ Upstream commit 7fb4a2cea6b18dab56d609530d077f168169ed6b ] Boqun reported that hlock->references can overflow. Add a debug test for that to generate a clear error when this happens. Without this, lockdep is likely to report a mysterious failure on unlock. Reported-by:

[GIT PULL for-3.18 12/13] uapi: fix linux/mroute6.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit 72aa107df6a275cf03359934ca5799a2be7a1bf7 ] Include to fix the following linux/mroute6.h userspace compilation errors: /usr/include/linux/mroute6.h:80:22: error: field 'mf6cc_origin' has incomplete type struct sockaddr_in6

[GIT PULL for-3.18 09/13] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

From: Eric Ren [ Upstream commit 439a36b8ef38657f765b80b775e2885338d72451 ] We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by

[GIT PULL for-4.4 19/25] i2c: at91: ensure state is restored after suspending

From: Alexandre Belloni [ Upstream commit e3ccc921b7d8fd1fcd10a00720e09823d8078666 ] When going to suspend, the I2C registers may be lost because the power to VDDcore is cut. Restore them when resuming. Signed-off-by: Alexandre Belloni

[GIT PULL for-3.18 09/13] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

From: Eric Ren [ Upstream commit 439a36b8ef38657f765b80b775e2885338d72451 ] We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a cluster lock has been taken by a precess already. Mostly, we can avoid recursive locking by writing code

[GIT PULL for-4.4 19/25] i2c: at91: ensure state is restored after suspending

From: Alexandre Belloni [ Upstream commit e3ccc921b7d8fd1fcd10a00720e09823d8078666 ] When going to suspend, the I2C registers may be lost because the power to VDDcore is cut. Restore them when resuming. Signed-off-by: Alexandre Belloni Acked-by: Ludovic Desroches Signed-off-by: Wolfram Sang

[GIT PULL for-3.18 12/13] uapi: fix linux/mroute6.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit 72aa107df6a275cf03359934ca5799a2be7a1bf7 ] Include to fix the following linux/mroute6.h userspace compilation errors: /usr/include/linux/mroute6.h:80:22: error: field 'mf6cc_origin' has incomplete type struct sockaddr_in6 mf6cc_origin; /* Origin

[GIT PULL for-4.4 14/25] crypto: xts - Add ECB dependency

From: Milan Broz [ Upstream commit 12cb3a1c4184f891d965d1f39f8cfcc9ef617647 ] Since the commit f1c131b45410a202eb45cc55980a7a9e4e4b4f40 crypto: xts - Convert to skcipher the XTS mode is based on ECB, so the mode must select ECB otherwise it can fail to initialize.

[GIT PULL for-3.18 08/13] crypto: xts - Add ECB dependency

From: Milan Broz [ Upstream commit 12cb3a1c4184f891d965d1f39f8cfcc9ef617647 ] Since the commit f1c131b45410a202eb45cc55980a7a9e4e4b4f40 crypto: xts - Convert to skcipher the XTS mode is based on ECB, so the mode must select ECB otherwise it can fail to initialize.

[GIT PULL for-3.18 08/13] crypto: xts - Add ECB dependency

From: Milan Broz [ Upstream commit 12cb3a1c4184f891d965d1f39f8cfcc9ef617647 ] Since the commit f1c131b45410a202eb45cc55980a7a9e4e4b4f40 crypto: xts - Convert to skcipher the XTS mode is based on ECB, so the mode must select ECB otherwise it can fail to initialize. Signed-off-by: Milan

[GIT PULL for-4.4 14/25] crypto: xts - Add ECB dependency

From: Milan Broz [ Upstream commit 12cb3a1c4184f891d965d1f39f8cfcc9ef617647 ] Since the commit f1c131b45410a202eb45cc55980a7a9e4e4b4f40 crypto: xts - Convert to skcipher the XTS mode is based on ECB, so the mode must select ECB otherwise it can fail to initialize. Signed-off-by: Milan

[GIT PULL for-3.18 02/13] watchdog: kempld: fix gcc-4.3 build

From: Arnd Bergmann [ Upstream commit 3736d4eb6af37492aeded7fec0072dedd959c842 ] gcc-4.3 can't decide whether the constant value in kempld_prescaler[PRESCALER_21] is built-time constant or not, and gets confused by the logic in do_div(): drivers/watchdog/kempld_wdt.o: In

[GIT PULL for-3.18 11/13] uapi: fix linux/rds.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit feb0869d90e51ce8b6fd8a46588465b1b5a26d09 ] Consistently use types from linux/types.h to fix the following linux/rds.h userspace compilation errors: /usr/include/linux/rds.h:106:2: error: unknown type name 'uint8_t' uint8_t

[GIT PULL for-3.18 02/13] watchdog: kempld: fix gcc-4.3 build

From: Arnd Bergmann [ Upstream commit 3736d4eb6af37492aeded7fec0072dedd959c842 ] gcc-4.3 can't decide whether the constant value in kempld_prescaler[PRESCALER_21] is built-time constant or not, and gets confused by the logic in do_div(): drivers/watchdog/kempld_wdt.o: In function

[GIT PULL for-3.18 11/13] uapi: fix linux/rds.h userspace compilation errors

From: "Dmitry V. Levin" [ Upstream commit feb0869d90e51ce8b6fd8a46588465b1b5a26d09 ] Consistently use types from linux/types.h to fix the following linux/rds.h userspace compilation errors: /usr/include/linux/rds.h:106:2: error: unknown type name 'uint8_t' uint8_t name[32];

[GIT PULL for-3.18 13/13] target/iscsi: Fix unsolicited data seq_end_offset calculation

From: Varun Prakash [ Upstream commit 4d65491c269729a1e3b375c45e73213f49103d33 ] In case of unsolicited data for the first sequence seq_end_offset must be set to minimum of total data length and FirstBurstLength, so do not add cmd->write_data_done to the min of total data

[GIT PULL for-4.4 20/25] ceph: clean up unsafe d_parent accesses in build_dentry_path

From: Jeff Layton [ Upstream commit c6b0b656ca24ede6657abb4a2cd910fa9c1879ba ] While we hold a reference to the dentry when build_dentry_path is called, we could end up racing with a rename that changes d_parent. Handle that situation correctly, by using the rcu_read_lock to

[GIT PULL for-3.18 13/13] target/iscsi: Fix unsolicited data seq_end_offset calculation

From: Varun Prakash [ Upstream commit 4d65491c269729a1e3b375c45e73213f49103d33 ] In case of unsolicited data for the first sequence seq_end_offset must be set to minimum of total data length and FirstBurstLength, so do not add cmd->write_data_done to the min of total data length and

[GIT PULL for-4.4 20/25] ceph: clean up unsafe d_parent accesses in build_dentry_path

From: Jeff Layton [ Upstream commit c6b0b656ca24ede6657abb4a2cd910fa9c1879ba ] While we hold a reference to the dentry when build_dentry_path is called, we could end up racing with a rename that changes d_parent. Handle that situation correctly, by using the rcu_read_lock to ensure that the

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