From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Zorro Lang <zlang@kernel.org>,
linux-xfs@vger.kernel.org
Subject: fix swapon for recently unshared blocks
Date: Wed, 5 Feb 2025 17:27:59 +0100 [thread overview]
Message-ID: <20250205162813.2249154-1-hch@lst.de> (raw)
Hi all,
the first patch fixes the recently added generic/370, and the
second one does a bit of naming cleanup in the area.
Diffstat:
xfs_aops.c | 24 ++++++++++++++++++++----
1 file changed, 20 insertions(+), 4 deletions(-)
next reply other threads:[~2025-02-05 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 16:27 Christoph Hellwig [this message]
2025-02-05 16:28 ` [PATCH 1/2] xfs: flush inodegc before swapon Christoph Hellwig
2025-02-05 18:23 ` Darrick J. Wong
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
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=20250205162813.2249154-1-hch@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--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