* Vivek Goyal (vgo...@redhat.com) wrote:
> On Wed, Jan 15, 2020 at 06:38:31PM -0500, Masayoshi Mizuma wrote:
>
> [..]
> > > +/* Should be called with inode->plock_mutex held */
> > > +static struct lo_inode_plock *lookup_create_plock_ctx(struct lo_data *lo,
> > > +
On Wed, Jan 15, 2020 at 06:38:31PM -0500, Masayoshi Mizuma wrote:
[..]
> > +/* Should be called with inode->plock_mutex held */
> > +static struct lo_inode_plock *lookup_create_plock_ctx(struct lo_data *lo,
> > + struct lo_inode
> > *inode,
> >
On Thu, Dec 12, 2019 at 04:38:45PM +, Dr. David Alan Gilbert (git) wrote:
> From: Vivek Goyal
>
> Doing posix locks with-in guest kernel are not sufficient if a file/dir
> is being shared by multiple guests. So we need the notion of daemon doing
> the locks which are visible to rest of the gu
From: Vivek Goyal
Doing posix locks with-in guest kernel are not sufficient if a file/dir
is being shared by multiple guests. So we need the notion of daemon doing
the locks which are visible to rest of the guests.
Given posix locks are per process, one can not call posix lock API on host,
other
