From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>, Zorro Lang <zlang@kernel.org>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/2] xfs: flush inodegc before swapon
Date: Wed, 5 Feb 2025 10:23:33 -0800 [thread overview]
Message-ID: <20250205182333.GJ21808@frogsfrogsfrogs> (raw)
In-Reply-To: <20250205162813.2249154-2-hch@lst.de>
On Wed, Feb 05, 2025 at 05:28:00PM +0100, Christoph Hellwig wrote:
> Fix the brand new xfstest that tries to swapon on a recently unshared
> file and use the chance to document the other bit of magic in this
> function.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Cc: <stable@vger.kernel.org> # v5.19
Fixes: 5e672cd69f0a53 ("xfs: introduce xfs_inodegc_push()")
Perhaps? This isn't really a hard brokenness, but it could surprise a
user somewhere.
> ---
> fs/xfs/xfs_aops.c | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
> index 69b8c2d1937d..c792297aa0a3 100644
> --- a/fs/xfs/xfs_aops.c
> +++ b/fs/xfs/xfs_aops.c
> @@ -21,6 +21,7 @@
> #include "xfs_error.h"
> #include "xfs_zone_alloc.h"
> #include "xfs_rtgroup.h"
> +#include "xfs_icache.h"
>
> struct xfs_writepage_ctx {
> struct iomap_writepage_ctx ctx;
> @@ -685,7 +686,22 @@ xfs_iomap_swapfile_activate(
> struct file *swap_file,
> sector_t *span)
> {
> - sis->bdev = xfs_inode_buftarg(XFS_I(file_inode(swap_file)))->bt_bdev;
> + struct xfs_inode *ip = XFS_I(file_inode(swap_file));
> +
> + /*
> + * Ensure inode GC has finished to remove unmapped extents, as the
> + * reflink bit is only cleared once all previously shared extents
> + * are unmapped. Otherwise swapon could incorrectly fail on a
> + * very recently unshare file.
unshared
> + */
> + xfs_inodegc_flush(ip->i_mount);
> +
> + /*
> + * Direct the swap code to the correct block device when this file
> + * sits on the RT device.
> + */
> + sis->bdev = xfs_inode_buftarg(ip)->bt_bdev;
With all that amended,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> +
> return iomap_swapfile_activate(sis, swap_file, span,
> &xfs_read_iomap_ops);
> }
> --
> 2.45.2
>
>
next prev parent reply other threads:[~2025-02-05 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 16:27 fix swapon for recently unshared blocks Christoph Hellwig
2025-02-05 16:28 ` [PATCH 1/2] xfs: flush inodegc before swapon Christoph Hellwig
2025-02-05 18:23 ` Darrick J. Wong [this message]
2025-02-05 21:08 ` Dave Chinner
2025-02-05 21:16 ` Darrick J. Wong
2025-02-05 21:53 ` Dave Chinner
2025-02-05 22:05 ` Darrick J. Wong
2025-02-05 16:28 ` [PATCH 2/2] xfs: rename xfs_iomap_swapfile_activate to xfs_vm_swap_activate Christoph Hellwig
2025-02-05 18:24 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2025-02-06 6:14 fix swapon for recently unshared blocks v2 Christoph Hellwig
2025-02-06 6:15 ` [PATCH 1/2] xfs: flush inodegc before swapon Christoph Hellwig
2025-02-11 8:44 ` 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=20250205182333.GJ21808@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox