linux-kernel - Re: [syzbot] [ext4?] possible deadlock in ext4_destroy_inline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251202015642.GB29113@macsyma.lan>
Date: Mon, 1 Dec 2025 20:56:42 -0500
From: "Theodore Tso" <tytso@....edu>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Andreas Dilger <adilger@...ger.ca>,
        syzbot <syzbot+bb2455d02bda0b5701e3@...kaller.appspotmail.com>,
        linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [ext4?] possible deadlock in ext4_destroy_inline_data
 (2)

On Mon, Dec 01, 2025 at 03:25:52PM -0800, Darrick J. Wong wrote:
> 
> Or expand extra_isize only when someone tries to set an inode field that
> actually requires it?  e.g. whenever setting the project id?

Or when adding/removing/changing an extended attribute, especially one
stored in the inode table, since that's when we need to make sure
we've left room the expanded inode.

Certainly if all we are doing is, say, updating the atime, trying to
move out an extended attribute to make room for an inode field that
might never get used is kind of a waste.

We just haven't really focused on this much, since we haven't needed
to expand the inode in many years.  But if someone wants to work on
it, that would be great!

					- Ted