This same problem applies to kerberized NFSv3 as well as NFSv4. In both cases, the kernel will keep retrying if rpc.gssd only finds expired credentials. I've been investigating this problem because after a Lucid to Precise upgrade, users with kerberized NFS homedirs are unable to unlock their screens.
So it looks like this is intended behavior, but it leaves users with kerberized NFS home directories in a really bad situation. There have been some proposed patches both here and in the linked Debian bug against nfs-utils, but so far it doesn't look like any have been accepted upstream.
This same problem applies to kerberized NFSv3 as well as NFSv4. In both cases, the kernel will keep retrying if rpc.gssd only finds expired credentials. I've been investigating this problem because after a Lucid to Precise upgrade, users with kerberized NFS homedirs are unable to unlock their screens.
Back in Jan 2010, rpc.gssd got support for returning EKEYEXPIRED: git.linux- nfs.org/ ?p=steved/ nfs-utils. git;a=commit; h=289ad31e
http://
And around the same time, the kernel was changed to retry on EKEYEXPIRED: git.kernel. org/?p= linux/kernel/ git/torvalds/ linux.git; a=commit; h=2c643488 (NFSv4) git.kernel. org/?p= linux/kernel/ git/torvalds/ linux.git; a=commit; h=b68d69b8 (NFSv3)
http://
http://
So it looks like this is intended behavior, but it leaves users with kerberized NFS home directories in a really bad situation. There have been some proposed patches both here and in the linked Debian bug against nfs-utils, but so far it doesn't look like any have been accepted upstream.