summaryrefslogtreecommitdiffstats
path: root/arch/h8300/lib/libgcc.h
diff options
context:
space:
mode:
authorOliver Hartkopp <socketcan@hartkopp.net>2020-11-26 20:21:40 +0100
committerMarc Kleine-Budde <mkl@pengutronix.de>2020-11-27 10:49:28 +0100
commitd73ff9b7c4eacaba0fd956d14882bcae970f8307 (patch)
tree4ca1fa9ce82b83b636d80efc7dc4c3af5d1d8e2b /arch/h8300/lib/libgcc.h
parent5c7d55bded77da6db7c5d249610e3a2eed730b3c (diff)
downloadlinux-d73ff9b7c4eacaba0fd956d14882bcae970f8307.tar.gz
linux-d73ff9b7c4eacaba0fd956d14882bcae970f8307.tar.bz2
linux-d73ff9b7c4eacaba0fd956d14882bcae970f8307.zip
can: af_can: can_rx_unregister(): remove WARN() statement from list operation sanity check
To detect potential bugs in CAN protocol implementations (double removal of receiver entries) a WARN() statement has been used if no matching list item was found for removal. The fault injection issued by syzkaller was able to create a situation where the closing of a socket runs simultaneously to the notifier call chain for removing the CAN network device in use. This case is very unlikely in real life but it doesn't break anything. Therefore we just replace the WARN() statement with pr_warn() to preserve the notification for the CAN protocol development. Reported-by: syzbot+381d06e0c8eaacb8706f@syzkaller.appspotmail.com Reported-by: syzbot+d0ddd88c9a7432f041e6@syzkaller.appspotmail.com Reported-by: syzbot+76d62d3b8162883c7d11@syzkaller.appspotmail.com Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Link: https://lore.kernel.org/r/20201126192140.14350-1-socketcan@hartkopp.net Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'arch/h8300/lib/libgcc.h')
0 files changed, 0 insertions, 0 deletions