All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: aalbersh@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/4] libxfs: fix data corruption bug in libxfs_file_write
Date: Thu, 5 Mar 2026 07:56:45 -0800	[thread overview]
Message-ID: <20260305155645.GE57948@frogsfrogsfrogs> (raw)
In-Reply-To: <95b8493c-4e56-03b2-0d9f-7a8ce1675a07@applied-asynchrony.com>

On Thu, Mar 05, 2026 at 08:46:35AM +0100, Holger Hoffstätte wrote:
> On 2026-03-05 05:24, Darrick J. Wong wrote:
> > Cc: <linux-xfs@vger.kernel.org> # v6.13.0
>        ^^^^^^^^^
> 
> I guess meant stable@ here and in the other patches?

No, these are userspace bugfixes and stable@ is only for kernel code.

Nowadays I like to annotate bugfixes for the benefit of anyone
backporting bugfixes to stable QA setups / xfsprogs packages (me), but
the awkward thing is that xfsprogs doesn't have a separate stable
backports list.  Unfortunately, the autobackporting tools all settled on
greg/sasha's shortsighted choice of tag format, so stuffing in an email
address for no good reason is what we're stuck with until someone else
screws up the courage to coordinate a flag day.

e.g.

Fixes: xfsprogs v6.13.0 73fb78e5ee8940 ("mkfs: support copying in large or sparse files")
Fixes: linux v5.8 b707fffda6a3e1 ("xfs: abort consistently on dquot flush failure")

or any such variant would have been clearer about where you're supposed
to apply it, at least in terms of repo and tag.

--D

  reply	other threads:[~2026-03-05 15:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05  4:24 [PATCHSET] xfsprogs: various bug fixes for 6.19 Darrick J. Wong
2026-03-05  4:24 ` [PATCH 1/4] misc: fix a few memory leaks Darrick J. Wong
2026-03-05 14:03   ` Christoph Hellwig
2026-03-05  4:24 ` [PATCH 2/4] libxfs: fix data corruption bug in libxfs_file_write Darrick J. Wong
2026-03-05  7:46   ` Holger Hoffstätte
2026-03-05 15:56     ` Darrick J. Wong [this message]
2026-03-05 14:04   ` Christoph Hellwig
2026-03-05  4:24 ` [PATCH 3/4] mkfs: fix protofile data corruption when in/out file block sizes don't match Darrick J. Wong
2026-03-05 14:04   ` Christoph Hellwig
2026-03-05  4:24 ` [PATCH 4/4] mkfs: fix log sunit automatic configuration Darrick J. Wong
2026-03-05 14:05   ` Christoph Hellwig
2026-03-05 22:56   ` Darrick J. Wong
  -- strict thread matches above, loose matches on Subject: below --
2026-03-10  3:24 [PATCHSET v2] xfsprogs: various bug fixes for 6.19 Darrick J. Wong
2026-03-10  3:25 ` [PATCH 2/4] libxfs: fix data corruption bug in libxfs_file_write Darrick J. Wong

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=20260305155645.GE57948@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=aalbersh@kernel.org \
    --cc=holger@applied-asynchrony.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.