From: Sergey Bashirov <sergeybashirov@gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Konstantin Evtushenko <koevtushenko@yandex.com>,
Sergey Bashirov <sergeybashirov@gmail.com>
Subject: [PATCH v2 0/3] NFSD: Fix last write offset handling in layoutcommit
Date: Tue, 15 Jul 2025 18:32:17 +0300 [thread overview]
Message-ID: <20250715153319.37428-1-sergeybashirov@gmail.com> (raw)
These patches correct the behavior of the pNFS server when the client
sends a layoutcommit without a new file size and with zero number of
block/scsi extents.
Tested manually for the pNFS block layout setup.
Signed-off-by: Sergey Bashirov <sergeybashirov@gmail.com>
---
Changes in v2:
- The first cleanup patch is unchanged
- Reworked main patch to guard entire new_size check, improved description
- Added cleanup patch to decode lc_newoffset as bool
Sergey Bashirov (3):
NFSD: Minor cleanup in layoutcommit processing
NFSD: Fix last write offset handling in layoutcommit
NFSD: Minor cleanup in layoutcommit decoding
fs/nfsd/blocklayout.c | 5 ++---
fs/nfsd/nfs4proc.c | 34 ++++++++++++++--------------------
fs/nfsd/nfs4xdr.c | 2 +-
3 files changed, 17 insertions(+), 24 deletions(-)
--
2.43.0
next reply other threads:[~2025-07-15 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 15:32 Sergey Bashirov [this message]
2025-07-15 15:32 ` [PATCH v2 1/3] NFSD: Minor cleanup in layoutcommit processing Sergey Bashirov
2025-07-15 15:32 ` [PATCH v2 2/3] NFSD: Fix last write offset handling in layoutcommit Sergey Bashirov
2025-07-16 11:16 ` Christoph Hellwig
2025-07-15 15:32 ` [PATCH v2 3/3] NFSD: Minor cleanup in layoutcommit decoding Sergey Bashirov
2025-07-16 11:16 ` Christoph Hellwig
2025-07-15 16:11 ` [PATCH v2 0/3] NFSD: Fix last write offset handling in layoutcommit Chuck Lever
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=20250715153319.37428-1-sergeybashirov@gmail.com \
--to=sergeybashirov@gmail.com \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=hch@infradead.org \
--cc=jlayton@kernel.org \
--cc=koevtushenko@yandex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
/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;
as well as URLs for NNTP newsgroup(s).