From: Christoph Hellwig <hch@lst.de>
To: Daejun Park <daejun7.park@samsung.com>
Cc: Christoph Hellwig <hch@lst.de>, Carlos Maiolino <cem@kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Dave Chinner <dgc@kernel.org>, Chuck Lever <cel@kernel.org>,
Jeff Layton <jlayton@kernel.org>, Dai Ngo <Dai.Ngo@oracle.com>,
Sergey Bashirov <sergeybashirov@gmail.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: (2) [PATCH] xfs: refuse a pNFS LAYOUTCOMMIT of a range without blocks
Date: Wed, 14 Oct 2026 15:01:47 +0200 [thread overview]
Message-ID: <20261014130147.GB15407@lst.de> (raw)
In-Reply-To: <20261014014017epcms2p7ab0ff4f1356d695c55514bd7ccaebadf@epcms2p7>
On Wed, Oct 14, 2026 at 10:40:17AM +0900, Daejun Park wrote:
> The IOLOCK held across both keeps truncate, fallocate and blockgc out
> today, but the flag doesn't depend on that, so v2 does it that way:
> xfs_bmapi_write() takes a new XFS_BMAPI_CONVERT_ONLY flag that fails for
> a hole or a delalloc extent instead of allocating, and
> xfs_fs_commit_blocks() passes it through xfs_iomap_write_unwritten().
>
> One difference from v1: a LAYOUTCOMMIT with a laid-out range followed by
> a hole now converts the laid-out range before it fails.
> xfs_fs_commit_blocks() already left earlier extents converted when a
> later one failed, and the Linux client resends all of its extents after
> a failed LAYOUTCOMMIT, so I don't think that matters.
I don't think that's an issue.
prev parent reply other threads:[~2026-10-14 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 6:00 [PATCH] xfs: refuse a pNFS LAYOUTCOMMIT of a range without blocks Daejun Park via B4 Relay
2026-10-13 12:04 ` Christoph Hellwig
2026-10-14 1:40 ` Daejun Park
2026-10-14 13:01 ` Christoph Hellwig [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=20261014130147.GB15407@lst.de \
--to=hch@lst.de \
--cc=Dai.Ngo@oracle.com \
--cc=cel@kernel.org \
--cc=cem@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=dgc@kernel.org \
--cc=djwong@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--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