From: Jeff Layton <jlayton@kernel.org>
To: Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>, Chuck Lever <cel@kernel.org>,
NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Shuah Khan <shuah@kernel.org>
Cc: Scott Mayhew <smayhew@redhat.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>
Subject: [PATCH 0/2] lockd: allow setting ports without setting gracetime
Date: Wed, 23 Sep 2026 06:58:55 -0400 [thread overview]
Message-ID: <20260923-nfsd-testing-v1-0-a793f54a4dd1@kernel.org> (raw)
This fixes a rather silly bug that Scott pointed out to me in a meeting
recently. You currently can't set the ports in lockd via the netlink
interface unless you also set the gracetime. This patch makes them all
properly optional.
We probably want this to go to stable.
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Jeff Layton (2):
lockd: allow SERVER_SET without a gracetime attribute
selftests/nfsd: add lockd netlink configuration tests
fs/lockd/svc.c | 50 ++---
tools/testing/selftests/nfsd/.gitignore | 1 +
tools/testing/selftests/nfsd/Makefile | 1 +
tools/testing/selftests/nfsd/nfsd_lockd_netlink.c | 249 ++++++++++++++++++++++
tools/testing/selftests/nfsd/nfsd_netlink.h | 90 ++++++--
5 files changed, 348 insertions(+), 43 deletions(-)
---
base-commit: cab95e6be3ba82bcf4c8be27c2eb20e55238aa41
change-id: 20260922-nfsd-testing-00c12335047d
Best regards,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2026-09-23 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 10:58 Jeff Layton [this message]
2026-09-23 10:58 ` [PATCH 1/2] lockd: allow SERVER_SET without a gracetime attribute Jeff Layton
2026-09-23 10:58 ` [PATCH 2/2] selftests/nfsd: add lockd netlink configuration tests Jeff Layton
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=20260923-nfsd-testing-v1-0-a793f54a4dd1@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=shuah@kernel.org \
--cc=smayhew@redhat.com \
--cc=tom@talpey.com \
--cc=trondmy@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®