From: <gregkh@linuxfoundation.org>
To: amir73il@gmail.com,catherine.hoang@oracle.com,chandan.babu@oracle.com,chandanbabu@kernel.org,djwong@kernel.org,gregkh@linuxfoundation.org,hch@lst.de,leah.rumancik@gmail.com,xfs-stable@lists.linux.dev
Cc: <stable-commits@vger.kernel.org>
Subject: Patch "xfs: only remap the written blocks in xfs_reflink_end_cow_extent" has been added to the 6.1-stable tree
Date: Thu, 30 Jan 2025 09:41:00 +0100 [thread overview]
Message-ID: <2025013000-appealing-debtless-0e69@gregkh> (raw)
In-Reply-To: <20250129184717.80816-13-leah.rumancik@gmail.com>
This is a note to let you know that I've just added the patch titled
xfs: only remap the written blocks in xfs_reflink_end_cow_extent
to the 6.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
xfs-only-remap-the-written-blocks-in-xfs_reflink_end_cow_extent.patch
and it can be found in the queue-6.1 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
From stable+bounces-111224-greg=kroah.com@vger.kernel.org Wed Jan 29 19:48:00 2025
From: Leah Rumancik <leah.rumancik@gmail.com>
Date: Wed, 29 Jan 2025 10:47:10 -0800
Subject: xfs: only remap the written blocks in xfs_reflink_end_cow_extent
To: stable@vger.kernel.org
Cc: xfs-stable@lists.linux.dev, amir73il@gmail.com, chandan.babu@oracle.com, catherine.hoang@oracle.com, Christoph Hellwig <hch@lst.de>, "Darrick J. Wong" <djwong@kernel.org>, Chandan Babu R <chandanbabu@kernel.org>, Leah Rumancik <leah.rumancik@gmail.com>
Message-ID: <20250129184717.80816-13-leah.rumancik@gmail.com>
From: Christoph Hellwig <hch@lst.de>
[ Upstream commit 55f669f34184ecb25b8353f29c7f6f1ae5b313d1 ]
xfs_reflink_end_cow_extent looks up the COW extent and the data fork
extent at offset_fsb, and then proceeds to remap the common subset
between the two.
It does however not limit the remapped extent to the passed in
[*offset_fsbm end_fsb] range and thus potentially remaps more blocks than
the one handled by the current I/O completion. This means that with
sufficiently large data and COW extents we could be remapping COW fork
mappings that have not been written to, leading to a stale data exposure
on a powerfail event.
We use to have a xfs_trim_range to make the remap fit the I/O completion
range, but that got (apparently accidentally) removed in commit
df2fd88f8ac7 ("xfs: rewrite xfs_reflink_end_cow to use intents").
Note that I've only found this by code inspection, and a test case would
probably require very specific delay and error injection.
Fixes: df2fd88f8ac7 ("xfs: rewrite xfs_reflink_end_cow to use intents")
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
Signed-off-by: Leah Rumancik <leah.rumancik@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
fs/xfs/xfs_reflink.c | 1 +
1 file changed, 1 insertion(+)
--- a/fs/xfs/xfs_reflink.c
+++ b/fs/xfs/xfs_reflink.c
@@ -783,6 +783,7 @@ xfs_reflink_end_cow_extent(
}
}
del = got;
+ xfs_trim_extent(&del, *offset_fsb, end_fsb - *offset_fsb);
/* Grab the corresponding mapping in the data fork. */
nmaps = 1;
Patches currently in stable-queue which might be from leah.rumancik@gmail.com are
queue-6.1/xfs-allow-read-io-and-ficlone-to-run-concurrently.patch
queue-6.1/xfs-hoist-freeing-of-rt-data-fork-extent-mappings.patch
queue-6.1/xfs-make-sure-maxlen-is-still-congruent-with-prod-when-rounding-down.patch
queue-6.1/xfs-only-remap-the-written-blocks-in-xfs_reflink_end_cow_extent.patch
queue-6.1/xfs-dquot-recovery-does-not-validate-the-recovered-dquot.patch
queue-6.1/xfs-clean-up-dqblk-extraction.patch
queue-6.1/xfs-abort-intent-items-when-recovery-intents-fail.patch
queue-6.1/xfs-up-ic_sema-if-flushing-data-device-fails.patch
queue-6.1/xfs-fix-internal-error-from-agfl-exhaustion.patch
queue-6.1/xfs-factor-out-xfs_defer_pending_abort.patch
queue-6.1/xfs-fix-units-conversion-error-in-xfs_bmap_del_extent_delay.patch
queue-6.1/xfs-bump-max-fsgeom-struct-version.patch
queue-6.1/xfs-handle-nimaps-0-from-xfs_bmapi_write-in-xfs_alloc_file_space.patch
queue-6.1/xfs-rt-stubs-should-return-negative-errnos-when-rt-disabled.patch
queue-6.1/xfs-clean-up-fs_xflag_realtime-handling-in-xfs_ioctl_setattr_xflags.patch
queue-6.1/xfs-respect-the-stable-writes-flag-on-the-rt-device.patch
queue-6.1/xfs-introduce-protection-for-drop-nlink.patch
queue-6.1/xfs-prevent-rt-growfs-when-quota-is-enabled.patch
queue-6.1/xfs-inode-recovery-does-not-validate-the-recovered-inode.patch
next prev parent reply other threads:[~2025-01-30 8:41 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 18:46 [PATCH 6.1 00/19] xfs 6.1.y fixes from 6.7 Leah Rumancik
2025-01-29 18:46 ` [PATCH 6.1 01/19] xfs: bump max fsgeom struct version Leah Rumancik
2025-01-30 8:40 ` Patch "xfs: bump max fsgeom struct version" has been added to the 6.1-stable tree gregkh
2025-02-01 23:54 ` [PATCH 6.1 01/19] xfs: bump max fsgeom struct version Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 02/19] xfs: hoist freeing of rt data fork extent mappings Leah Rumancik
2025-01-30 8:41 ` Patch "xfs: hoist freeing of rt data fork extent mappings" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 02/19] xfs: hoist freeing of rt data fork extent mappings Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 03/19] xfs: prevent rt growfs when quota is enabled Leah Rumancik
2025-01-30 8:41 ` Patch "xfs: prevent rt growfs when quota is enabled" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 03/19] xfs: prevent rt growfs when quota is enabled Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 04/19] xfs: rt stubs should return negative errnos when rt disabled Leah Rumancik
2025-01-30 8:41 ` Patch "xfs: rt stubs should return negative errnos when rt disabled" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 04/19] xfs: rt stubs should return negative errnos when rt disabled Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 05/19] xfs: fix units conversion error in xfs_bmap_del_extent_delay Leah Rumancik
2025-01-30 8:41 ` Patch "xfs: fix units conversion error in xfs_bmap_del_extent_delay" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 05/19] xfs: fix units conversion error in xfs_bmap_del_extent_delay Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 06/19] xfs: make sure maxlen is still congruent with prod when rounding down Leah Rumancik
2025-01-30 8:41 ` Patch "xfs: make sure maxlen is still congruent with prod when rounding down" has been added to the 6.1-stable tree gregkh
2025-02-01 23:54 ` [PATCH 6.1 06/19] xfs: make sure maxlen is still congruent with prod when rounding down Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 07/19] xfs: introduce protection for drop nlink Leah Rumancik
2025-01-30 8:41 ` Patch "xfs: introduce protection for drop nlink" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 07/19] xfs: introduce protection for drop nlink Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 08/19] xfs: handle nimaps=0 from xfs_bmapi_write in xfs_alloc_file_space Leah Rumancik
2025-01-30 8:41 ` Patch "xfs: handle nimaps=0 from xfs_bmapi_write in xfs_alloc_file_space" has been added to the 6.1-stable tree gregkh
2025-02-01 23:54 ` [PATCH 6.1 08/19] xfs: handle nimaps=0 from xfs_bmapi_write in xfs_alloc_file_space Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 09/19] xfs: allow read IO and FICLONE to run concurrently Leah Rumancik
2025-01-30 8:40 ` Patch "xfs: allow read IO and FICLONE to run concurrently" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 09/19] xfs: allow read IO and FICLONE to run concurrently Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 10/19] xfs: factor out xfs_defer_pending_abort Leah Rumancik
2025-01-30 8:40 ` Patch "xfs: factor out xfs_defer_pending_abort" has been added to the 6.1-stable tree gregkh
2025-02-01 23:54 ` [PATCH 6.1 10/19] xfs: factor out xfs_defer_pending_abort Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 11/19] xfs: abort intent items when recovery intents fail Leah Rumancik
2025-01-30 8:40 ` Patch "xfs: abort intent items when recovery intents fail" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 11/19] xfs: abort intent items when recovery intents fail Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 12/19] xfs: only remap the written blocks in xfs_reflink_end_cow_extent Leah Rumancik
2025-01-30 8:41 ` gregkh [this message]
2025-02-01 23:53 ` Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 13/19] xfs: up(ic_sema) if flushing data device fails Leah Rumancik
2025-01-30 8:41 ` Patch "xfs: up(ic_sema) if flushing data device fails" has been added to the 6.1-stable tree gregkh
2025-02-01 23:54 ` [PATCH 6.1 13/19] xfs: up(ic_sema) if flushing data device fails Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 14/19] xfs: fix internal error from AGFL exhaustion Leah Rumancik
2025-01-30 8:40 ` Patch "xfs: fix internal error from AGFL exhaustion" has been added to the 6.1-stable tree gregkh
2025-02-01 23:54 ` [PATCH 6.1 14/19] xfs: fix internal error from AGFL exhaustion Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 15/19] xfs: inode recovery does not validate the recovered inode Leah Rumancik
2025-01-30 8:41 ` Patch "xfs: inode recovery does not validate the recovered inode" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 15/19] xfs: inode recovery does not validate the recovered inode Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 16/19] xfs: clean up dqblk extraction Leah Rumancik
2025-01-30 8:40 ` Patch "xfs: clean up dqblk extraction" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 16/19] xfs: clean up dqblk extraction Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 17/19] xfs: dquot recovery does not validate the recovered dquot Leah Rumancik
2025-01-30 8:40 ` Patch "xfs: dquot recovery does not validate the recovered dquot" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 17/19] xfs: dquot recovery does not validate the recovered dquot Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 18/19] xfs: clean up FS_XFLAG_REALTIME handling in xfs_ioctl_setattr_xflags Leah Rumancik
2025-01-30 8:40 ` Patch "xfs: clean up FS_XFLAG_REALTIME handling in xfs_ioctl_setattr_xflags" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 18/19] xfs: clean up FS_XFLAG_REALTIME handling in xfs_ioctl_setattr_xflags Sasha Levin
2025-01-29 18:47 ` [PATCH 6.1 19/19] xfs: respect the stable writes flag on the RT device Leah Rumancik
2025-01-30 8:41 ` Patch "xfs: respect the stable writes flag on the RT device" has been added to the 6.1-stable tree gregkh
2025-02-01 23:53 ` [PATCH 6.1 19/19] xfs: respect the stable writes flag on the RT device Sasha Levin
2025-01-30 8:41 ` [PATCH 6.1 00/19] xfs 6.1.y fixes from 6.7 Greg KH
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=2025013000-appealing-debtless-0e69@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=catherine.hoang@oracle.com \
--cc=chandan.babu@oracle.com \
--cc=chandanbabu@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=leah.rumancik@gmail.com \
--cc=stable-commits@vger.kernel.org \
--cc=xfs-stable@lists.linux.dev \
/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.