linux.git/fs/cifs/README, branch master

cifs: create a new Documentation/ directory and move docfiles into it

2013-09-08T19:24:10+00:00

Currently, we have a number of documentation files that live under
fs/cifs/. Generally, these don't get picked up by distro packagers,
since they're in a non-standard location. Move them to a new spot
under Documentation/ instead.

Signed-off-by: Jeff Layton 
Signed-off-by: Steve French

treewide: fix typo of "suport" in various comments and Kconfig

2012-11-19T13:16:09+00:00

Signed-off-by: Masanari Iida 
Signed-off-by: Jiri Kosina

cifs: remove legacy MultiuserMount option

2012-05-17T01:13:31+00:00

We've now warned about this for two releases. Remove it for 3.5.

Signed-off-by: Jeff Layton

CIFS: Delete echo_retries module parm

2012-03-21T16:35:38+00:00

It's the essential step before respecting MaxMpxCount value during
negotiating because we will keep only one extra slot for sending
echo requests. If there is no response during two echo intervals -
reconnect the tcp session.

Reviewed-by: Jeff Layton 
Signed-off-by: Pavel Shilovsky 
Signed-off-by: Steve French

Typo in cifs readme in name of module parm directory

2011-10-13T04:42:26+00:00

Suresh had a typo in his recent patch adding information on
the new oplock_endabled parm. Should be documented as in
directory /sys/module/cifs/parameters not /proc/module/cifs/parameters

Signed-off-by: Steve French

cifs: update README about the kernel module parameters

2011-10-13T04:42:09+00:00

Reported-by: Alexander Swen 
Cc: Jeff Layton 
Signed-off-by: Suresh Jayaraman 
Signed-off-by: Steve French

CIFS: Add rwpidforward mount option

2011-05-27T03:57:16+00:00

Add rwpidforward mount option that switches on a mode when we forward
pid of a process who opened a file to any read and write operation.

This can prevent applications like WINE from failing on read or write
operation on a previously locked file region from the same netfd from
another process if we use mandatory brlock style.

It is actual for WINE because during a run of WINE program two processes
work on the same netfd - share the same file struct between several VFS
fds:
1) WINE-server does open and lock;
2) WINE-application does read and write.

Signed-off-by: Pavel Shilovsky 
Signed-off-by: Steve French

Don't compile in unused reparse point symlink code

2011-05-19T14:10:48+00:00

Recent Windows versions now create symlinks more frequently
and they do use this "reparse point" symlink mechanism.  We can of course
do symlinks nicely to Samba and other servers which support the
CIFS Unix Extensions and we can also do SFU symlinks and "client only"
"MF" symlinks optionally, but for recent Windows we currently can not
handle the common "reparse point" symlinks fully, removing the caller
for this. We will need to extend and reenable this "reparse point" worker
code in cifs and fix cifs_symlink to call this.  In the interim this code
has been moved to its own config option so it is not compiled in by default
until cifs_symlink fixed up (and tested) to use this.

CC: Jeff Layton 
Signed-off-by: Steve French

cifs: replace /proc/fs/cifs/Experimental with a module parm

2011-04-12T00:40:43+00:00

This flag currently only affects whether we allow "zero-copy" writes
with signing enabled. Typically we map pages in the pagecache directly
into the write request. If signing is enabled however and the contents
of the page change after the signature is calculated but before the
write is sent then the signature will be wrong. Servers typically
respond to this by closing down the socket.

Still, this can provide a performance benefit so the "Experimental" flag
was overloaded to allow this. That's really not a good place for this
option however since it's not clear what that flag does.

Move that flag instead to a new module parameter that better describes
its purpose. That's also better since it can be set at module insertion
time by configuring modprobe.d.

Reviewed-by: Suresh Jayaraman 
Signed-off-by: Jeff Layton 
Signed-off-by: Steve French

CIFS: Add strictcache mount option

2011-01-25T19:31:38+00:00

Use for switching on strict cache mode. In this mode the
client reads from the cache all the time it has Oplock Level II,
otherwise - read from the server. As for write - the client stores
a data in the cache in Exclusive Oplock case, otherwise - write
directly to the server.

Signed-off-by: Pavel Shilovsky 
Reviewed-by: Jeff Layton 
Signed-off-by: Steve French