From: Deepanshu Kartikey <kartikey406@gmail.com>
To: tytso@mit.edu
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: reject inline data flag when i_extra_isize is zero
Date: Fri, 3 Oct 2025 06:21:03 +0530 [thread overview]
Message-ID: <20251003005103.2399934-1-kartikey406@gmail.com> (raw)
Looking at the syzbot logs more carefully, I see the initial 'acceptance' was
because the filesystem failed to mount ('VFS: Can't find ext4 filesystem'),
so the bug couldn't be triggered at all. My patches were never actually tested
against the real bug.
I apologize for the confusion. I still cannot test locally to determine what
the actual corruption scenario is. Today I have re-tested my same patch in
syzbot and it is failing.
Best regards,
Deepanshu
next reply other threads:[~2025-10-03 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 0:51 Deepanshu Kartikey [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-02 10:41 [PATCH] ext4: reject inline data flag when i_extra_isize is zero Deepanshu Kartikey
2025-10-02 19:57 ` Theodore Ts'o
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=20251003005103.2399934-1-kartikey406@gmail.com \
--to=kartikey406@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox