From: Jeff Layton <jlayton@kernel.org>
To: Scott Mayhew <smayhew@redhat.com>
Cc: Steve Dickson <steved@redhat.com>,
Yongcheng Yang <yoyang@redhat.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 0/3] nfsdctl: add support for new lockd configuration interface
Date: Tue, 14 Jan 2025 16:18:02 -0500 [thread overview]
Message-ID: <659d6f0153daf83ebfcad8d7bdb80adb6aa319b5.camel@kernel.org> (raw)
In-Reply-To: <Z4bScYOgDwbpyXjt@aion>
On Tue, 2025-01-14 at 16:09 -0500, Scott Mayhew wrote:
> On Fri, 10 Jan 2025, Jeff Layton wrote:
>
> > v2 is just a small update to fix the problems that Scott spotted.
> >
> > This patch series adds support for the new lockd configuration interface
> > that should fix this RH bug:
> >
> > https://issues.redhat.com/browse/RHEL-71698
> >
> > There are some other improvements here too, notably a switch to xlog.
> > Only lightly tested, but seems to do the right thing.
> >
> > Port handling with lockd still needs more work. Currently that is
> > usually configured by rpc.statd. I think we need to convert it to
> > use netlink to configure the ports as well, when it's able.
> >
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
>
> I think the read_nfsd_conf call should be moved out of autostart_func
> and into main (right before the command-line options are parsed). Right
> now if you enable debugging in nfs.conf, you get the "configuring
> listeners" and "nfsdctl exiting" messages, but not the "nfsdctl started"
> message. It's not a big deal though and could be done if additional
> debug logging is added in the future.
>
That sounds good. We can do that in a separate patch.
> Reviewed-by: Scott Mayhew <smayhew@redhat.com>
Thanks!
> > ---
> > Changes in v2:
> > - properly regenerate manpages
> > - fix up bogus merge conflict
> > - add D_GENERAL xlog messages when nfsdctl starts and exits
> > - Link to v1: https://lore.kernel.org/r/20250109-lockd-nl-v1-0-108548ab0b6b@kernel.org
> >
> > ---
> > Jeff Layton (3):
> > nfsdctl: convert to xlog()
> > nfsdctl: fix the --version option
> > nfsdctl: add necessary bits to configure lockd
> >
> > configure.ac | 4 +
> > utils/nfsdctl/lockd_netlink.h | 29 ++++
> > utils/nfsdctl/nfsdctl.8 | 15 +-
> > utils/nfsdctl/nfsdctl.adoc | 8 +
> > utils/nfsdctl/nfsdctl.c | 331 ++++++++++++++++++++++++++++++++++--------
> > 5 files changed, 321 insertions(+), 66 deletions(-)
> > ---
> > base-commit: 65f4cc3a6ce1472ee4092c4bbf4b19beb0a8217b
> > change-id: 20250109-lockd-nl-6272fa9e8a5d
> >
> > Best regards,
> > --
> > Jeff Layton <jlayton@kernel.org>
> >
>
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-01-14 21:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 13:46 [PATCH v2 0/3] nfsdctl: add support for new lockd configuration interface Jeff Layton
2025-01-10 13:46 ` [PATCH v2 1/3] nfsdctl: convert to xlog() Jeff Layton
2025-01-10 13:46 ` [PATCH v2 2/3] nfsdctl: fix the --version option Jeff Layton
2025-01-10 13:46 ` [PATCH v2 3/3] nfsdctl: add necessary bits to configure lockd Jeff Layton
2025-01-10 15:05 ` Tom Talpey
2025-01-10 15:21 ` Jeff Layton
2025-01-10 15:40 ` Tom Talpey
2025-01-13 13:39 ` Benjamin Coddington
2025-01-14 15:53 ` Tom Talpey
2025-01-14 21:09 ` [PATCH v2 0/3] nfsdctl: add support for new lockd configuration interface Scott Mayhew
2025-01-14 21:18 ` Jeff Layton [this message]
2025-01-15 14:44 ` Scott Mayhew
2025-01-15 14:56 ` Jeff Layton
2025-01-15 15:12 ` Steve Dickson
2025-01-15 15:28 ` Jeff Layton
2025-01-15 16:40 ` Scott Mayhew
2025-01-15 17:00 ` [nfs-utils PATCH] nfsdctl: debug logging fixups Scott Mayhew
2025-01-15 17:02 ` Jeff Layton
2025-01-15 17:32 ` Steve Dickson
2025-01-15 17:35 ` Jeff Layton
2025-01-15 17:47 ` Steve Dickson
2025-01-15 18:33 ` Jeff Layton
2025-01-15 20:53 ` Steve Dickson
2025-01-16 11:50 ` Jeff Layton
2025-01-16 21:00 ` Steve Dickson
2025-01-16 21:12 ` Jeff Layton
2025-03-19 19:47 ` [PATCH v2 0/3] nfsdctl: add support for new lockd configuration interface Steve Dickson
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=659d6f0153daf83ebfcad8d7bdb80adb6aa319b5.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.com \
--cc=steved@redhat.com \
--cc=yoyang@redhat.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