Skip to content

Fix issues in check_irq_usage()

Boqun Feng lkml 1 version Applied

Status from this message: The following commit has been merged into the locking/core branch of tip:

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 2 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/4locking/lockdep: Fix the dep path printing for backwards BFSkernel/locking/lockdep.c+106 -20 replies
2/4locking/lockdep: Remove the unnecessary trace savingkernel/locking/lockdep.c+0 -30 replies
3/4lockding/lockdep: Avoid to find wrong lock dep path in check_irq_usage()kernel/locking/lockdep.c+11 -10 replies
4/4locking/selftests: Add a selftest for check_irq_usage()lib/locking-selftest.c+65 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/4] Fix issues in check_irq_usage()

Hi Peter,

As we talked in IRC, Johannes Berg reported a problem and I could reproduce by the selftest case in patch #4, there are three issues:

1) printing of backwards dependency path doesn't work as expected,

2) we have unnecessary and incorrect save_trace() call

3) check_irq_usage() may result in a wrong depedency path (when a
real one really exits).

Fix them separately in patch 1~3.

Regards,
Boqun

Boqun Feng (4):
locking/lockdep: Fix the dep path printing for backwards BFS locking/lockdep: Remove the unnecessary trace saving lockding/lockdep: Avoid to find wrong lock dep path in
check_irq_usage()
locking/selftests: Add a selftest for check_irq_usage()

 kernel/locking/lockdep.c | 123 +++++++++++++++++++++++++++++++++++++--
 lib/locking-selftest.c   |  65 +++++++++++++++++++++
 2 files changed, 182 insertions(+), 6 deletions(-)
Signature · 1 line
2.30.2