From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+2c73319c406f1987d156@syzkaller.appspotmail.com>,
Alexei Starovoitov <ast@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
mcgrof@kernel.org,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: bpf-next boot error: KASAN: use-after-free Write in call_usermodehelper_exec_work
Date: Thu, 7 Jun 2018 20:12:22 +0200 [thread overview]
Message-ID: <20180607181222.GD5527@wotan.suse.de> (raw)
In-Reply-To: <20180607160659.g3x2pwdbxcsx5yxs@ast-mbp.dhcp.thefacebook.com>
On Thu, Jun 07, 2018 at 09:07:01AM -0700, Alexei Starovoitov wrote:
> On Thu, Jun 07, 2018 at 02:19:16PM +0200, Dmitry Vyukov wrote:
> > On Mon, Jun 4, 2018 at 10:21 PM, syzbot
> > <syzbot+2c73319c406f1987d156@syzkaller.appspotmail.com> wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit: 69b450789136 Merge branch 'misc-BPF-improvements'
> > > git tree: bpf-next
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=1080d1d7800000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=e4078980b886800c
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=2c73319c406f1987d156
> > > compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> > >
> > > Unfortunately, I don't have any reproducer for this crash yet.
> > >
> > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > Reported-by: syzbot+2c73319c406f1987d156@syzkaller.appspotmail.com
> >
> >
> > This crash now happens on every other boot of mainline tree. This
> > prevents syzbot testing of new code, and just boots machine with
> > corrupted memory. Were there any recent changes in umh? +Alexei, you
> > seem to touch it last. Could your change cause this?
>
> looking into it. I think I see the issue. Trying to reproduce.
And this is why a test driver would be useful ;)
Luis
next prev parent reply other threads:[~2018-06-07 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 20:21 bpf-next boot error: KASAN: use-after-free Write in call_usermodehelper_exec_work syzbot
2018-06-07 12:19 ` Dmitry Vyukov
2018-06-07 16:07 ` Alexei Starovoitov
2018-06-07 18:12 ` Luis R. Rodriguez [this message]
2018-06-07 18:32 ` Dmitry Vyukov
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=20180607181222.GD5527@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2c73319c406f1987d156@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).