[PATCH v3 18/24] locking/lockdep: Reuse list entries that are no longer in use

Instead of abandoning elements of list_entries[] that are no longer in use, make alloc_list_entry() reuse array elements that have been freed. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- kernel/locking/lockdep.c | 27 --- 1

[PATCH v3 20/24] locking/lockdep: Introduce __lockdep_free_key_range()

This patch does not change any functionality but makes the next patch in this series easier to read. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- kernel/locking/lockdep.c | 37 ++--- 1 file changed, 22 insertions(+),

[PATCH v3 19/24] locking/lockdep: Check data structure consistency

Debugging lockdep data structure inconsistencies is challenging. Add disabled code that verifies data structure consistency at runtime. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- kernel/locking/lockdep.c | 146

Re: [PATCH v2] clocksource/drivers/fttmr010: fix invalid interrupt register access

On 11/5/18, 11:00 AM, "Tao Ren" wrote: > On 11/5/18, 10:51 AM, "Daniel Lezcano" wrote: >> Oh right, sorry. Should it go to stable also ? Is there a Fixes tag it can >> apply ? >> > Personally I don't think it needs to go to stable, because I don't see any > functional failures caused by this

[PATCH v3 18/24] locking/lockdep: Reuse list entries that are no longer in use

Instead of abandoning elements of list_entries[] that are no longer in use, make alloc_list_entry() reuse array elements that have been freed. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- kernel/locking/lockdep.c | 27 --- 1

[PATCH v3 24/24] lockdep tests: Test dynamic key registration

Make sure that the lockdep_register_key() and lockdep_unregister_key() code is tested when running the lockdep tests. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- tools/lib/lockdep/include/liblockdep/common.h | 2 ++

[PATCH v3 23/24] kernel/workqueue: Use dynamic lockdep keys for workqueues

Commit 87915adc3f0a ("workqueue: re-add lockdep dependencies for flushing") improved deadlock checking in the workqueue implementation. Unfortunately that patch also introduced a few false positive lockdep complaints. This patch suppresses these false positives by allocating the workqueue mutex

[PATCH v3 17/24] locking/lockdep: Free lock classes that are no longer in use

Instead of leaving lock classes that are no longer in use in the lock_classes array, reuse entries from that array that are no longer in use. Maintain a linked list of free lock classes with list head 'free_lock_class'. Initialize that list from inside register_lock_class() instead of from inside

[PATCH v3 03/24] lockdep tests: Improve testing accuracy

Instead of checking whether the tests produced any output, check the output itself. This patch avoids that e.g. debug output causes the message "PASSED!" to be reported for failed tests. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche ---

[PATCH v3 15/24] locking/lockdep: Reorder struct lock_class members

This patch does not change any functionality but makes the patch that frees lock classes that are no longer in use easier to read. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- include/linux/lockdep.h | 14 +++--- 1 file changed, 7

[PATCH v3 16/24] locking/lockdep: Retain the class key and name while freeing a lock class

The next patch in this series uses the class name in code that detects calls to lock_acquire() while a class key is being freed. Hence retain the class name for lock classes that are being freed. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche ---

[PATCH v3 05/24] liblockdep: Rename "trywlock" into "trywrlock"

This patch avoids that the following compiler warning is reported while compiling the lockdep unit tests: include/liblockdep/rwlock.h: In function 'liblockdep_pthread_rwlock_trywlock': include/liblockdep/rwlock.h:66:9: warning: implicit declaration of function 'pthread_rwlock_trywlock'; did you

[PATCH v3 16/24] locking/lockdep: Retain the class key and name while freeing a lock class

The next patch in this series uses the class name in code that detects calls to lock_acquire() while a class key is being freed. Hence retain the class name for lock classes that are being freed. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche ---

[PATCH v3 05/24] liblockdep: Rename "trywlock" into "trywrlock"

This patch avoids that the following compiler warning is reported while compiling the lockdep unit tests: include/liblockdep/rwlock.h: In function 'liblockdep_pthread_rwlock_trywlock': include/liblockdep/rwlock.h:66:9: warning: implicit declaration of function 'pthread_rwlock_trywlock'; did you

[PATCH v3 17/24] locking/lockdep: Free lock classes that are no longer in use

Instead of leaving lock classes that are no longer in use in the lock_classes array, reuse entries from that array that are no longer in use. Maintain a linked list of free lock classes with list head 'free_lock_class'. Initialize that list from inside register_lock_class() instead of from inside

[PATCH v3 03/24] lockdep tests: Improve testing accuracy

