[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176049624801.779602.18399405052764304689.b4-ty@mit.edu>
Date: Tue, 14 Oct 2025 22:44:13 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: adilger.kernel@...ger.ca, Deepanshu Kartikey <kartikey406@...il.com>
Cc: "Theodore Ts'o" <tytso@....edu>, yi.zhang@...weicloud.com,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
syzbot+038b7bf43423e132b308@...kaller.appspotmail.com,
Zhang Yi <yi.zhang@...wei.com>
Subject: Re: [PATCH v4] ext4: detect invalid INLINE_DATA + EXTENTS flag combination
On Tue, 30 Sep 2025 16:58:10 +0530, Deepanshu Kartikey wrote:
> syzbot reported a BUG_ON in ext4_es_cache_extent() when opening a verity
> file on a corrupted ext4 filesystem mounted without a journal.
>
> The issue is that the filesystem has an inode with both the INLINE_DATA
> and EXTENTS flags set:
>
> EXT4-fs error (device loop0): ext4_cache_extents:545: inode #15:
> comm syz.0.17: corrupted extent tree: lblk 0 < prev 66
>
> [...]
Applied, thanks!
[1/1] ext4: detect invalid INLINE_DATA + EXTENTS flag combination
commit: 1d3ad183943b38eec2acf72a0ae98e635dc8456b
Best regards,
--
Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists