From: syzbot <syzbot+3c9f079f8fb1d7d331be@syzkaller.appspotmail.com>
To: Yuezhang.Mo@sony.com, brauner@kernel.org, daniel.palmer@sony.com,
hirofumi@mail.parknet.co.jp, jack@suse.com, jack@suse.cz,
jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
linkinjeon@kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mark@fasheh.com, ocfs2-devel@lists.linux.dev,
sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, viro@zeniv.linux.org.uk, wataru.aoyama@sony.com,
yuezhang.mo@sony.com
Subject: Re: [syzbot] [ocfs2?] [ext4?] WARNING in __find_get_block (2)
Date: Sat, 15 Feb 2025 22:11:03 -0800 [thread overview]
Message-ID: <67b18177.050a0220.54b41.0004.GAE@google.com> (raw)
In-Reply-To: <6741d52e.050a0220.1cc393.0010.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 70465acbb0ce1bb69447acf32f136c8153cda0de
Author: Yuezhang Mo <Yuezhang.Mo@sony.com>
Date: Mon Dec 2 01:53:17 2024 +0000
exfat: fix exfat_find_empty_entry() not returning error on failure
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15d62bf8580000
start commit: f44d154d6e3d Merge tag 'soc-fixes-6.13' of git://git.kerne..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1234f097ee657d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=3c9f079f8fb1d7d331be
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e302df980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1265b4f8580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: exfat: fix exfat_find_empty_entry() not returning error on failure
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-02-16 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 13:14 [syzbot] [udf?] WARNING in __find_get_block (2) syzbot
2024-12-17 2:43 ` [syzbot] [ext4?] " syzbot
2024-12-17 14:35 ` syzbot
2025-02-16 6:11 ` 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=67b18177.050a0220.54b41.0004.GAE@google.com \
--to=syzbot+3c9f079f8fb1d7d331be@syzkaller.appspotmail.com \
--cc=Yuezhang.Mo@sony.com \
--cc=brauner@kernel.org \
--cc=daniel.palmer@sony.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linkinjeon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=wataru.aoyama@sony.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