3.2.0-24-virtual rejects sec=krb5p NFS mount option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
# uname -a
Linux client 3.2.0-24-virtual #37-Ubuntu SMP Wed Apr 25 12:51:49 UTC 2012 i686 i686 i386 GNU/Linux
# mount -v -t nfs -o sec=krb5p server:/srv/nfs/k /mnt
mount.nfs: timeout set for Tue May 1 17:46:30 2012
mount.nfs: trying text-based options 'sec=krb5p,
mount.nfs: mount(2): Invalid argument
mount.nfs: an incorrect mount option was specified
If I boot the same VM using 3.2.0-24-
sec=sys NFS mounts work just fine with either kernel.
After each failed mount attempt, dmesg says:
gss_create: Pseudoflavor 390005 not found!
RPC: Couldn't create auth handle (flavor 390005)
Additional info:
# cat /proc/version_
Ubuntu 3.2.0-24.37-virtual 3.2.14
lspci -vnvn produces no output. This is running as a guest on a Debian squeeze Xen 4.0.1 host.
The auth_rpcgss module is loaded:
# lsmod
Module Size Used by
autofs4 27969 31
xt_tcpudp 12531 14
nf_conntrack_ipv4 19084 5
nf_defrag_ipv4 12649 1 nf_conntrack_ipv4
xt_state 12514 5
nf_conntrack 73847 2 nf_conntrack_
iptable_filter 12706 1
ip_tables 18106 1 iptable_filter
x_tables 21974 4 xt_tcpudp,
nfsd 229850 2
nfs 307289 0
lockd 78804 2 nfsd,nfs
fscache 50642 1 nfs
auth_rpcgss 39597 2 nfsd,nfs
nfs_acl 12771 2 nfsd,nfs
sunrpc 205647 6 nfsd,nfs,
ext2 67987 1
lp 17455 0
parport 40930 1 lp
Comparing the kernel config files in /boot shows only these differences:
-CONFIG_
+CONFIG_
-CONFIG_
+CONFIG_
-CONFIG_
+CONFIG_
-CONFIG_
+# CONFIG_INTEL_IDLE is not set
dmesg says:
gss_create: Pseudoflavor 390005 not found!
RPC: Couldn't create auth handle (flavor 390005)
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 992678
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.