From: Pavel Shilovsky Date: Thu, 6 Dec 2012 18:07:52 +0000 (+0400) Subject: CIFS: Fix write after setting a read lock for read oplock files X-Git-Tag: omap-for-v3.8/fixes-for-merge-window-v4-signed~54^2 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c299dd0e2d3dd61d0048a9d9b021aa01f023ed0c;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 populating the page cache without marking affected pages dirty after a successful write directly to the server. Also remove CONFIG_CIFS_SMB2 ifdefs because it's suitable for both CIFS and SMB2 protocols. Signed-off-by: Pavel Shilovsky Signed-off-by: Jeff Layton Signed-off-by: Steve French --- Reading git-diff-tree failed