summaryrefslogtreecommitdiff
path: root/fs/afs/flock.c
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2008-09-08 15:58:13 (GMT)
committerLinus Torvalds <torvalds@linux-foundation.org>2008-09-08 22:35:19 (GMT)
commitaf904deaf6da3f3285eb0a06a3dc6a1af0251030 (patch)
treead0f0eef5824d22e1fa6ca79f45bc3b59c19985a /fs/afs/flock.c
parent7686ad5606f08d9dfb33a2087a36c8366366015b (diff)
downloadlinux-af904deaf6da3f3285eb0a06a3dc6a1af0251030.tar.xz
NFS: Restore missing hunk in NFS mount option parser
Automounter maps can contain mount options valid for other NFS implementations but not for Linux. The Linux automounter uses the mount command's "-s" command line option ("s" for "sloppy") so that mount requests containing such options are not rejected. Commit f45663ce5fb30f76a3414ab3ac69f4dd320e760a attempted to address a known regression with text-based NFS mount option parsing. Unrecognized mount options would cause mount requests to fail, even if the "-s" option was used on the mount command line. Unfortunately, this commit was not complete as submitted. It adds a new mount option, "sloppy". But it is missing a hunk, so it now allows NFS mounts with unrecognized mount options, even if the "sloppy" option is not present. This could be a problem if a required critical mount option such as "sync" is misspelled, for example, and is considered a regression from 2.6.26. This patch restores the missing hunk. Now, the default behavior of text-based NFS mount options is as before: any unrecognized mount option will cause the mount to fail. Please include this in 2.6.27-rc. Thanks to Neil Brown for reporting this. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Acked-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/afs/flock.c')
0 files changed, 0 insertions, 0 deletions