Instead of checking whether the tests produced any output, check the output itself. This patch avoids that e.g. debug output causes the message "PASSED!" to be reported for failed tests. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche ---

[PATCH v3 24/24] lockdep tests: Test dynamic key registration

Make sure that the lockdep_register_key() and lockdep_unregister_key() code is tested when running the lockdep tests. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- tools/lib/lockdep/include/liblockdep/common.h | 2 ++

[PATCH v3 23/24] kernel/workqueue: Use dynamic lockdep keys for workqueues

Commit 87915adc3f0a ("workqueue: re-add lockdep dependencies for flushing") improved deadlock checking in the workqueue implementation. Unfortunately that patch also introduced a few false positive lockdep complaints. This patch suppresses these false positives by allocating the workqueue mutex

[PATCH v3 15/24] locking/lockdep: Reorder struct lock_class members

This patch does not change any functionality but makes the patch that frees lock classes that are no longer in use easier to read. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- include/linux/lockdep.h | 14 +++--- 1 file changed, 7

[PATCH v3 14/24] locking/lockdep: Make zap_class() remove all matching lock order entries

Make sure that all lock order entries that refer to a class are removed from the list_entries[] array when a kernel module is unloaded. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- include/linux/lockdep.h | 1 + kernel/locking/lockdep.c | 17

[PATCH v3 04/24] lockdep tests: Run lockdep tests a second time under Valgrind

This improves test coverage. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- tools/lib/lockdep/run_tests.sh | 14 ++ 1 file changed, 14 insertions(+) diff --git a/tools/lib/lockdep/run_tests.sh b/tools/lib/lockdep/run_tests.sh index

[PATCH v3 01/24] lockdep tests: Display compiler warning and error messages

If compilation of liblockdep fails, display an error message and exit immediately. Display compiler warning and error messages that are generated while building a test. Only run a test if compilation of it succeeded. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van

[PATCH v3 07/24] lockdep tests: Test the lockdep_reset_lock() implementation

This patch makes sure that the lockdep_reset_lock() function gets tested. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- tools/lib/lockdep/include/liblockdep/common.h | 1 + tools/lib/lockdep/include/liblockdep/mutex.h | 1 +

[PATCH v3 14/24] locking/lockdep: Make zap_class() remove all matching lock order entries

Make sure that all lock order entries that refer to a class are removed from the list_entries[] array when a kernel module is unloaded. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- include/linux/lockdep.h | 1 + kernel/locking/lockdep.c | 17

[PATCH v3 04/24] lockdep tests: Run lockdep tests a second time under Valgrind

This improves test coverage. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- tools/lib/lockdep/run_tests.sh | 14 ++ 1 file changed, 14 insertions(+) diff --git a/tools/lib/lockdep/run_tests.sh b/tools/lib/lockdep/run_tests.sh index

[PATCH v3 01/24] lockdep tests: Display compiler warning and error messages

If compilation of liblockdep fails, display an error message and exit immediately. Display compiler warning and error messages that are generated while building a test. Only run a test if compilation of it succeeded. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van

[PATCH v3 07/24] lockdep tests: Test the lockdep_reset_lock() implementation

This patch makes sure that the lockdep_reset_lock() function gets tested. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- tools/lib/lockdep/include/liblockdep/common.h | 1 + tools/lib/lockdep/include/liblockdep/mutex.h | 1 +

[PATCH v3 21/24] locking/lockdep: Verify whether lock objects are small enough to be used as class keys

Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- kernel/locking/lockdep.c | 9 + 1 file changed, 9 insertions(+) diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c index 8c69516b1283..a47357d3dca7 100644 ---

[PATCH v3 22/24] locking/lockdep: Add support for dynamic keys

A shortcoming of the current lockdep implementation is that it requires lock keys to be allocated statically. That forces certain lock objects to share lock keys. Since lock dependency analysis groups lock objects per key sharing lock keys can cause false positive lockdep reports. Make it possible

[PATCH v3 10/24] locking/lockdep: Introduce lock_class_cache_is_registered()

This patch does not change any functionality but makes the lockdep_reset_lock() function easier to read. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- kernel/locking/lockdep.c | 50 1 file changed, 30

[PATCH v3 08/24] locking/lockdep: Declare local symbols static

This patch avoids that sparse complains about a missing declaration for the lock_classes array when building with CONFIG_DEBUG_LOCKDEP=n. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- kernel/locking/lockdep.c | 3 +++ 1 file changed, 3 insertions(+)

