public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: zlang@redhat.com, linux-ext4@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 1/3] xfs/018: remove inline xattr recovery tests
Date: Thu, 5 Feb 2026 22:27:16 -0800	[thread overview]
Message-ID: <20260206062716.GO7686@frogsfrogsfrogs> (raw)
In-Reply-To: <aYWJhGU-7YfXr2HR@infradead.org>

On Thu, Feb 05, 2026 at 10:26:12PM -0800, Christoph Hellwig wrote:
> On Thu, Feb 05, 2026 at 10:22:22PM -0800, Darrick J. Wong wrote:
> > On Thu, Feb 05, 2026 at 09:59:42PM -0800, Christoph Hellwig wrote:
> > > On Thu, Feb 05, 2026 at 08:56:24AM -0800, Darrick J. Wong wrote:
> > > > "In Linux 7.0 we've changed the extended attribute update code to try to
> > > > take a shortcut for performance reasons.  Before walking through the
> > > > attr intent state machine (slow), the update will check to see if the
> > > > attr structure is in short format and will stay in that format after the
> > > > change.  If so, then the incore inode can be updated and logged, and the
> > > > update is complete (fast) in a single transaction.
> > > > 
> > > > "(Obviously, for complex attr structures or large changes we still walk
> > > > through the intent machinery.)
> > > > 
> > > > "However, xfs/018 tests the behavior of the "larp" error injector, which
> > > > only triggers from inside the attr intent state machine.  Therefore, the
> > > > short format tests don't actually trip the injector.  It makes no sense
> > > > to add a new larp injection callsite for the shortcut because either the
> > > > single transaction gets written to disk or it doesn't."
> > > 
> > > Make sense, but from looking at the test I'm still a bit confused
> > > why it fails (vs just not testing something too useful)
> > 
> > The golden output no longer matches because the attr update doesn't
> > return EIO and shut down the filesystem due to the larp injection.
> 
> Ah, that's the missing bit.  Can you add that blurb to the commit
> message?

Will do!

> With that and the above:
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>

Thanks!

--D

  reply	other threads:[~2026-02-06  6:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 19:11 [PATCHSET] fstests: more random fixes for v2026.01.27 Darrick J. Wong
2026-02-02 19:11 ` [PATCH 1/3] xfs/018: remove inline xattr recovery tests Darrick J. Wong
2026-02-03  5:22   ` Christoph Hellwig
2026-02-05 16:56     ` Darrick J. Wong
2026-02-05 17:19       ` Carlos Maiolino
2026-02-06  5:59       ` Christoph Hellwig
2026-02-06  6:22         ` Darrick J. Wong
2026-02-06  6:26           ` Christoph Hellwig
2026-02-06  6:27             ` Darrick J. Wong [this message]
2026-02-06 21:54   ` [PATCH v1.1 " Darrick J. Wong
2026-02-02 19:11 ` [PATCH 2/3] xfs/620: force xattr leaf format for this test Darrick J. Wong
2026-02-03  5:22   ` Christoph Hellwig
2026-02-05 17:15   ` Carlos Maiolino
2026-02-02 19:11 ` [PATCH 3/3] generic/749: don't write a ton of _mread output to seqres.full Darrick J. Wong
2026-02-03  5:23   ` Christoph Hellwig
2026-02-05 17:17   ` Carlos Maiolino

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=20260206062716.GO7686@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=zlang@redhat.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