Bug 534328

Summary:	autofs segfaults after kernel update to 2.6.27.29
Product:	[openSUSE] openSUSE 11.1	Reporter:	Forgotten User k1N4TgUH7O <forgotten_k1N4TgUH7O>
Component:	Network	Assignee:	Neil Brown <nfbrown>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Blocker
Priority:	P1 - Urgent	CC:	rbsmith
Version:	Final
Target Milestone:	Final
Hardware:	i586
OS:	openSUSE 11.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User k1N4TgUH7O 2009-08-26 08:08:15 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.13) Gecko/2009080200 SUSE/3.0.13-0.1.2 Firefox/3.0.13

NFS4 mounts do not work anymore after the kernel update to version 2.6.27.29. Downgrading to version 2.6.27.25 fixes the problem.

When starting or restarting (rcautofs restart) the daemon crashes with the following message in /var/log/messages:
Aug  3 17:37:01 crusher kernel: automount[3705]: segfault at b7b6dcc0 ip b7b6dcc0 sp b756b3ac error 14
and once I also got
Aug 25 11:19:48 crusher kernel: automount[3727]: segfault at b79a4cc0 ip b79a4cc0 sp b73dc3ac error 14 in libkrb5.so.3.3[b7a58000+9c000]

A solution is to mount the network manually (only nfs3 worked for me, don't know whether this is of importance here).

I've also tried several autofs versions, but none worked. It really seems to be a kernel issue.

Reproducible: Always

Comment 1 Randall Smith 2009-08-31 20:05:17 UTC

Autofs segfaults on x86_64 also. Likewise, mounting NFS4 file systems fails with invalid argument.

strace -f mount -t nfs4 10.0.0.1:/filesystem /mnt

produces the output containing:

mount("10.0.0.1:/filesystem", "/mnt", "nfs4", 0, "clientaddr=10.0.0.2,addr=10.0.0.1") = -1 EINVAL (Invalid argument)
write(2, "mount.nfs4: an incorrect option was specified\n", 52)=52

Comment 2 Forgotten User k1N4TgUH7O 2009-09-02 07:22:45 UTC

Yes, that's the same problem here. Also reproducible on both 64bit and 32bit.

Comment 3 Randall Smith 2009-09-02 11:48:36 UTC

Another duplicate.

*** This bug has been marked as a duplicate of bug 531633 ***