[PATCH v3 21/24] locking/lockdep: Verify whether lock objects are small enough to be used as class keys

Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- kernel/locking/lockdep.c | 9 + 1 file changed, 9 insertions(+) diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c index 8c69516b1283..a47357d3dca7 100644 ---

[PATCH v3 22/24] locking/lockdep: Add support for dynamic keys

A shortcoming of the current lockdep implementation is that it requires lock keys to be allocated statically. That forces certain lock objects to share lock keys. Since lock dependency analysis groups lock objects per key sharing lock keys can cause false positive lockdep reports. Make it possible

[PATCH v3 10/24] locking/lockdep: Introduce lock_class_cache_is_registered()

This patch does not change any functionality but makes the lockdep_reset_lock() function easier to read. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- kernel/locking/lockdep.c | 50 1 file changed, 30

[PATCH v3 08/24] locking/lockdep: Declare local symbols static

This patch avoids that sparse complains about a missing declaration for the lock_classes array when building with CONFIG_DEBUG_LOCKDEP=n. Cc: Peter Zijlstra Cc: Waiman Long Cc: Johannes Berg Signed-off-by: Bart Van Assche --- kernel/locking/lockdep.c | 3 +++ 1 file changed, 3 insertions(+)

Re: [PATCH] riscv: remove unused variable in ftrace

On Thu, 6 Dec 2018 11:20:31 -0800 Olof Johansson wrote: > On Thu, Dec 6, 2018 at 2:26 AM David Abdurachmanov > wrote: > > > > Noticed while building kernel-4.20.0-0.rc5.git2.1.fc30 for > > Fedora 30/RISCV. > > > > [..] > > BUILDSTDERR: arch/riscv/kernel/ftrace.c: In function > >

Re: [PATCH] riscv: remove unused variable in ftrace

On Thu, 6 Dec 2018 11:20:31 -0800 Olof Johansson wrote: > On Thu, Dec 6, 2018 at 2:26 AM David Abdurachmanov > wrote: > > > > Noticed while building kernel-4.20.0-0.rc5.git2.1.fc30 for > > Fedora 30/RISCV. > > > > [..] > > BUILDSTDERR: arch/riscv/kernel/ftrace.c: In function > >

[PATCH] thermal: uniphier: Convert to SPDX identifier

This converts license boilerplate to SPDX identifier, and removes unnecessary lines. Signed-off-by: Kunihiko Hayashi --- drivers/thermal/uniphier_thermal.c | 13 + 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/drivers/thermal/uniphier_thermal.c

[PATCH] thermal: uniphier: Convert to SPDX identifier

This converts license boilerplate to SPDX identifier, and removes unnecessary lines. Signed-off-by: Kunihiko Hayashi --- drivers/thermal/uniphier_thermal.c | 13 + 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/drivers/thermal/uniphier_thermal.c

Re: [RFC v3 11/19] kunit: add Python libraries for handing KUnit config and kernel

