10 Sep, 2013
5 commits
-
that force a client to purge cache pages when a server requests it.
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
to make adding new types of lease buffers easier.
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
and separate smb20_operations struct.
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French
09 Sep, 2013
2 commits
-
that prepare the code to handle different types of SMB2 leases.
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
that allows to access files through symlink created on a server.
Acked-by: Jeff Layton
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French
11 Jul, 2013
3 commits
-
On reconnects, we need to reopen file and then obtain all byte-range
locks held by the client. SMB2 protocol provides feature to make
this process atomic by reconnecting to the same file handle
with all it's byte-range locks. This patch adds this capability
for SMB2 shares.Signed-off-by: Pavel Shilovsky
Signed-off-by: Steven French -
to prepare it for further durable handle reconnect processing.
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steven French -
and eliminated unused file_attribute parms of SMB2_open.
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steven French
28 Jun, 2013
1 commit
-
Commit 9ddec56131 (cifs: move handling of signed connections into
separate function) broke signing on SMB2/3 connections. While the code
to enable signing on the connections was very similar between the two,
the bits that get set in the sec_mode are different.Declare a couple of new smb_version_values fields and set them
appropriately for SMB1 and SMB2/3. Then change cifs_enable_signing to
use those instead.Reported-by: Shirish Pargaonkar
Signed-off-by: Jeff Layton
Tested-by: Shirish Pargaonkar
Signed-off-by: Steve French
27 Jun, 2013
2 commits
-
Fix build warning in Shirish's recent SMB3 signing patch
which occurs when SMB2 support is disabled in Kconfig.fs/built-in.o: In function `cifs_setup_session':
>> (.text+0xa1767): undefined reference to `generate_smb3signingkey'Pointed out by: automated 0-DAY kernel build testing backend
Intel Open Source Technology CenterCC: Shirish Pargaonkar
Signed-off-by: Steve French -
Cut and paste likely introduced accidentally inserted spurious #define
in d60622eb5a23904facf4a4efac60f5bfa810d7d4 causes no harm but looks weirdSigned-off-by: Steve French
24 Jun, 2013
2 commits
-
SMB3 protocol adds various optional per-share capabilities (and
SMB3.02 adds one more beyond that). Add ability to dump
(/proc/fs/cifs/DebugData) the share capabilities and share flags to
improve debugging.Signed-off-by: Steve French
Acked-by: Jeff Layton -
The new Windows update supports SMB3.02 dialect, a minor update to SMB3.
This patch adds support for mounting with vers=3.02Signed-off-by: Steve French
Reviewed-by: Jeff Layton
05 May, 2013
1 commit
-
It's not obvious from reading the macro names that these macros
are for debugging. Convert the names to a single more typical
kernel style cifs_dbg macro.cERROR(1, ...) -> cifs_dbg(VFS, ...)
cFYI(1, ...) -> cifs_dbg(FYI, ...)
cFYI(DBG2, ...) -> cifs_dbg(NOISY, ...)Move the terminating format newline from the macro to the call site.
Add CONFIG_CIFS_DEBUG function cifs_vfs_err to emit the
"CIFS VFS: " prefix for VFS messages.Size is reduced ~ 1% when CONFIG_CIFS_DEBUG is set (default y)
$ size fs/cifs/cifs.ko*
text data bss dec hex filename
265245 2525 132 267902 4167e fs/cifs/cifs.ko.new
268359 2525 132 271016 422a8 fs/cifs/cifs.ko.oldOther miscellaneous changes around these conversions:
o Miscellaneous typo fixes
o Add terminating \n's to almost all formats and remove them
from the macros to be more kernel style like. A few formats
previously had defective \n's
o Remove unnecessary OOM messages as kmalloc() calls dump_stack
o Coalesce formats to make grep easier,
added missing spaces when coalescing formats
o Use %s, __func__ instead of embedded function name
o Removed unnecessary "cifs: " prefixes
o Convert kzalloc with multiply to kcalloc
o Remove unused cifswarn macroSigned-off-by: Joe Perches
Signed-off-by: Jeff Layton
Signed-off-by: Steve French
07 Mar, 2013
1 commit
-
Cc: stable@vger.kernel.org
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French
02 Jan, 2013
1 commit
-
If we have mandatory byte-range locks on a file we can't cache reads
because pagereading may have conflicts with these locks on the server.
That's why we should allow level2 oplocks for files without mandatory
locks only.Signed-off-by: Pavel Shilovsky
Acked-by: Jeff Layton
Signed-off-by: Steve French
10 Dec, 2012
1 commit
-
Restructure code to make SMB2 vs. SMB3 signing a protocol
specific op. SMB3 signing (AES_CMAC) is not enabled yet,
but this restructuring at least makes sure we don't send
an smb2 signature on an smb3 signed connection. A followon
patch will add AES_CMAC and enable smb3 signing.Signed-off-by: Steve French
Acked-by: Jeff Layton
06 Dec, 2012
2 commits
-
This patch enables optional for original SMB2 (SMB2.02) dialect
by specifying vers=2.0 on mount.Reviewed-by: Pavel Shilovsky
Signed-off-by: Steve French -
because the is no difference here. This also adds support of prefixpath
mount option for SMB2.Signed-off-by: Pavel Shilovsky
Reviewed-by: Jeff Layton
Signed-off-by: Steve French
02 Oct, 2012
1 commit
-
Based on whether the user (on mount command) chooses:
vers=3.0 (for smb3.0 support)
vers=2.1 (for smb2.1 support)
or (with subsequent patch, which will allow SMB2 support)
vers=2.0 (for original smb2.02 dialect support)send only one dialect at a time during negotiate (we
had been sending a list).Reviewed-by: Jeff Layton
Signed-off-by: Steve French
27 Sep, 2012
1 commit
-
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French
25 Sep, 2012
17 commits
-
Some trivial endian fixes for the SMB2 code. One
warning remains which I asked Pavel to look at.Reviewed-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
if server supports them and we need oplocks.
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
-
Signed-off-by: Pavel Shilovsky
-
Now that we aren't abusing the kmap address space, there's no need for
this lock or to impose a limit on the rsize.Signed-off-by: Jeff Layton
-
Now that we're not kmapping so much at once, there's no need to cap
the wsize at the amount that can be simultaneously kmapped.Reviewed-by: Pavel Shilovsky
Signed-off-by: Jeff Layton
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French -
Signed-off-by: Pavel Shilovsky
Signed-off-by: Steve French