All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: cem@kernel.org, stable@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 04/13] xfs: reattach dquots after changing inode ids
Date: Mon, 12 Oct 2026 05:44:05 -0700	[thread overview]
Message-ID: <aszWFcgPtr5cFKdT@infradead.org> (raw)
In-Reply-To: <179151614707.3163896.4351468047280563575.stgit@frogsfrogsfrogs>

Sashiko still feels unhappy about this one, and the complaints look
kinda legit.


  reply	other threads:[~2026-10-12 12:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09  6:14 [PATCHSET v2] xfs: LLM-inspired bug fixes, part 21 Darrick J. Wong
2026-10-09  6:15 ` [PATCH 01/13] xfs: check for termination during rmap btree walk Darrick J. Wong
2026-10-09  6:15 ` [PATCH 02/13] xfs: don't subtract excess usage twice when computing agf_btreeblks Darrick J. Wong
2026-10-12 12:42   ` Christoph Hellwig
2026-10-09  6:15 ` [PATCH 03/13] xfs: abort directory tree repair whenever dl->aborted is set Darrick J. Wong
2026-10-09  6:15 ` [PATCH 04/13] xfs: reattach dquots after changing inode ids Darrick J. Wong
2026-10-12 12:44   ` Christoph Hellwig [this message]
2026-10-12 15:15     ` Darrick J. Wong
2026-10-09  6:16 ` [PATCH 05/13] xfs: never reset the default quota timer Darrick J. Wong
2026-10-09  6:16 ` [PATCH 06/13] xfs: fix correction of unwritten extents in quota file data fork Darrick J. Wong
2026-10-12 12:44   ` Christoph Hellwig
2026-10-09  6:16 ` [PATCH 07/13] xfs: always report inode repair setup failures Darrick J. Wong
2026-10-09  6:16 ` [PATCH 08/13] xfs: range-check bc_levels array access in scrub tracepoints Darrick J. Wong
2026-10-09  6:17 ` [PATCH 09/13] xfs: reject absurdly large xattr value lengths in xchk_xattr_actor Darrick J. Wong
2026-10-09  6:17 ` [PATCH 10/13] xfs: break out xattr entry checks into separate functions Darrick J. Wong
2026-10-12 12:45   ` Christoph Hellwig
2026-10-09  6:17 ` [PATCH 11/13] xfs: check for buffer overruns when examining local/remote xattr entries Darrick J. Wong
2026-10-12 12:45   ` Christoph Hellwig
2026-10-09  6:17 ` [PATCH 12/13] xfs: clarify various parts of the bitmap API Darrick J. Wong
2026-10-12 12:45   ` Christoph Hellwig
2026-10-09  6:18 ` [PATCH 13/13] xfs: complain loudly when dirtree checker finds broken links Darrick J. Wong
2026-10-12 12:46   ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2026-10-12 15:20 [PATCHSET v3] xfs: LLM-inspired bug fixes, part 21 Darrick J. Wong
2026-10-12 15:21 ` [PATCH 04/13] xfs: reattach dquots after changing inode ids Darrick J. Wong
2026-10-13  7:35   ` Christoph Hellwig

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=aszWFcgPtr5cFKdT@infradead.org \
    --to=hch@infradead.org \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=stable@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.