CIFS: Fix oplock break handling (try #2)

Browse source

When we get oplock break notification we should set the appropriate
value of OplockLevel field in oplock break acknowledge according to
the oplock level held by the client in this time. As we only can have
level II oplock or no oplock in the case of oplock break, we should be
aware only about clientCanCacheRead field in cifsInodeInfo structure.

Also fix bug connected with wrong interpretation of OplockLevel field
during oplock break notification processing.

Signed-off-by: Pavel Shilovsky <piastryyy@gmail.com>
Cc: <stable@kernel.org>
Signed-off-by: Steve French <sfrench@us.ibm.com>

...

This commit is contained in:

Pavel Shilovsky 2011-01-17 20:15:44 +03:00 • committed by Steve French

parent c56eb8fb6d

commit 12fed00de9

4 changed files with 16 additions and 13 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

fs/cifs/cifsproto.h

View file

4

fs/cifs/cifssmb.c

View file

21

fs/cifs/file.c

View file

2

fs/cifs/misc.c

View file