[linux-cifs-client] Re: POSIX client locking semantics.

[Steven French]

I don't use either the level (0x208) or the unix cap bit yet on the client
(it is unlikely that other clients do either) - so reusing this bit comes
down to what Samba (the server) does with it today - if no one (server)
sets it - and we are using it for approximately the same purpose that it
was created for - seems less confusing to reuse it.


Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: 512-838-2294
email: sfrench at-sign us dot ibm dot com

Jeremy Allison <jra at samba.org> wrote on 10/20/2005 10:41:40 AM:

> On Thu, Oct 20, 2005 at 10:41:21AM -0500, Steven French wrote:
> >
> > > Can you explain what you mean here ?
> > Sorry to be cryptic, I did not have source in front of me at the time
but
> > wanted to remind people new to this topic about what was already
defined.
> >
> > #define CIFS_UNIX_FCNTL_CAP 0x00000001
> >
> > is one of the bits that can be returned by the 64 bit capability flags
on
> > QFSINFO FILE_SYSTEM_UNIX_INFO (It was defined in the original Unix
> > extensions spec).   Presumably the setfsinfo would set this.
> >
> > For those who had not been following this thread ... in addition to the
> > capability bit, a year or so ago we reserved a FILEINFO/PATHINFO level
for
> > GET/SET of posix locks (as level 0x208) and made a stab at defining a
> > CIFS_POSIX_LOCK structure.
>
> Ok thanks I see what you mean. The only problem I have with it
> is I'm proposing to change the read/write semantics in this
> case, so was wondering if the set should be of a differently
> named bit.
>
> Jeremy.
-------------- next part --------------
HTML attachment scrubbed and removed