From: ebiederm@xmission.com (Eric W. Biederman)
To: syzbot <syzbot+f625baafb9a1c4bfc3f6@syzkaller.appspotmail.com>
Cc: aarcange@redhat.com, akpm@linux-foundation.org,
andrea.parri@amarulasolutions.com, ast@kernel.org,
avagin@gmail.com, daniel@iogearbox.net, dbueso@suse.de,
john.fastabend@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, oleg@redhat.com, prsood@codeaurora.org,
syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in mm_update_next_owner
Date: Mon, 10 Jun 2019 16:27:15 -0500 [thread overview]
Message-ID: <87ftoh6si4.fsf@xmission.com> (raw)
In-Reply-To: <000000000000c0d84e058ad677aa@google.com> (syzbot's message of "Sat, 08 Jun 2019 14:17:00 -0700")
syzbot <syzbot+f625baafb9a1c4bfc3f6@syzkaller.appspotmail.com> writes:
> syzbot has bisected this bug to:
>
> commit e9db4ef6bf4ca9894bb324c76e01b8f1a16b2650
> Author: John Fastabend <john.fastabend@gmail.com>
> Date: Sat Jun 30 13:17:47 2018 +0000
>
> bpf: sockhash fix omitted bucket lock in sock_close
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15e978e1a00000
> start commit: 38e406f6 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
> git tree: net
> final crash: https://syzkaller.appspot.com/x/report.txt?x=17e978e1a00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=13e978e1a00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=60564cb52ab29d5b
> dashboard link: https://syzkaller.appspot.com/bug?extid=f625baafb9a1c4bfc3f6
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1193d81ea00000
>
> Reported-by: syzbot+f625baafb9a1c4bfc3f6@syzkaller.appspotmail.com
> Fixes: e9db4ef6bf4c ("bpf: sockhash fix omitted bucket lock in sock_close")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
How is mm_update_next_owner connected to bpf?
Eric
next prev parent reply other threads:[~2019-06-10 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 19:13 general protection fault in mm_update_next_owner syzbot
2019-06-08 21:17 ` syzbot
2019-06-10 21:27 ` Eric W. Biederman [this message]
2019-06-11 7:00 ` 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=87ftoh6si4.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andrea.parri@amarulasolutions.com \
--cc=ast@kernel.org \
--cc=avagin@gmail.com \
--cc=daniel@iogearbox.net \
--cc=dbueso@suse.de \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=prsood@codeaurora.org \
--cc=syzbot+f625baafb9a1c4bfc3f6@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).