From: Daniel Borkmann <daniel@iogearbox.net>
To: syzbot <syzbot+491c1b7565ba9069ecae@syzkaller.appspotmail.com>
Cc: ast@kernel.org, bjorn.topel@intel.com, bpf@vger.kernel.org,
davem@davemloft.net, hawk@kernel.org,
jakub.kicinski@netronome.com, john.fastabend@gmail.com,
jonathan.lemon@gmail.com, kafai@fb.com,
linux-kernel@vger.kernel.org, magnus.karlsson@intel.com,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com
Subject: Re: general protection fault in xsk_map_update_elem
Date: Tue, 24 Sep 2019 00:50:50 +0200 [thread overview]
Message-ID: <20190923225050.GA26406@pc-63.home> (raw)
In-Reply-To: <0000000000006a3a2f05933a5c53@google.com>
On Mon, Sep 23, 2019 at 08:49:11AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: b41dae06 Merge tag 'xfs-5.4-merge-7' of git://git.kernel.o..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=130b25ad600000
> kernel config: https://syzkaller.appspot.com/x/.config?x=dfcf592db22b9132
> dashboard link: https://syzkaller.appspot.com/bug?extid=491c1b7565ba9069ecae
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155a0c29600000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=172bf6d9600000
>
> The bug was bisected to:
>
> commit 0402acd683c678874df6bdbc23530ca07ea19353
> Author: Björn Töpel <bjorn.topel@intel.com>
> Date: Thu Aug 15 09:30:13 2019 +0000
>
> xsk: remove AF_XDP socket from map when the socket is released
Bjorn, PTAL, thanks.
next prev parent reply other threads:[~2019-09-23 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 15:49 general protection fault in xsk_map_update_elem syzbot
2019-09-23 22:50 ` Daniel Borkmann [this message]
2019-09-24 5:05 ` Björn Töpel
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=20190923225050.GA26406@pc-63.home \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+491c1b7565ba9069ecae@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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).