[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0c10c604-ce38-3733-a442-37945ec36075@pengutronix.de>
Date: Fri, 27 Nov 2020 08:28:44 +0100
From: Marc Kleine-Budde <mkl@...gutronix.de>
To: Oliver Hartkopp <socketcan@...tkopp.net>, dvyukov@...gle.com,
netdev@...r.kernel.org, linux-can@...r.kernel.org
Cc: syzkaller-bugs@...glegroups.com,
syzbot+381d06e0c8eaacb8706f@...kaller.appspotmail.com,
syzbot+d0ddd88c9a7432f041e6@...kaller.appspotmail.com,
syzbot+76d62d3b8162883c7d11@...kaller.appspotmail.com
Subject: Re: [PATCH] can: remove WARN() statement from list operation sanity
check
On 11/26/20 8:21 PM, Oliver Hartkopp wrote:
> 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@...kaller.appspotmail.com
> Reported-by: syzbot+d0ddd88c9a7432f041e6@...kaller.appspotmail.com
> Reported-by: syzbot+76d62d3b8162883c7d11@...kaller.appspotmail.com
> Signed-off-by: Oliver Hartkopp <socketcan@...tkopp.net>
applied to can/testing.
tnx,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists