From: syzbot <syzbot+01ef7a8da81a975e1ccd@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, anna.luese@v-bien.de,
brauner@kernel.org, jack@suse.cz,
jfs-discussion@lists.sourceforge.net, libaokun1@huawei.com,
linkinjeon@kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
p.raghav@samsung.com, shaggy@kernel.org, sj1557.seo@samsung.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] WARNING in bdev_getblk
Date: Fri, 11 Jul 2025 10:30:02 -0700 [thread overview]
Message-ID: <68714a1a.a00a0220.26a83e.005a.GAE@google.com> (raw)
In-Reply-To: <okx6a3ngonajh7jrzc65ybd4i6bcnkc7gm4mggyo3jlm6s2ojx@yy5jcipsnd3l>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+01ef7a8da81a975e1ccd@syzkaller.appspotmail.com
Tested-by: syzbot+01ef7a8da81a975e1ccd@syzkaller.appspotmail.com
Tested on:
commit: a62b7a37 Add linux-next specific files for 20250711
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13b87a8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bb4e3ec360fcbd0f
dashboard link: https://syzkaller.appspot.com/bug?extid=01ef7a8da81a975e1ccd
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=14c6c68c580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-07-11 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 13:59 [syzbot] [exfat?] WARNING in bdev_getblk syzbot
2025-07-10 9:48 ` [syzbot] [ext4?] " syzbot
2025-07-11 12:27 ` syzbot
2025-07-11 15:51 ` Jan Kara
2025-07-11 16:42 ` Jan Kara
2025-07-11 17:30 ` syzbot [this message]
2025-07-15 10:36 ` Pankaj Raghav (Samsung)
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=68714a1a.a00a0220.26a83e.005a.GAE@google.com \
--to=syzbot+01ef7a8da81a975e1ccd@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=anna.luese@v-bien.de \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=libaokun1@huawei.com \
--cc=linkinjeon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.raghav@samsung.com \
--cc=shaggy@kernel.org \
--cc=sj1557.seo@samsung.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.