Pavel Shilovsky 88cf75aaaf 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 <piastry@etersoft.ru>
Reviewed-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve French <smfrench@gmail.com>
2013-01-01 23:04:14 -06:00
..
2012-12-20 14:00:01 -05:00
2012-12-20 14:00:01 -05:00
2012-12-20 14:00:01 -05:00
2012-11-16 11:20:42 -06:00
2012-12-20 17:40:20 -08:00
2012-12-20 14:00:01 -05:00
2012-12-20 18:40:00 -05:00
2012-12-20 18:40:52 -05:00
2012-12-20 18:40:53 -05:00
2012-12-20 18:40:53 -05:00
2012-12-20 18:40:54 -05:00
2012-12-20 18:40:54 -05:00
2012-12-20 18:40:55 -05:00
2012-12-20 14:00:01 -05:00
2012-12-20 14:00:01 -05:00
2012-07-14 16:34:47 +04:00
2012-12-20 14:00:01 -05:00
2012-12-20 14:00:01 -05:00
2012-12-17 17:15:26 -08:00
2012-12-20 14:00:01 -05:00
2012-10-22 08:50:37 +03:00
2012-10-29 09:00:57 -07:00
2012-10-09 15:52:31 +09:00
2012-11-28 21:49:02 -05:00
2012-12-20 18:46:29 -05:00
2012-10-09 18:35:22 -04:00
2012-12-11 13:43:42 +09:00
2012-09-26 21:08:52 -04:00
2012-12-17 17:15:27 -08:00
2012-12-20 18:50:01 -05:00
2012-10-09 23:33:39 -04:00