From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Eric Dumazet <eric.dumazet@gmail.com>,
syzbot <syzbot+b02ff0707a97e4e79ebb@syzkaller.appspotmail.com>,
davem@davemloft.net, glider@google.com,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: KMSAN: uninit-value in can_receive
Date: Tue, 3 Dec 2019 11:37:58 +0100 [thread overview]
Message-ID: <82b02a62-51ff-4568-c33d-90223a2aed86@hartkopp.net> (raw)
In-Reply-To: <0f395f1e-b7d4-6254-2a0c-54029b4dc38f@pengutronix.de>
No. I have analyzed several solutions which turn out to be either unsafe
in processing or need some changes in af_packet :-(
I'm currently very busy @work but will come up with a discussion until
end of this week.
There is no big pressure as the problem is more unpleasant than causing
a real problem right now.
Best regards,
Oliver
On 03/12/2019 11.09, Marc Kleine-Budde wrote:
> On 11/20/19 9:10 PM, Oliver Hartkopp wrote:
> [...]
>> So the KMSAN detection was right at the end :-(
>>
>> I'll take a closer look to enable PF_PACKET to send CAN frames again
>> which will fix up the entire problem.
>
> I'm going to send a pull request today. Do you already have a fix for this?
>
> regards,
> Marc
>
next prev parent reply other threads:[~2019-12-03 10:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 19:05 KMSAN: uninit-value in can_receive syzbot
2019-11-18 20:25 ` Oliver Hartkopp
2019-11-18 20:29 ` Marc Kleine-Budde
2019-11-18 20:49 ` Oliver Hartkopp
2019-11-18 21:15 ` Marc Kleine-Budde
2019-11-19 7:35 ` Oliver Hartkopp
2019-11-19 9:00 ` Oleksij Rempel
2019-11-19 10:08 ` Dmitry Vyukov
2019-11-19 13:06 ` Alexander Potapenko
2019-11-19 16:53 ` Eric Dumazet
2019-11-19 20:24 ` Oliver Hartkopp
2019-11-19 21:09 ` Eric Dumazet
2019-11-20 20:10 ` Oliver Hartkopp
2019-12-03 10:09 ` Marc Kleine-Budde
2019-12-03 10:37 ` Oliver Hartkopp [this message]
2019-12-03 10:40 ` Marc Kleine-Budde
2019-11-26 9:00 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82b02a62-51ff-4568-c33d-90223a2aed86@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=glider@google.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=syzbot+b02ff0707a97e4e79ebb@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.