2011/1/14 Pavel Shilovsky <piastryyy@xxxxxxxxx>: > 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@xxxxxxxxx> > Cc: <stable@xxxxxxxxxx> What's about this? -- Best regards, Pavel Shilovsky. -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
