From: syzbot <syzbot+a2b9a4ed0d61b1efb3f5@syzkaller.appspotmail.com>
To: brauner@kernel.org, djwong@kernel.org, hch@infradead.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [iomap?] general protection fault in iomap_dio_bio_end_io
Date: Mon, 24 Nov 2025 04:49:02 -0800 [thread overview]
Message-ID: <6924543e.a70a0220.d98e3.008c.GAE@google.com> (raw)
In-Reply-To: <aSQlrJxWxNyCVt3z@infradead.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+a2b9a4ed0d61b1efb3f5@syzkaller.appspotmail.com
Tested-by: syzbot+a2b9a4ed0d61b1efb3f5@syzkaller.appspotmail.com
Tested on:
commit: 660f4047 iomap: allocate s_dio_done_wq for async reads..
git tree: git://git.infradead.org/users/hch/misc.git iomap-dio-read-fix
console output: https://syzkaller.appspot.com/x/log.txt?x=15c4c612580000
kernel config: https://syzkaller.appspot.com/x/.config?x=68d11c703cf8e4a0
dashboard link: https://syzkaller.appspot.com/bug?extid=a2b9a4ed0d61b1efb3f5
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2025-11-24 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 0:01 [syzbot] [iomap?] general protection fault in iomap_dio_bio_end_io syzbot
2025-11-24 8:53 ` [PATCH Next] iomap: Add sanity check for dio done workqueue Edward Adam Davis
2025-11-24 9:18 ` Christoph Hellwig
2025-11-24 9:30 ` [syzbot] [iomap?] general protection fault in iomap_dio_bio_end_io Christoph Hellwig
2025-11-24 12:49 ` 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=6924543e.a70a0220.d98e3.008c.GAE@google.com \
--to=syzbot+a2b9a4ed0d61b1efb3f5@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--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).