Linux NFS development
 help / color / mirror / Atom feed
From: Daejun Park via B4 Relay <devnull+daejun7.park.samsung.com@kernel.org>
To: Calum Mackay <calum.mackay@oracle.com>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <cel@kernel.org>,
	 Jeff Layton <jlayton@kernel.org>, Christoph Hellwig <hch@lst.de>,
	 Dai Ngo <dai.ngo@oracle.com>,
	Daejun Park <daejun7.park@samsung.com>
Subject: [PATCH pynfs 0/3] Block layout tests for LAYOUTCOMMITs of ranges without blocks
Date: Wed, 14 Oct 2026 13:10:25 +0900	[thread overview]
Message-ID: <20261014-pynfs-block-commit-v1-0-1723979f495f@samsung.com> (raw)

Patch 1 is "Add a test for contiguous writable extents in a block
layout", posted on October 6 [1] and unchanged. Patch 2 adds tests for
LAYOUTCOMMITs of ranges that no layout covered, which shut XFS down or
committed a block that nobody wrote before the XFS series in [2].
Patch 3 describes how the block layout tests are run against Linux
nfsd, as Christoph asked [3].

Tested with Linux nfsd on nfsd-testing d918c664efd5, XFS on an
NVMe/TCP namespace exported by nvmet, in QEMU guests with KASAN and
lockdep:

 - Without [2], BLOCK7 fails at the GETATTR after the LAYOUTCOMMIT, as
   XFS has shut down, and the tests after it fail for the same reason.
   With BLOCK7 and BLOCK8 left out, BLOCK9 fails because the server
   commits the hole. BLOCK10 passes; the server only logs a
   "non-standard errno" warning for it.
 - With [2], BLOCK6 to BLOCK10 pass in 5 runs, and also on an
   XFS_DEBUG kernel.
 - BLOCK3 fails with and without [2], on a bug in the test.

[1] https://lore.kernel.org/r/20261006002622epcms2p38e492aef17fdf79e48b05c9aada2918d@epcms2p3
[2] https://lore.kernel.org/r/20261014-xfs-pnfs-commit-hole-v2-0-d3a02a79ab6c@samsung.com
[3] https://lore.kernel.org/r/20261013120359.GB2944@lst.de

---
Daejun Park (3):
      Add a test for contiguous writable extents in a block layout
      Add tests for LAYOUTCOMMITs of ranges without blocks in a block layout
      Add README-blocklayout

 nfs4.1/README-blocklayout        |  41 +++++++
 nfs4.1/server41tests/st_block.py | 230 ++++++++++++++++++++++++++++++++++++++-
 2 files changed, 268 insertions(+), 3 deletions(-)
---
base-commit: cd4701827a8261fedbfb4c6e39029fb9671321a6
change-id: 20261014-pynfs-block-commit-c70fe337b684

Best regards,
-- 
Daejun Park <daejun7.park@samsung.com>



             reply	other threads:[~2026-10-14  4:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  4:10 Daejun Park via B4 Relay [this message]
2026-10-14  4:10 ` [PATCH pynfs 1/3] Add a test for contiguous writable extents in a block layout Daejun Park via B4 Relay
2026-10-14  4:10 ` [PATCH pynfs 2/3] Add tests for LAYOUTCOMMITs of ranges without blocks " Daejun Park via B4 Relay
2026-10-14  4:10 ` [PATCH pynfs 3/3] Add README-blocklayout Daejun Park via B4 Relay

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=20261014-pynfs-block-commit-v1-0-1723979f495f@samsung.com \
    --to=devnull+daejun7.park.samsung.com@kernel.org \
    --cc=calum.mackay@oracle.com \
    --cc=cel@kernel.org \
    --cc=daejun7.park@samsung.com \
    --cc=dai.ngo@oracle.com \
    --cc=hch@lst.de \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@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