On Thu, Dec 06, 2018 at 12:32:47PM +, Kieran Bingham wrote: > My main initial idea for a libumlinux is to provide infrastructure such > as our linked-lists and other kernel formatting so that we can take > kernel code directly to userspace for test and debug (assuming that > there are no

Re: [PATCH v4] signal: add taskfd_send_signal() syscall

On Thu, Dec 06, 2018 at 04:34:54PM -0800, Daniel Colascione wrote: > On Thu, Dec 6, 2018 at 4:31 PM Serge E. Hallyn wrote: > > > > On Fri, Dec 07, 2018 at 12:17:45AM +0100, Christian Brauner wrote: > > > On Thu, Dec 06, 2018 at 11:39:48PM +0100, Christian Brauner wrote: > > > > On Thu, Dec 06,

Re: [PATCH v4] signal: add taskfd_send_signal() syscall

On Thu, Dec 06, 2018 at 04:34:54PM -0800, Daniel Colascione wrote: > On Thu, Dec 6, 2018 at 4:31 PM Serge E. Hallyn wrote: > > > > On Fri, Dec 07, 2018 at 12:17:45AM +0100, Christian Brauner wrote: > > > On Thu, Dec 06, 2018 at 11:39:48PM +0100, Christian Brauner wrote: > > > > On Thu, Dec 06,

linux-next: manual merge of the jc_docs tree with the fscrypt tree

Hi all, Today's linux-next merge of the jc_docs tree got a conflict in: Documentation/filesystems/index.rst between commit: 1b71a6809f96 ("fs-verity: add a documentation file") from the fscrypt tree and commit: 7bbfd9ad8eb2 ("Documentation: convert path-lookup from markdown to

linux-next: manual merge of the jc_docs tree with the fscrypt tree

Hi all, Today's linux-next merge of the jc_docs tree got a conflict in: Documentation/filesystems/index.rst between commit: 1b71a6809f96 ("fs-verity: add a documentation file") from the fscrypt tree and commit: 7bbfd9ad8eb2 ("Documentation: convert path-lookup from markdown to

[PATCH v5 1/2] dt-bindings: PCI: Add UniPhier PCIe host controller description

Add DT bindings for PCIe controller implemented in UniPhier SoCs when configured in Root Complex (host) mode. This controller is based on the DesignWare PCIe core. Signed-off-by: Kunihiko Hayashi Reviewed-by: Rob Herring --- .../devicetree/bindings/pci/uniphier-pcie.txt | 81

[PATCH v5 2/2] PCI: uniphier: Add UniPhier PCIe host controller support

This introduces specific glue layer for UniPhier platform to support PCIe host controller that is based on the DesignWare PCIe core, and this driver supports Root Complex (host) mode. Signed-off-by: Kunihiko Hayashi --- MAINTAINERS| 7 +

[PATCH v5 1/2] dt-bindings: PCI: Add UniPhier PCIe host controller description

Add DT bindings for PCIe controller implemented in UniPhier SoCs when configured in Root Complex (host) mode. This controller is based on the DesignWare PCIe core. Signed-off-by: Kunihiko Hayashi Reviewed-by: Rob Herring --- .../devicetree/bindings/pci/uniphier-pcie.txt | 81

[PATCH v5 2/2] PCI: uniphier: Add UniPhier PCIe host controller support

This introduces specific glue layer for UniPhier platform to support PCIe host controller that is based on the DesignWare PCIe core, and this driver supports Root Complex (host) mode. Signed-off-by: Kunihiko Hayashi --- MAINTAINERS| 7 +

[PATCH v5 0/2] Add new UniPhier PCIe host driver

This series adds PCIe host controller driver for Socionext UniPhier SoCs. This controller is based on the DesignWare PCIe core. This driver supports LD20 and PXs3 SoCs. v4: https://www.spinics.net/lists/linux-pci/msg78278.html About legacy IRQ, it might be necessary to share common view from

[PATCH v5 0/2] Add new UniPhier PCIe host driver

This series adds PCIe host controller driver for Socionext UniPhier SoCs. This controller is based on the DesignWare PCIe core. This driver supports LD20 and PXs3 SoCs. v4: https://www.spinics.net/lists/linux-pci/msg78278.html About legacy IRQ, it might be necessary to share common view from

[PATCH v2] tps65218: Use devm_regmap_add_irq_chip and clean up error path in probe

Use devm_regmap_add_irq_chip and clean up error path in probe. Hence clean up the probe error path and the remove function. Reported-by: Christian Hohnstaedt Signed-off-by: Keerthy --- Changes in v2: * Cleaned up remove function as well. drivers/mfd/tps65218.c | 18 +++--- 1

[PATCH v2] tps65218: Use devm_regmap_add_irq_chip and clean up error path in probe

Use devm_regmap_add_irq_chip and clean up error path in probe. Hence clean up the probe error path and the remove function. Reported-by: Christian Hohnstaedt Signed-off-by: Keerthy --- Changes in v2: * Cleaned up remove function as well. drivers/mfd/tps65218.c | 18 +++--- 1

Re: [PATCH] dt-bindings: sifive: describe sifive-blocks versioning

On Thu, 6 Dec 2018, Rob Herring wrote: > On Wed, Nov 21, 2018 at 05:06:56PM -0800, Paul Walmsley wrote: > > > > For IP blocks that are generated from the public, open-source > > sifive-blocks repository, describe the version numbering policy > > that its maintainers intend to use, upon

Re: [PATCH] dt-bindings: sifive: describe sifive-blocks versioning

On Thu, 6 Dec 2018, Rob Herring wrote: > On Wed, Nov 21, 2018 at 05:06:56PM -0800, Paul Walmsley wrote: > > > > For IP blocks that are generated from the public, open-source > > sifive-blocks repository, describe the version numbering policy > > that its maintainers intend to use, upon

Re: [RFC v3 17/19] of: unittest: migrate tests to run on KUnit

On Wed, Dec 5, 2018 at 5:43 PM Brendan Higgins wrote: > > On Tue, Dec 4, 2018 at 5:41 AM Rob Herring wrote: > > > > On Mon, Dec 3, 2018 at 6:14 PM Brendan Higgins > > wrote: > > > > > > On Thu, Nov 29, 2018 at 4:40 PM Randy Dunlap > > > wrote: > > > > > > > > On 11/28/18 12:56 PM, Rob Herring

Re: [PATCH v4] signal: add taskfd_send_signal() syscall

On Thu, Dec 6, 2018 at 4:31 PM Serge E. Hallyn wrote: > > On Fri, Dec 07, 2018 at 12:17:45AM +0100, Christian Brauner wrote: > > On Thu, Dec 06, 2018 at 11:39:48PM +0100, Christian Brauner wrote: > > > On Thu, Dec 06, 2018 at 03:46:53PM -0600, Eric W. Biederman wrote: > > > > Christian Brauner

Re: [PATCH v4] signal: add taskfd_send_signal() syscall

On Thu, Dec 6, 2018 at 4:31 PM Serge E. Hallyn wrote: > > On Fri, Dec 07, 2018 at 12:17:45AM +0100, Christian Brauner wrote: > > On Thu, Dec 06, 2018 at 11:39:48PM +0100, Christian Brauner wrote: > > > On Thu, Dec 06, 2018 at 03:46:53PM -0600, Eric W. Biederman wrote: > > > > Christian Brauner

Re: [PATCH v4] signal: add taskfd_send_signal() syscall

On Fri, Dec 07, 2018 at 12:17:45AM +0100, Christian Brauner wrote: > On Thu, Dec 06, 2018 at 11:39:48PM +0100, Christian Brauner wrote: > > On Thu, Dec 06, 2018 at 03:46:53PM -0600, Eric W. Biederman wrote: > > > Christian Brauner writes: > > > > > > >> Your intention is to add the thread case

Re: [PATCH v4] signal: add taskfd_send_signal() syscall

On Fri, Dec 07, 2018 at 12:17:45AM +0100, Christian Brauner wrote: > On Thu, Dec 06, 2018 at 11:39:48PM +0100, Christian Brauner wrote: > > On Thu, Dec 06, 2018 at 03:46:53PM -0600, Eric W. Biederman wrote: > > > Christian Brauner writes: > > > > > > >> Your intention is to add the thread case

Re: [PATCH] mfd: tps65218: Use devm_regmap_add_irq_chip and clean up error path in probe

On 12/7/2018 2:21 AM, Sebastian Reichel wrote: Hi, On Thu, Dec 06, 2018 at 11:07:44PM +0530, Keerthy wrote: Use devm_regmap_add_irq_chip and clean up error path in probe. Reported-by: Christian Hohnstaedt Signed-off-by: Keerthy --- Boot tested on am437x-gp-evm. This is missing cleanup

Re: [PATCH] mfd: tps65218: Use devm_regmap_add_irq_chip and clean up error path in probe

On 12/7/2018 2:21 AM, Sebastian Reichel wrote: Hi, On Thu, Dec 06, 2018 at 11:07:44PM +0530, Keerthy wrote: Use devm_regmap_add_irq_chip and clean up error path in probe. Reported-by: Christian Hohnstaedt Signed-off-by: Keerthy --- Boot tested on am437x-gp-evm. This is missing cleanup

Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind()

On Thu, Dec 06, 2018 at 04:48:57PM -0700, Logan Gunthorpe wrote: > > > On 2018-12-06 4:38 p.m., Dave Hansen wrote: > > On 12/6/18 3:28 PM, Logan Gunthorpe wrote: > >> I didn't think this was meant to describe actual real world performance > >> between all of the links. If that's the case all of

Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind()

On Thu, Dec 06, 2018 at 04:48:57PM -0700, Logan Gunthorpe wrote: > > > On 2018-12-06 4:38 p.m., Dave Hansen wrote: > > On 12/6/18 3:28 PM, Logan Gunthorpe wrote: > >> I didn't think this was meant to describe actual real world performance > >> between all of the links. If that's the case all of

Re: [PATCH] nvme-rdma: complete requests from ->timeout

Could you please take a look at this bug and code review? We are seeing more instances of this bug and found that reconnect_work could hang as well, as can be seen from below stacktrace. Workqueue: nvme-wq nvme_rdma_reconnect_ctrl_work [nvme_rdma] Call Trace: __schedule+0x2ab/0x880

Re: [PATCH] nvme-rdma: complete requests from ->timeout

Could you please take a look at this bug and code review? We are seeing more instances of this bug and found that reconnect_work could hang as well, as can be seen from below stacktrace. Workqueue: nvme-wq nvme_rdma_reconnect_ctrl_work [nvme_rdma] Call Trace: __schedule+0x2ab/0x880

Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind()

On Thu, Dec 06, 2018 at 03:09:21PM -0800, Dave Hansen wrote: > On 12/6/18 2:39 PM, Jerome Glisse wrote: > > No if the 4 sockets are connect in a ring fashion ie: > > Socket0 - Socket1 > >| | > > Socket3 - Socket2 > > > > Then you have 4 links: > > link0:

Re: [PATCH v2] mwifiex: debugfs: correct histogram spacing, formatting

On Tue, Dec 04, 2018 at 08:37:30AM +0200, Kalle Valo wrote: > Brian Norris writes: > > > Here's a v2 that combines both sets of strings in that way. I'm not > > resending the other patches, since they were only related in concept > > (since I was referring to debugfs for implementing the nl80211

Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind()

On Thu, Dec 06, 2018 at 03:09:21PM -0800, Dave Hansen wrote: > On 12/6/18 2:39 PM, Jerome Glisse wrote: > > No if the 4 sockets are connect in a ring fashion ie: > > Socket0 - Socket1 > >| | > > Socket3 - Socket2 > > > > Then you have 4 links: > > link0:

Re: [PATCH v2] mwifiex: debugfs: correct histogram spacing, formatting

On Tue, Dec 04, 2018 at 08:37:30AM +0200, Kalle Valo wrote: > Brian Norris writes: > > > Here's a v2 that combines both sets of strings in that way. I'm not > > resending the other patches, since they were only related in concept > > (since I was referring to debugfs for implementing the nl80211

[RFC PATCH v2 2/2] mwifiex: add NL80211_STA_INFO_RX_BITRATE support

Comparing the existing TX_BITRATE parsing code (in mwifiex_parse_htinfo()) with the RX bitrate histograms in debugfs.c, it appears that the rxpd_rate and rxpd_htinfo fields have the same format. At least, they give reasonable results when I parse them this way. So this patch adds support for

[RFC PATCH v2 1/2] mwifiex: refactor mwifiex_parse_htinfo() for reuse

This function converts some firmware-specific parameters into cfg80211 'rate_info' structures. It currently assumes it's dealing only with TX bitrate, but the RX bitrate looks to be the same, so refactor this function to be reusable. Signed-off-by: Brian Norris --- v2: * no change - just split

Re: [PATCH] arm64: dts: sdm845: Add lpasscc node

Hi, On Wed, Dec 5, 2018 at 12:00 AM Taniya Das wrote: > > This adds the low pass audio clock controller node to sdm845 based on > the example in the bindings. > > Signed-off-by: Taniya Das > --- > arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 4 +++- > arch/arm64/boot/dts/qcom/sdm845.dtsi| 8

Re: [PATCH] arm64: dts: sdm845: Add lpasscc node

Hi, On Wed, Dec 5, 2018 at 12:00 AM Taniya Das wrote: > > This adds the low pass audio clock controller node to sdm845 based on > the example in the bindings. > > Signed-off-by: Taniya Das > --- > arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 4 +++- > arch/arm64/boot/dts/qcom/sdm845.dtsi| 8

Re: [PATCH] dt-bindings: sifive: describe sifive-blocks versioning

On Wed, Nov 21, 2018 at 05:06:56PM -0800, Paul Walmsley wrote: > > For IP blocks that are generated from the public, open-source > sifive-blocks repository, describe the version numbering policy > that its maintainers intend to use, upon request from Rob > Herring . > > Cc: Rob Herring > Cc:

Re: [PATCH] dt-bindings: sifive: describe sifive-blocks versioning

On Wed, Nov 21, 2018 at 05:06:56PM -0800, Paul Walmsley wrote: > > For IP blocks that are generated from the public, open-source > sifive-blocks repository, describe the version numbering policy > that its maintainers intend to use, upon request from Rob > Herring . > > Cc: Rob Herring > Cc:

Re: [PATCH v2 3/3] arm64: dts: qcom: sdm845: Add SD nodes for sdm845-mtp

On Thu 06 Dec 10:45 PST 2018, Evan Green wrote: > Enable support for one of the micro SD slots on the MTP. > > Signed-off-by: Evan Green Reviewed-by: Bjorn Andersson Regards, Bjorn > --- > > Changes in v2: > - Fixed alphabetization of node placement in sdm845-mtp.dtsi (Doug) > - Fixed

Re: [PATCH v2 3/3] arm64: dts: qcom: sdm845: Add SD nodes for sdm845-mtp

On Thu 06 Dec 10:45 PST 2018, Evan Green wrote: > Enable support for one of the micro SD slots on the MTP. > > Signed-off-by: Evan Green Reviewed-by: Bjorn Andersson Regards, Bjorn > --- > > Changes in v2: > - Fixed alphabetization of node placement in sdm845-mtp.dtsi (Doug) > - Fixed

Re: [PATCH v2 2/3] arm64: dts: qcom: sdm845: Add SD node

On Thu 06 Dec 10:45 PST 2018, Evan Green wrote: > Add one of the two SD controllers to SDM845. > > Signed-off-by: Evan Green > Reviewed-by: Douglas Anderson Reviewed-by: Bjorn Andersson Regards, Bjorn > --- > > Changes in v2: > - Reworded commit message to note that there are multiple SD

Re: [PATCH v2 2/3] arm64: dts: qcom: sdm845: Add SD node

On Thu 06 Dec 10:45 PST 2018, Evan Green wrote: > Add one of the two SD controllers to SDM845. > > Signed-off-by: Evan Green > Reviewed-by: Douglas Anderson Reviewed-by: Bjorn Andersson Regards, Bjorn > --- > > Changes in v2: > - Reworded commit message to note that there are multiple SD

[PATCH] selftests/seccomp: Remove SIGSTOP si_pid check

Commit f149b3155744 ("signal: Never allocate siginfo for SIGKILL or SIGSTOP") means that the seccomp selftest cannot check si_pid under SIGSTOP anymore. Since it's believed[1] there are no other userspace things depending on the old behavior, this removes the behavioral check in the selftest,

[PATCH] selftests/seccomp: Remove SIGSTOP si_pid check

Commit f149b3155744 ("signal: Never allocate siginfo for SIGKILL or SIGSTOP") means that the seccomp selftest cannot check si_pid under SIGSTOP anymore. Since it's believed[1] there are no other userspace things depending on the old behavior, this removes the behavioral check in the selftest,

Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind()

On 2018-12-06 4:38 p.m., Dave Hansen wrote: > On 12/6/18 3:28 PM, Logan Gunthorpe wrote: >> I didn't think this was meant to describe actual real world performance >> between all of the links. If that's the case all of this seems like a >> pipe dream to me. > > The HMAT discussions (that I was

[PATCH] scsi: qla2xxx: deadlock by configfs_depend_item

The intent of invoking configfs_depend_item in commit 7474f52a82d51 ("tcm_qla2xxx: Perform configfs depend/undepend for base_tpg") was to prevent a physical Fibre Channel port removal when virtual (NPIV) ports announced through that physical port are active. The change does not work as expected:

Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind()

On 2018-12-06 4:38 p.m., Dave Hansen wrote: > On 12/6/18 3:28 PM, Logan Gunthorpe wrote: >> I didn't think this was meant to describe actual real world performance >> between all of the links. If that's the case all of this seems like a >> pipe dream to me. > > The HMAT discussions (that I was

[PATCH] scsi: qla2xxx: deadlock by configfs_depend_item

The intent of invoking configfs_depend_item in commit 7474f52a82d51 ("tcm_qla2xxx: Perform configfs depend/undepend for base_tpg") was to prevent a physical Fibre Channel port removal when virtual (NPIV) ports announced through that physical port are active. The change does not work as expected:

Re: MADV_HUGEPAGE vs. NUMA semantic (was: Re: [LKP] [mm] ac5b2c1891: vm-scalability.throughput -61.3% regression)

On Thu, 6 Dec 2018, Michal Hocko wrote: > MADV_HUGEPAGE changes the picture because the caller expressed a need > for THP and is willing to go extra mile to get it. That involves > allocation latency and as of now also a potential remote access. We do > not have complete agreement on the later

Re: MADV_HUGEPAGE vs. NUMA semantic (was: Re: [LKP] [mm] ac5b2c1891: vm-scalability.throughput -61.3% regression)

On Thu, 6 Dec 2018, Michal Hocko wrote: > MADV_HUGEPAGE changes the picture because the caller expressed a need > for THP and is willing to go extra mile to get it. That involves > allocation latency and as of now also a potential remote access. We do > not have complete agreement on the later

Re: [PATCH 2/3] dt-bindings: drm/panel: simple: add support for PDA 91-00156-A0

On Wed, Nov 21, 2018 at 08:48:00AM +, eugen.hris...@microchip.com wrote: > From: Cristian Birsan > > PDA 91-00156-A0 5.0 is a 5.0" WVGA TFT LCD panel. > This panel with backlight is found in PDA 5" LCD screen (TM5000 series or > AC320005-5). > Adding Device Tree bindings for this panel. > >

[PATCH 1/6] arm64: kpti: move check for non-vulnerable CPUs to a function

From: Mian Yousaf Kaukab Add is_meltdown_safe() which is a whitelist of known safe cores. Signed-off-by: Mian Yousaf Kaukab [Moved location of function] Signed-off-by: Jeremy Linton --- arch/arm64/kernel/cpufeature.c | 16 1 file changed, 12 insertions(+), 4 deletions(-)

[PATCH 1/6] arm64: kpti: move check for non-vulnerable CPUs to a function

From: Mian Yousaf Kaukab Add is_meltdown_safe() which is a whitelist of known safe cores. Signed-off-by: Mian Yousaf Kaukab [Moved location of function] Signed-off-by: Jeremy Linton --- arch/arm64/kernel/cpufeature.c | 16 1 file changed, 12 insertions(+), 4 deletions(-)

Re: [PATCH 1/3] dt-bindings: add vendor prefix for PDA Precision Design Associates, Inc.

On Wed, 21 Nov 2018 08:47:57 +, wrote: > Precision Design Associates, Inc. (PDA) manufactures standard and custom > capacitive touch screens, LCD's embedded controllers and custom embedded > software. They specialize in industrial, rugged and outdoor applications. > Website:

[PATCH 2/6] arm64: add sysfs vulnerability show for meltdown

Add a simple state machine which will track whether all the online cores in a machine are vulnerable. Once that is done we have a fairly authoritative view of the machine vulnerability, which allows us to make a judgment about machine safety if it hasn't been mitigated. Signed-off-by: Jeremy

[PATCH 3/6] arm64: add sysfs vulnerability show for spectre v1

From: Mian Yousaf Kaukab spectre v1, has been mitigated, and the mitigation is always active. Signed-off-by: Mian Yousaf Kaukab Signed-off-by: Jeremy Linton --- arch/arm64/kernel/cpu_errata.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/kernel/cpu_errata.c

[PATCH 4/6] arm64: add sysfs vulnerability show for spectre v2

Add code to track whether all the cores in the machine are vulnerable, and whether all the vulnerable cores have been mitigated. Once we have that information we can add the sysfs stub and provide an accurate view of what is known about the machine. Signed-off-by: Jeremy Linton ---

Re: [PATCH v2 3/3] arm64: dts: qcom: sdm845: Add SD nodes for sdm845-mtp

Hi, On Thu, Dec 6, 2018 at 10:46 AM Evan Green wrote: > > Enable support for one of the micro SD slots on the MTP. > > Signed-off-by: Evan Green > --- > > Changes in v2: > - Fixed alphabetization of node placement in sdm845-mtp.dtsi (Doug) > - Fixed card detect name to match schematics

[PATCH 5/6] arm64: add sysfs vulnerability show for speculative store bypass

From: Mian Yousaf Kaukab Return status based no ssbd_state and the arm64 SSBS feature. Return string "Unknown" in case CONFIG_ARM64_SSBD is disabled or arch workaround2 is not available in the firmware. Signed-off-by: Mian Yousaf Kaukab [Added SSBS logic] Signed-off-by: Jeremy Linton ---

[PATCH 2/6] arm64: add sysfs vulnerability show for meltdown

Add a simple state machine which will track whether all the online cores in a machine are vulnerable. Once that is done we have a fairly authoritative view of the machine vulnerability, which allows us to make a judgment about machine safety if it hasn't been mitigated. Signed-off-by: Jeremy

[PATCH 3/6] arm64: add sysfs vulnerability show for spectre v1

From: Mian Yousaf Kaukab spectre v1, has been mitigated, and the mitigation is always active. Signed-off-by: Mian Yousaf Kaukab Signed-off-by: Jeremy Linton --- arch/arm64/kernel/cpu_errata.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm64/kernel/cpu_errata.c

[PATCH 4/6] arm64: add sysfs vulnerability show for spectre v2

Add code to track whether all the cores in the machine are vulnerable, and whether all the vulnerable cores have been mitigated. Once we have that information we can add the sysfs stub and provide an accurate view of what is known about the machine. Signed-off-by: Jeremy Linton ---

Re: [PATCH v2 3/3] arm64: dts: qcom: sdm845: Add SD nodes for sdm845-mtp

Hi, On Thu, Dec 6, 2018 at 10:46 AM Evan Green wrote: > > Enable support for one of the micro SD slots on the MTP. > > Signed-off-by: Evan Green > --- > > Changes in v2: > - Fixed alphabetization of node placement in sdm845-mtp.dtsi (Doug) > - Fixed card detect name to match schematics

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