From: Pavel Begunkov <asml.silence@gmail.com>
To: syzbot <syzbot+1bcb75613069ad4957fc@syzkaller.appspotmail.com>,
axboe@kernel.dk, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] WARNING in __io_submit_flush_completions
Date: Tue, 24 Dec 2024 13:57:10 +0000 [thread overview]
Message-ID: <62983fd8-d5f6-470e-88e2-6f4737bfed79@gmail.com> (raw)
In-Reply-To: <6765b448.050a0220.15b956.00d4.GAE@google.com>
On 12/20/24 18:15, syzbot wrote:
>
> HEAD commit: 8faabc041a00 Merge tag 'net-6.13-rc4' of git://git.kernel...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=13249e0f980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c22efbd20f8da769
> dashboard link: https://syzkaller.appspot.com/bug?extid=1bcb75613069ad4957fc
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12172fe8580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111f92df980000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/0bdb6cecaf61/disk-8faabc04.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/98b22dfadac0/vmlinux-8faabc04.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/65a511d3ba7f/bzImage-8faabc04.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+1bcb75613069ad4957fc@syzkaller.appspotmail.com
I can't reproduce but it makes sense. It shouldn't be a real
problem as it's protected by ->uring_lock
--
Pavel Begunkov
next prev parent reply other threads:[~2024-12-24 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 18:15 [syzbot] [io-uring?] WARNING in __io_submit_flush_completions syzbot
2024-12-24 13:57 ` Pavel Begunkov [this message]
2025-01-05 13:52 ` Pavel Begunkov
2025-01-05 14:13 ` 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=62983fd8-d5f6-470e-88e2-6f4737bfed79@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+1bcb75613069ad4957fc@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