From: Pavel Shilovsky Date: Fri, 21 Dec 2012 11:07:52 +0000 (+0400) Subject: CIFS: Fix write after setting a read lock for read oplock files X-Git-Tag: v3.8-rc3~10^2~1 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=88cf75aaaf27a652b3e85960ac3060172dd3edac;p=pandora-kernel.git CIFS: Fix write after setting a read lock for read oplock files If we have a read oplock and set a read lock in it, we can't write to the locked area - so, filemap_fdatawrite may fail with a no information for a userspace application even if we request a write to non-locked area. Fix this by writing directly to the server and then breaking oplock level from level2 to None. Also remove CONFIG_CIFS_SMB2 ifdefs because it's suitable for both CIFS and SMB2 protocols. Signed-off-by: Pavel Shilovsky Reviewed-by: Jeff Layton Signed-off-by: Steve French --- Reading git-diff-tree failed