public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Andreas Dilger <adilger@dilger.ca>,
	syzbot <syzbot+bb2455d02bda0b5701e3@syzkaller.appspotmail.com>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] possible deadlock in ext4_destroy_inline_data (2)
Date: Mon, 1 Dec 2025 20:56:42 -0500	[thread overview]
Message-ID: <20251202015642.GB29113@macsyma.lan> (raw)
In-Reply-To: <20251201232552.GA89435@frogsfrogsfrogs>

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

  reply	other threads:[~2025-12-02  1:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 22:08 [syzbot] [ext4?] possible deadlock in ext4_destroy_inline_data (2) syzbot
2025-12-01  6:21 ` syzbot
2025-12-01 16:16 ` Theodore Tso
2025-12-01 23:17   ` Andreas Dilger
2025-12-01 23:25     ` Darrick J. Wong
2025-12-02  1:56       ` Theodore Tso [this message]
2025-12-02  1:14     ` Theodore Tso

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=20251202015642.GB29113@macsyma.lan \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=djwong@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+bb2455d02bda0b5701e3@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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