[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fuse-devel
Subject:    Re: [fuse-devel] [2.8.x] ulockmgr_server issue / fusexmp_fh example
From:       Sebastian Pipping <webmaster () hartwork ! org>
Date:       2011-07-07 17:03:17
Message-ID: 4E15E6D5.10602 () hartwork ! org
[Download RAW message or body]

On 07/06/2011 12:57 PM, Miklos Szeredi wrote:
> I'll have two patches for this, one kernel and one userspace.  I'll post
> them shortly.

Seen the patches, great!  They look like you put love into them, thanks!


> Lets take an example:
> 
> File F on fusexmp_fh filesystem corresponds to file X on underlying
> filesystem.
> 
> If Process P locks F then GETLK on F will return l_pid=P, GETLK on X will
> return l_pid=U, where U is the ulockmgr_server process corresponding to
> the lock.
> 
> If process P locks X then GETLK on both F and X will return l_pid=P.
> 
> If another fusexmp_fh is mounted and there G also corresponds to X on
> the underlying filesystem and P locks F the GETLK on G and X will return
> l_pid=U, while GETLK on F will return P.

Maybe that's not too bad after all.  Thanks for the detailed example.

Best,



Sebastian

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
fuse-devel mailing list
fuse-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fuse-devel
[prev in list] [next in list] [prev in thread] [next in thread]