From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org, Daejun Park <daejun7.park@samsung.com>
Cc: Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>,
Dave Chinner <dgc@kernel.org>,
Pankaj Raghav <p.raghav@samsung.com>,
Chuck Lever <cel@kernel.org>, Jeff Layton <jlayton@kernel.org>,
Dai Ngo <Dai.Ngo@oracle.com>,
Sergey Bashirov <sergeybashirov@gmail.com>,
Andrey Albershteyn <aalbersh@kernel.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v5 0/9] xfs: pNFS block layout fixes
Date: Tue, 03 Nov 2026 11:02:38 +0100 [thread overview]
Message-ID: <179370015876.413123.10956026336394412777.b4-ty@kernel.org> (raw)
In-Reply-To: <20261029-xfs-pnfs-batch-v5-0-ef8d2eafb7fa@samsung.com>
On Thu, 29 Oct 2026 11:22:57 +0900, Daejun Park wrote:
> The XFS side of the pNFS block and SCSI layout fixes. A pNFS client
> alone can trigger the bugs fixed by patches 1 and 3 to 6. Patch 7
> closes a race with a local process writing to a shared mapping.
> Patches 8 and 9 make a LAYOUTCOMMIT stable the way fdatasync does.
>
> Patch 3 needs patch 2. Patch 4 should not go without patches 2 and 3,
> and patch 6 not without patch 5. Patches 1 to 6 are marked for stable.
> XFS_BMAPI_CONVERT_ONLY takes bit 12 of the bmapi flags, which the
> fs-verity series [1] also uses.
>
> [...]
Applied to for-next, thanks!
[1/9] xfs: mark the inode preallocated for pNFS write layouts past EOF
commit: 77d5d75d727ab3d4c540632ead457d47d3456cd3
[2/9] xfs: add a flag to convert unwritten extents without allocating blocks
commit: e0fbfbec7d5ba059fcb1529054b5447cbe9c6e0e
[3/9] xfs: refuse a pNFS LAYOUTCOMMIT of a range without blocks
commit: faf5f20d6c005af531de079a5a0ea658b305954a
[4/9] xfs: clamp a pNFS LAYOUTCOMMIT extent before computing its end
commit: 351fccff2881e40f4f449bf100aceb47a54688e9
[5/9] xfs: cap the block count of xfs_iomap_write_direct() at one extent
commit: cefa7c7b065d129fe95a64b24ee68ca8c47629c6
[6/9] xfs: clamp the pNFS layout range to the maximum file size
commit: e4211f8034ce04a6bb1e12fc6a054e08b933e5cd
[7/9] xfs: take the invalidate lock while mapping a pNFS layout
commit: d58a23e183d578aca38d7186c353702facbf722b
[8/9] xfs: add datasync and log_flushed arguments to xfs_log_force_inode()
commit: c92cc6514b9c11dd29b90b0a814e8ea87b4a4687
[9/9] xfs: make pNFS LAYOUTCOMMIT stable the way fdatasync does
commit: c3b00a553cbb68b0bebed0ca16d2aa0300d07e56
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2026-11-03 10:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 2:22 Daejun Park via B4 Relay
2026-10-29 2:22 ` [PATCH v5 1/9] xfs: mark the inode preallocated for pNFS write layouts past EOF Daejun Park via B4 Relay
2026-10-29 2:22 ` [PATCH v5 2/9] xfs: add a flag to convert unwritten extents without allocating blocks Daejun Park via B4 Relay
2026-10-29 2:23 ` [PATCH v5 3/9] xfs: refuse a pNFS LAYOUTCOMMIT of a range without blocks Daejun Park via B4 Relay
2026-10-29 2:23 ` [PATCH v5 4/9] xfs: clamp a pNFS LAYOUTCOMMIT extent before computing its end Daejun Park via B4 Relay
2026-10-29 2:23 ` [PATCH v5 5/9] xfs: cap the block count of xfs_iomap_write_direct() at one extent Daejun Park via B4 Relay
2026-11-03 5:49 ` Christoph Hellwig
2026-11-03 8:44 ` Carlos Maiolino
2026-11-03 12:46 ` Pankaj Raghav (Samsung)
2026-10-29 2:23 ` [PATCH v5 6/9] xfs: clamp the pNFS layout range to the maximum file size Daejun Park via B4 Relay
2026-10-29 2:23 ` [PATCH v5 7/9] xfs: take the invalidate lock while mapping a pNFS layout Daejun Park via B4 Relay
2026-10-29 2:23 ` [PATCH v5 8/9] xfs: add datasync and log_flushed arguments to xfs_log_force_inode() Daejun Park via B4 Relay
2026-10-29 2:23 ` [PATCH v5 9/9] xfs: make pNFS LAYOUTCOMMIT stable the way fdatasync does Daejun Park via B4 Relay
2026-11-03 10:02 ` Carlos Maiolino [this message]
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=179370015876.413123.10956026336394412777.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=aalbersh@kernel.org \
--cc=cel@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=dgc@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=p.raghav@samsung.com \
--cc=sergeybashirov@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®