From: Deepanshu Kartikey <kartikey406@gmail.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca, yi.zhang@huaweicloud.com
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: validate extent entries before caching in ext4_find_extent()
Date: Mon, 29 Sep 2025 21:15:48 +0530 [thread overview]
Message-ID: <20250929154548.360371-1-kartikey406@gmail.com> (raw)
Zhang Yi,
I've prepared v2 based on your feedback about avoiding redundant checks.
After further analysis, I'm detecting the invalid INLINE_DATA + EXTENTS
flag combination rather than just VERITY + INLINE_DATA, as this addresses
the broader issue of mutually exclusive flags.
The v2 patch rejects any inode with both INLINE_DATA and EXTENTS flags set,
which catches this corruption and potentially other similar cases.
Thank you for guiding me to the root cause.
Best regards,
Deepanshu
next reply other threads:[~2025-09-29 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 15:45 Deepanshu Kartikey [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-29 14:00 Deepanshu Kartikey
2025-09-29 5:27 Deepanshu Kartikey
2025-09-29 12:07 ` Zhang Yi
2025-09-29 5:23 Deepanshu Kartikey
2025-09-28 10:09 Deepanshu Kartikey
2025-09-29 2:01 ` Zhang Yi
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=20250929154548.360371-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 \
--cc=yi.zhang@huaweicloud.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
all inboxes | Powered by JetHome®