[linux-cifs-client] [PATCH 0/2] posix locks behaviour on Windows server

Pavel Shilovsky piastry at etersoft.ru
Sat Mar 14 08:00:24 GMT 2009


On Thursday 05 March 2009 22:15:01 you wrote:
> Pavel Shilovsky wrote:
> > What is about my patch?
> >
> >
> > --
> > Best regards,
> > Pavel Shilovsky.
>
> My first reaction was that it added complexity to a mainline path, for a
> case in which posix behavior was unlikely to be understood by developers
> (and this odd quirk of posix locking behavior is unlikely to be an app
> dependency) so would like more convincing evidence that it actually
> breaks an app before turning it on by default (I am not arguing against
> implementing posix behaviors in general, but just that "Linux
> developers" are just as likely to assume the opposite behavior as posix
> in this case, so this is riskier than it looks to turn on by default).
>
> IIRC you noted that Wine depends on this behavior- but was hoping a
> better way to solve Wine's needs was by passing through the mandatory
> locking behavior that Windows apps would need (I realize that this has
> obstacles ... in getting the linux-fsdevel community to understand why
> headers or minor vfs changes would be needed for this)
>
It is connected with some more troubles when we have windows locks behavior on 
share but posix locks behaviour on other system. That's why special workaround 
is used in wine, but It isn't a good way, I think.

Yes, "Linux developers" don't like such posix behaviour, but standard is 
standard... If we follow it in one things and don't - in another, It can make 
many problems! It's my opinion, of course.

>
> Jeff,
> Thoughts?

-- 
Best regards,
Pavel Shilovsky.


More information about the linux-cifs-client mailing list