2024-03-30 11:57:14

by Dan Shelton

[permalink] [raw]
Subject: kernel update to 6.8.2 broke idmapd group mapping

Hello!

I have updated my Debian 11 with the Linux 6.8.2 kernel, running
rpc.nfsd with various NFSV4 clients.
Userland stayed exactly the same, so neither idmapd or nfs-utils were changed.

But I now see lots of weird group names (not usernames, they are
normal) from idmapd, but not all group name mappings are affected:
Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfsdcb:
authbuf=*,10.2.66.30 authtype=group
Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
calling nsswitch->name_to_gid
Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
nsswitch->name_to_gid returned -22
Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
return value is -22
Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: Server : (group) name
"^PM-!M-?M-4q" -> id "65534"
Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfsdcb:
authbuf=*,10.2.66.30 authtype=group
Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
calling nsswitch->name_to_gid
Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
nsswitch->name_to_gid returned -22
Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
return value is -22
Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: Server : (group) name
"PM-^^M-^OM-4q" -> id "65534"
Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfsdcb:
authbuf=*,10.2.66.30 authtype=group
Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
calling nsswitch->name_to_gid
Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
nsswitch->name_to_gid returned -22
Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
return value is -22
Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: Server : (group) name
"M-^PM-^]/M-4q" -> id "65534"
Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfsdcb:
authbuf=*,10.2.66.30 authtype=group
Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
calling nsswitch->name_to_gid
Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
nsswitch->name_to_gid returned -22
Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
return value is -22
Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: Server : (group) name
"M- M- M-^_M-4q" -> id "65534"
,

Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd


2024-04-26 01:57:36

by Dan Shelton

[permalink] [raw]
Subject: Re: kernel update to 6.8.2 broke idmapd group mapping

On Sat, 30 Mar 2024 at 12:56, Dan Shelton <[email protected]> wrote:
>
> Hello!
>
> I have updated my Debian 11 with the Linux 6.8.2 kernel, running
> rpc.nfsd with various NFSV4 clients.
> Userland stayed exactly the same, so neither idmapd or nfs-utils were changed.
>
> But I now see lots of weird group names (not usernames, they are
> normal) from idmapd, but not all group name mappings are affected:
> Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfsdcb:
> authbuf=*,10.2.66.30 authtype=group
> Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> calling nsswitch->name_to_gid
> Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> nsswitch->name_to_gid returned -22
> Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
> return value is -22
> Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: Server : (group) name
> "^PM-!M-?M-4q" -> id "65534"
> Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfsdcb:
> authbuf=*,10.2.66.30 authtype=group
> Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> calling nsswitch->name_to_gid
> Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> nsswitch->name_to_gid returned -22
> Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
> return value is -22
> Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: Server : (group) name
> "PM-^^M-^OM-4q" -> id "65534"
> Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfsdcb:
> authbuf=*,10.2.66.30 authtype=group
> Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> calling nsswitch->name_to_gid
> Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> nsswitch->name_to_gid returned -22
> Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
> return value is -22
> Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: Server : (group) name
> "M-^PM-^]/M-4q" -> id "65534"
> Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfsdcb:
> authbuf=*,10.2.66.30 authtype=group
> Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> calling nsswitch->name_to_gid
> Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> nsswitch->name_to_gid returned -22
> Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
> return value is -22
> Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: Server : (group) name
> "M- M- M-^_M-4q" -> id "65534"

Help?

Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd

2024-04-26 04:24:43

by NeilBrown

[permalink] [raw]
Subject: Re: kernel update to 6.8.2 broke idmapd group mapping

On Fri, 26 Apr 2024, Dan Shelton wrote:
> On Sat, 30 Mar 2024 at 12:56, Dan Shelton <[email protected]> wrote:
> >
> > Hello!
> >
> > I have updated my Debian 11 with the Linux 6.8.2 kernel, running
> > rpc.nfsd with various NFSV4 clients.

Update to 6.8.2 from ... what?
There are no nfsd changes between 6.8 and 6.8.2.

I assume you only change the server - none of the NFS clients were
changed?

Can you use "tcpdump -s 0 ...." to capture network traffic while this is
happening? That might provide some hints.

NeilBrown


> > Userland stayed exactly the same, so neither idmapd or nfs-utils were changed.
> >
> > But I now see lots of weird group names (not usernames, they are
> > normal) from idmapd, but not all group name mappings are affected:
> > Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfsdcb:
> > authbuf=*,10.2.66.30 authtype=group
> > Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> > calling nsswitch->name_to_gid
> > Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> > nsswitch->name_to_gid returned -22
> > Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
> > return value is -22
> > Mar 28 19:15:18 ingramnode86 rpc.idmapd[400]: Server : (group) name
> > "^PM-!M-?M-4q" -> id "65534"
> > Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfsdcb:
> > authbuf=*,10.2.66.30 authtype=group
> > Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> > calling nsswitch->name_to_gid
> > Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> > nsswitch->name_to_gid returned -22
> > Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
> > return value is -22
> > Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: Server : (group) name
> > "PM-^^M-^OM-4q" -> id "65534"
> > Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfsdcb:
> > authbuf=*,10.2.66.30 authtype=group
> > Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> > calling nsswitch->name_to_gid
> > Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> > nsswitch->name_to_gid returned -22
> > Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
> > return value is -22
> > Mar 28 19:15:19 ingramnode86 rpc.idmapd[400]: Server : (group) name
> > "M-^PM-^]/M-4q" -> id "65534"
> > Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfsdcb:
> > authbuf=*,10.2.66.30 authtype=group
> > Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> > calling nsswitch->name_to_gid
> > Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid:
> > nsswitch->name_to_gid returned -22
> > Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: nfs4_name_to_gid: final
> > return value is -22
> > Mar 28 19:15:20 ingramnode86 rpc.idmapd[400]: Server : (group) name
> > "M- M- M-^_M-4q" -> id "65534"
>
> Help?
>
> Dan
> --
> Dan Shelton - Cluster Specialist Win/Lin/Bsd
>
>