Bug 3895

Summary:	mount nfs broken in 1.18.4
Product:	Busybox	Reporter:	Chris <blue.dragan+bb>
Component:	Standard Compliance	Assignee:	unassigned
Status:	RESOLVED INVALID
Severity:	normal	CC:	busybox-cvs
Priority:	P5
Version:	1.18.x
Target Milestone:	---
Hardware:	PC
OS:	Linux
Host:		Target:
Build:

Description Chris 2011-06-17 17:47:36 UTC

The following command is broken in busybox 1.18.4:
mount -t nfs -o nolock server:/dir /mountpoint

Executing this command now returns "Invalid argument".

This command used to work fine in busybox 1.18.3 (the same kernel and other system components).

Comment 1 Denys Vlasenko 2011-06-18 09:01:41 UTC

(In reply to comment #0)
> The following command is broken in busybox 1.18.4:
> mount -t nfs -o nolock server:/dir /mountpoint
> 
> Executing this command now returns "Invalid argument".
> 
> This command used to work fine in busybox 1.18.3 (the same kernel and other
> system components).

This is rather surprising, considering that 1.18.4 had no changed in mount.

Can you run "strace -s99 -f -oLOG mount <args>" with working and with broken mount, and attach resulting LOG files to this bug?

Comment 2 Denys Vlasenko 2011-06-18 09:02:38 UTC

Also please attach .config files you used to build your busybox binaries (for both versions).

Comment 3 Chris 2011-08-30 20:17:44 UTC

This is my fault, sorry. I was compiling busybox with the Gentoo toolchain and somebody split off NFS to an nfs USE flag, which I didn't notice, so after upgrading I was building without NFS support.

Closing as not a bug.