2012/12/3 Steve French <[email protected]>: > Just to doublecheck semantics ... posix applications (on the Linux > kernel client) want to always allow a write where possible - if Wine > issues a mandatory lock on a cached file do we want it to apply to > posix applications or just applications like Wine? Is the only way we > can tell the difference the mount option you suggested? >
This change is not targeted to fix Wine-specific behavior. If we negotiate mandatory locking we need to be sure the server and client are the same: the server denied writes to the range locked with read lock - we should do the same things on the client to make the behavior not depend on the kind of oplock we have now. As for wine mount option: now, when we have rwpidforward and forcemand mount options, I don't think we need it because all that it should do is rwpidforward + forcemand + strictcache. -- Best regards, Pavel Shilovsky. -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
