aboutsummaryrefslogtreecommitdiffstats
path: root/net/bluetooth/hci_request.c
diff options
context:
space:
mode:
authorPaul E. McKenney <[email protected]>2020-12-08 22:43:43 +0000
committerPaul E. McKenney <[email protected]>2021-01-22 23:24:23 +0000
commit3375efeddf6972df47df26a5b5c643189bd3c02a (patch)
tree1cbf279264fc88f0cab1a396ffdba91f54ca11d0 /net/bluetooth/hci_request.c
parentrcu: Make call_rcu() print mem_dump_obj() info for double-freed callback (diff)
downloadkernel-3375efeddf6972df47df26a5b5c643189bd3c02a.tar.gz
kernel-3375efeddf6972df47df26a5b5c643189bd3c02a.zip
percpu_ref: Dump mem_dump_obj() info upon reference-count underflow
Reference-count underflow for percpu_ref is detected in the RCU callback percpu_ref_switch_to_atomic_rcu(), and the resulting warning does not print anything allowing easy identification of which percpu_ref use case is underflowing. This is of course not normally a problem when developing a new percpu_ref use case because it is most likely that the problem resides in this new use case. However, when deploying a new kernel to a large set of servers, the underflow might well be a new corner case in any of the old percpu_ref use cases. This commit therefore calls mem_dump_obj() to dump out any additional available information on the underflowing percpu_ref instance. Cc: Ming Lei <[email protected]> Cc: Jens Axboe <[email protected]> Cc: Joonsoo Kim <[email protected]> Reported-by: Andrii Nakryiko <[email protected]> Tested-by: Naresh Kamboju <[email protected]> Signed-off-by: Paul E. McKenney <[email protected]>
Diffstat (limited to 'net/bluetooth/hci_request.c')
0 files changed, 0 insertions, 0 deletions