From: syzbot <syzbot+5320383e16029ba057ff@syzkaller.appspotmail.com>
To: Anna.Schumaker@Netapp.com, Anna.Schumaker@netapp.com,
axboe@kernel.dk, casey@schaufler-ca.com, dhowells@redhat.com,
dvyukov@google.com, io-uring@vger.kernel.org, jannh@google.com,
keescook@chromium.org, kstewart@linuxfoundation.org,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, neilb@suse.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
viro@zeniv.linux.org.uk
Subject: Re: general protection fault in override_creds
Date: Mon, 02 Dec 2019 07:22:00 -0800 [thread overview]
Message-ID: <0000000000001b5b540598ba2498@google.com> (raw)
In-Reply-To: <000000000000da160a0598b2c704@google.com>
syzbot has bisected this bug to:
commit 181e448d8709e517c9c7b523fcd209f24eb38ca7
Author: Jens Axboe <axboe@kernel.dk>
Date: Mon Nov 25 15:52:30 2019 +0000
io_uring: async workers should inherit the user creds
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10424ceae00000
start commit: b94ae8ad Merge tag 'seccomp-v5.5-rc1' of git://git.kernel...
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=12424ceae00000
console output: https://syzkaller.appspot.com/x/log.txt?x=14424ceae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=ff560c3de405258c
dashboard link: https://syzkaller.appspot.com/bug?extid=5320383e16029ba057ff
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12dd682ae00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16290abce00000
Reported-by: syzbot+5320383e16029ba057ff@syzkaller.appspotmail.com
Fixes: 181e448d8709 ("io_uring: async workers should inherit the user
creds")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-12-02 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000da160a0598b2c704@google.com>
2019-12-02 6:40 ` general protection fault in override_creds Dmitry Vyukov
2019-12-02 15:40 ` Jens Axboe
2019-12-02 15:49 ` Jens Axboe
2019-12-02 15:22 ` syzbot [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=0000000000001b5b540598ba2498@google.com \
--to=syzbot+5320383e16029ba057ff@syzkaller.appspotmail.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=axboe@kernel.dk \
--cc=casey@schaufler-ca.com \
--cc=dhowells@redhat.com \
--cc=dvyukov@google.com \
--cc=io-uring@vger.kernel.org \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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