From: Dan Shelton <dan.f.shelton@gmail.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: kernel update to 6.8.2 broke idmapd group mapping
Date: Sat, 30 Mar 2024 12:56:39 +0100 [thread overview]
Message-ID: <CAAvCNcCDsAcZFoCuCgM_HrooSTjr5T9aQ2s_LC_81XUzVetwqw@mail.gmail.com> (raw)
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
next reply other threads:[~2024-03-30 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 11:56 Dan Shelton [this message]
2024-04-26 1:57 ` kernel update to 6.8.2 broke idmapd group mapping Dan Shelton
2024-04-26 4:22 ` NeilBrown
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=CAAvCNcCDsAcZFoCuCgM_HrooSTjr5T9aQ2s_LC_81XUzVetwqw@mail.gmail.com \
--to=dan.f.shelton@gmail.com \
--cc=linux-nfs@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).