linux-toradex.git/fs/cifs, branch v3.9.7

cifs: fix off-by-one bug in build_unc_path_to_root

2013-06-13T17:49:31+00:00

commit 1fc29bacedeabb278080e31bb9c1ecb49f143c3b upstream.

commit 839db3d10a (cifs: fix up handling of prefixpath= option) changed
the code such that the vol->prepath no longer contained a leading
delimiter and then fixed up the places that accessed that field to
account for that change.

One spot in build_unc_path_to_root was missed however. When doing the
pointer addition on pos, that patch failed to account for the fact that
we had already incremented "pos" by one when adding the length of the
prepath. This caused a buffer overrun by one byte.

This patch fixes the problem by correcting the handling of "pos".

Reported-by: Marcus Moeller 
Reported-by: Ken Fallon 
Signed-off-by: Jeff Layton 
Signed-off-by: Steve French 
Signed-off-by: Greg Kroah-Hartman

cifs: fix potential buffer overrun when composing a new options string

2013-06-07T19:53:04+00:00

commit 166faf21bd14bc5c5295a44874bf7f3930c30b20 upstream.

Consider the case where we have a very short ip= string in the original
mount options, and when we chase a referral we end up with a very long
IPv6 address. Be sure to allow for that possibility when estimating the
size of the string to allocate.

Signed-off-by: Jeff Layton 
Signed-off-by: Steve French 
Signed-off-by: Greg Kroah-Hartman

cifs: only set ops for inodes in I_NEW state

2013-06-07T19:52:26+00:00

commit c2b93e0699723700f886ce17bb65ffd771195a6d upstream.

It's generally not safe to reset the inode ops once they've been set. In
the case where the inode was originally thought to be a directory and
then later found to be a DFS referral, this can lead to an oops when we
try to trigger an inode op on it after changing the ops to the blank
referral operations.

Reported-and-Tested-by: Sachin Prabhu 
Signed-off-by: Jeff Layton 
Signed-off-by: Steve French 
Signed-off-by: Greg Kroah-Hartman

cifs: Allow passwords which begin with a delimitor

2013-04-10T20:54:14+00:00

Fixes a regression in cifs_parse_mount_options where a password
which begins with a delimitor is parsed incorrectly as being a blank
password.

Signed-off-by: Sachin Prabhu 
Acked-by: Jeff Layton 
Cc: 
Signed-off-by: Steve French

Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6

2013-03-22T00:59:22+00:00

Pull CIFS fixes from Steve French:
 "Three small CIFS Fixes (the most important of the three fixes a recent
  problem authenticating to Windows 8 using cifs rather than SMB2)"

* 'for-next' of git://git.samba.org/sfrench/cifs-2.6:
  cifs: ignore everything in SPNEGO blob after mechTypes
  cifs: delay super block destruction until all cifsFileInfo objects are gone
  cifs: map NT_STATUS_SHARING_VIOLATION to EBUSY instead of ETXTBSY

cifs: ignore everything in SPNEGO blob after mechTypes

2013-03-21T17:40:19+00:00

We've had several reports of people attempting to mount Windows 8 shares
and getting failures with a return code of -EINVAL. The default sec=
mode changed recently to sec=ntlmssp. With that, we expect and parse a
SPNEGO blob from the server in the NEGOTIATE reply.

The current decode_negTokenInit function first parses all of the
mechTypes and then tries to parse the rest of the negTokenInit reply.
The parser however currently expects a mechListMIC or nothing to follow the
mechTypes, but Windows 8 puts a mechToken field there instead to carry
some info for the new NegoEx stuff.

In practice, we don't do anything with the fields after the mechTypes
anyway so I don't see any real benefit in continuing to parse them.
This patch just has the kernel ignore the fields after the mechTypes.
We'll probably need to reinstate some of this if we ever want to support
NegoEx.

Reported-by: Jason Burgess 
Reported-by: Yan Li 
Signed-off-by: Jeff Layton 
Cc: 
Signed-off-by: Steve French

cifs: delay super block destruction until all cifsFileInfo objects are gone

2013-03-13T19:12:06+00:00

cifsFileInfo objects hold references to dentries and it is possible that
these will still be around in workqueues when VFS decides to kill super
block during unmount.

This results in panics like this one:
BUG: Dentry ffff88001f5e76c0{i=66b4a,n=1M-2} still in use (1) [unmount of cifs cifs]
------------[ cut here ]------------
kernel BUG at fs/dcache.c:943!
[..]
Process umount (pid: 1781, threadinfo ffff88003d6e8000, task ffff880035eeaec0)
[..]
Call Trace:
 [] shrink_dcache_for_umount+0x33/0x60
 [] generic_shutdown_super+0x2c/0xe0
 [] kill_anon_super+0x16/0x30
 [] cifs_kill_sb+0x1a/0x30 [cifs]
 [] deactivate_locked_super+0x57/0x80
 [] deactivate_super+0x4e/0x70
 [] mntput_no_expire+0xd7/0x130
 [] sys_umount+0x9c/0x3c0
 [] system_call_fastpath+0x16/0x1b

Fix this by making each cifsFileInfo object hold a reference to cifs
super block, which implicitly keeps VFS super block around as well.

Signed-off-by: Mateusz Guzik 
Reviewed-by: Jeff Layton 
Cc: 
Reported-and-Tested-by: Ben Greear 
Signed-off-by: Steve French

cifs: map NT_STATUS_SHARING_VIOLATION to EBUSY instead of ETXTBSY

2013-03-13T19:09:20+00:00

NT_SHARING_VIOLATION errors are mapped to ETXTBSY which is unexpected
for operations such as unlink where we can hit these errors.

The patch maps the error NT_SHARING_VIOLATION to EBUSY instead. The
patch also replaces all instances of ETXTBSY in
cifs_rename_pending_delete() with EBUSY.

Signed-off-by: Sachin Prabhu 
Reviewed-by: Jeff Layton 
Signed-off-by: Steve French

fs: Limit sys_mount to only request filesystem modules. (Part 3)

2013-03-11T14:09:48+00:00

Somehow I failed to add the MODULE_ALIAS_FS for cifs, hostfs, hpfs,
squashfs, and udf despite what I thought were my careful checks :(

Add them now.

Signed-off-by: "Eric W. Biederman"

CIFS: Fix missing of oplock_read value in smb30_values structure

2013-03-07T01:37:01+00:00

Cc: stable@vger.kernel.org
Signed-off-by: Pavel Shilovsky 
Signed-off-by: Steve French