From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+0b92850d68d9b12934f5@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, akpm@linux-foundation.org,
apopple@nvidia.com, byungchul@sk.com, david@redhat.com,
gourry@gourry.net, jack@suse.cz, joshua.hahnjy@gmail.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, matthew.brost@intel.com, rakie.kim@sk.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
ying.huang@linux.alibaba.com, ziy@nvidia.com
Subject: Re: [syzbot] [mm?] [ext4?] WARNING in ext4_init_orphan_info
Date: Tue, 9 Sep 2025 12:59:38 +0200 [thread overview]
Message-ID: <puvp7vzyv427rdfs6jkdfi5qdhfrotxahijtah5wwvlh4s3ykw@tq5ytvrlwnlh> (raw)
In-Reply-To: <68bf33e3.a70a0220.7a912.02c3.GAE@google.com>
On Mon 08-09-25 12:52:03, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 02f310fcf47fa9311d6ba2946a8d19e7d7d11f37
> Author: Jan Kara <jack@suse.cz>
> Date: Mon Aug 16 09:57:06 2021 +0000
>
> ext4: Speedup ext4 orphan inode handling
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16645562580000
> start commit: 76eeb9b8de98 Linux 6.17-rc5
> git tree: upstream
> final oops: https://syzkaller.appspot.com/x/report.txt?x=15645562580000
> console output: https://syzkaller.appspot.com/x/log.txt?x=11645562580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=429771c55b615e85
> dashboard link: https://syzkaller.appspot.com/bug?extid=0b92850d68d9b12934f5
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=168d2562580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15869562580000
>
> Reported-by: syzbot+0b92850d68d9b12934f5@syzkaller.appspotmail.com
> Fixes: 02f310fcf47f ("ext4: Speedup ext4 orphan inode handling")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Hum, yes, we don't verify orphan file size is sane. I'll send a fix.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2025-09-09 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 18:45 syzbot
2025-09-08 19:52 ` syzbot
2025-09-09 10:59 ` Jan Kara [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=puvp7vzyv427rdfs6jkdfi5qdhfrotxahijtah5wwvlh4s3ykw@tq5ytvrlwnlh \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=david@redhat.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=rakie.kim@sk.com \
--cc=syzbot+0b92850d68d9b12934f5@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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