From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+60c52ca98513a8760a91@syzkaller.appspotmail.com>,
asml.silence@gmail.com, ebiederm@xmission.com,
io-uring@vger.kernel.org, legion@kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel BUG in commit_creds
Date: Thu, 14 Apr 2022 20:29:24 -0600 [thread overview]
Message-ID: <c122ba3e-ef7b-0f70-1972-1bae0ddff651@kernel.dk> (raw)
In-Reply-To: <000000000000a7edb305dca75a50@google.com>
On 4/14/22 7:30 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 40354149f4d7 Add linux-next specific files for 20220414
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1778a95cf00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a44d62051576f6f5
> dashboard link: https://syzkaller.appspot.com/bug?extid=60c52ca98513a8760a91
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1102d2e0f00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e22af4f00000
>
> The issue was bisected to:
>
> commit 6bf9c47a398911e0ab920e362115153596c80432
> Author: Jens Axboe <axboe@kernel.dk>
> Date: Tue Mar 29 16:10:08 2022 +0000
>
> io_uring: defer file assignment
#syz test: git://git.kernel.dk/linux-block io_uring-5.18
--
Jens Axboe
next prev parent reply other threads:[~2022-04-15 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 1:30 [syzbot] kernel BUG in commit_creds syzbot
2022-04-15 2:29 ` Jens Axboe [this message]
2022-04-15 4:04 ` syzbot
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=c122ba3e-ef7b-0f70-1972-1bae0ddff651@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=ebiederm@xmission.com \
--cc=io-uring@vger.kernel.org \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+60c52ca98513a8760a91@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