From: syzbot <syzbot+307da6ca5cb0d01d581a@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, bfoster@redhat.com, jack@suse.cz,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, ritesh.list@gmail.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] WARNING in ext4_iomap_begin (2)
Date: Fri, 29 Sep 2023 07:29:18 -0700 [thread overview]
Message-ID: <000000000000f147d80606803f1d@google.com> (raw)
In-Reply-To: <0000000000005697bd05fe4aea49@google.com>
syzbot has bisected this issue to:
commit 310ee0902b8d9d0a13a5a13e94688a5863fa29c2
Author: Brian Foster <bfoster@redhat.com>
Date: Tue Mar 14 13:07:59 2023 +0000
ext4: allow concurrent unaligned dio overwrites
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10a8442a680000
start commit: 9ed22ae6be81 Merge tag 'spi-fix-v6.6-rc3' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12a8442a680000
console output: https://syzkaller.appspot.com/x/log.txt?x=14a8442a680000
kernel config: https://syzkaller.appspot.com/x/.config?x=12da82ece7bf46f9
dashboard link: https://syzkaller.appspot.com/bug?extid=307da6ca5cb0d01d581a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15eb672e680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16219bc6680000
Reported-by: syzbot+307da6ca5cb0d01d581a@syzkaller.appspotmail.com
Fixes: 310ee0902b8d ("ext4: allow concurrent unaligned dio overwrites")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-09-29 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 3:29 [syzbot] [ext4?] WARNING in ext4_iomap_begin (2) syzbot
2023-09-29 8:21 ` syzbot
2023-09-29 17:25 ` Brian Foster
2023-09-29 17:45 ` syzbot
2023-09-29 19:19 ` Brian Foster
2023-09-29 19:40 ` syzbot
2023-09-29 14:29 ` 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=000000000000f147d80606803f1d@google.com \
--to=syzbot+307da6ca5cb0d01d581a@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=bfoster@redhat.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.