mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: 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>
Cc: Scott Mayhew <smayhew@redhat.com>,
	linux-nfs@vger.kernel.org,  linux-kernel@vger.kernel.org,
	Jeff Layton <jlayton@kernel.org>
Subject: [PATCH 0/2] nfsd: remove legacy tracking methods
Date: Wed, 23 Sep 2026 12:14:20 -0400	[thread overview]
Message-ID: <20260923-nfsd-legacy-v1-0-8490c0c12ea5@kernel.org> (raw)

Around three years ago, we added CONFIG_NFSD_LEGACY_CLIENT_TRACKING with
the intent to eventually remove the code that it compiles in when
enabled. A little over a year ago, we switched the default for it to
"n".

All of the major distros now disable this option, so finish the job by
finally removing the config option altogether. With this, nfsdcld
becomes the sole way to do v4 recovery tracking.

This also finally gets rid of the dependency on MD5 hashing that the
legacy recdir method used, which will mean that FIPS auditors will stop
dinging us too.

I think we should shoot for putting this in v7.5. Anyone have
objections?

Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Jeff Layton (2):
      nfsd: remove the nfsdcltrack usermodehelper tracking backend
      nfsd: remove CONFIG_NFSD_LEGACY_CLIENT_TRACKING

 arch/s390/configs/debug_defconfig |   1 -
 arch/s390/configs/defconfig       |   1 -
 fs/nfsd/Kconfig                   |  17 -
 fs/nfsd/netns.h                   |   1 -
 fs/nfsd/nfs4ctl.h                 |   8 +-
 fs/nfsd/nfs4recover.c             | 998 +-------------------------------------
 fs/nfsd/nfsctl.c                  |  79 ---
 fs/nfsd/state.h                   |   4 -
 fs/nfsd/trace.h                   |  19 -
 9 files changed, 3 insertions(+), 1125 deletions(-)
---
base-commit: cab95e6be3ba82bcf4c8be27c2eb20e55238aa41
change-id: 20260923-nfsd-legacy-468be4ee7773

Best regards,
-- 
Jeff Layton <jlayton@kernel.org>


             reply	other threads:[~2026-09-23 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 16:14 Jeff Layton [this message]
2026-09-23 16:14 ` [PATCH 1/2] nfsd: remove the nfsdcltrack usermodehelper tracking backend Jeff Layton
2026-09-23 16:14 ` [PATCH 2/2] nfsd: remove CONFIG_NFSD_LEGACY_CLIENT_TRACKING Jeff Layton
2026-09-23 18:25 ` [PATCH 0/2] nfsd: remove legacy tracking methods 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=20260923-nfsd-legacy-v1-0-8490c0c12ea5@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=cel@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=smayhew@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

all inboxes | Powered by JetHome®