Hi, On Tue, Dec 10, 2024 at 07:25:54AM -0500, Scott Mayhew wrote: > Get rid of the nfsd4_legacy_tracking_ops->init() call in > check_for_legacy_methods(). That will be handled in the caller > (nfsd4_client_tracking_init()). Otherwise, we'll wind up calling > nfsd4_legacy_tracking_ops->init() twice, and the second time we'll > trigger the BUG_ON() in nfsd4_init_recdir(). > > Fixes: 74fd48739d04 ("nfsd: new Kconfig option for legacy client tracking") > Reported-by: Jur van der Burg <jur@xxxxxxxxxxx> > Link: https://bugzilla.kernel.org/show_bug.cgi?id=219580 > Signed-off-by: Scott Mayhew <smayhew@xxxxxxxxxx> > --- > fs/nfsd/nfs4recover.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/fs/nfsd/nfs4recover.c b/fs/nfsd/nfs4recover.c > index 4a765555bf84..1c8fcb04b3cd 100644 > --- a/fs/nfsd/nfs4recover.c > +++ b/fs/nfsd/nfs4recover.c > @@ -2052,7 +2052,6 @@ static inline int check_for_legacy_methods(int status, struct net *net) > path_put(&path); > if (status) > return -ENOTDIR; > - status = nn->client_tracking_ops->init(net); > } > return status; With a kernel with CONFIG_NFSD_LEGACY_CLIENT_TRACKING=y and this change applied, successfully tested against the issue reported in https://bugs.debian.org/1087900 https://bugs.debian.org/1091439 Tested-by: Salvatore Bonaccorso <carnil@xxxxxxxxxx> Regards, Salvatore