LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: syzbot <syzbot+cbe357153903f8d9409a@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: bpf build error
Date: Fri, 24 May 2019 11:24:14 +0200 [thread overview]
Message-ID: <CACT4Y+Y_iA=5Bdtcg+X-ky7Q3m5hxGOexo+246b6b2ow_GLUGg@mail.gmail.com> (raw)
In-Reply-To: <649cac1e-c77c-daf8-6ae7-b02c8571b988@iogearbox.net>
On Fri, May 24, 2019 at 10:08 AM Daniel Borkmann <daniel@iogearbox.net> wrote:
>
> On 05/24/2019 07:28 AM, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: e6f6cd0d bpf: sockmap, fix use after free from sleep in ps..
> > git tree: bpf
> > console output: https://syzkaller.appspot.com/x/log.txt?x=16f116e4a00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=fc045131472947d7
> > dashboard link: https://syzkaller.appspot.com/bug?extid=cbe357153903f8d9409a
> > compiler: gcc (GCC) 9.0.0 20181231 (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+cbe357153903f8d9409a@syzkaller.appspotmail.com
> >
> > net/core/skbuff.c:2340:6: error: ‘struct msghdr’ has no member named ‘flags’
>
> Disregard, tossed from bpf tree.
Let's close it then
#syz invalid
or it will hang open on the dashboard distracting people looking for
open bugs and new bpf build breakages won't be reported.
prev parent reply other threads:[~2019-05-24 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 5:28 syzbot
2019-05-24 8:08 ` Daniel Borkmann
2019-05-24 9:24 ` Dmitry Vyukov [this message]
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='CACT4Y+Y_iA=5Bdtcg+X-ky7Q3m5hxGOexo+246b6b2ow_GLUGg@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+cbe357153903f8d9409a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--subject='Re: bpf build error' \
/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
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).