All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Dave Chinner <dgc@kernel.org>
Cc: Hans Holmberg <hans.holmberg@wdc.com>,
	Carlos Maiolino <cem@kernel.org>,
	"Darrick J . Wong" <djwong@kernel.org>,
	Dave Chinner <david@fromorbit.com>,
	Christoph Hellwig <hch@lst.de>,
	Damien Le Moal <dlemoal@kernel.org>,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: handle racing deletions in xfs_zone_gc_iter_irec
Date: Mon, 18 May 2026 14:43:11 +0200	[thread overview]
Message-ID: <20260518124311.GA4694@lst.de> (raw)
In-Reply-To: <agrERjRq10bm0rrY@dread>

On Mon, May 18, 2026 at 05:48:22PM +1000, Dave Chinner wrote:
> > -		if (error == -ENOENT) {
> > +		if (error == -ENOENT || error == -EINVAL) {
> >  			iter->rec_idx++;
> >  			goto retry;
> >  		}
> 
> Why did you choose to do this? I was expecting the updated fix to be
> dropping XFS_IGET_UNTRUSTED from the xfs_iget() call because the
> inode numbers are coming from a trusted source (i.e. the rmapbt) and
> this would then return the expected -ENOENT on unlink races instead
> of -EINVAL....

The inode number is not trusted.  It comes from a stale copy of the rmap,
and the inode cluster can have been freed and reallocated.  Dropping
XFS_IGET_UNTRUSTED would be highly dangerous as it could cause iget
to interprete something else as an inode struture in this case and
easily cause kernel crashes.


  parent reply	other threads:[~2026-05-18 12:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  6:52 [PATCH v2] xfs: handle racing deletions in xfs_zone_gc_iter_irec Hans Holmberg
2026-05-18  7:48 ` Dave Chinner
2026-05-18  8:55   ` Hans Holmberg
2026-05-18  9:17     ` Damien Le Moal
2026-05-18  9:44     ` Dave Chinner
2026-05-18 12:45       ` Christoph Hellwig
2026-05-18 12:43   ` Christoph Hellwig [this message]
2026-05-19  7:15 ` Christoph Hellwig
2026-05-30  6:35 ` 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=20260518124311.GA4694@lst.de \
    --to=hch@lst.de \
    --cc=cem@kernel.org \
    --cc=david@fromorbit.com \
    --cc=dgc@kernel.org \
    --cc=djwong@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hans.holmberg@wdc.com \
    --cc=linux-xfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.