[Gluster-devel] Re: Threads and locks: tgid vs pid

[Anand Avati]

----- "Corentin Chary" <corentin.chary at gmail.com> wrote:

> On Wed, Oct 21, 2009 at 7:11 PM, Corentin Chary
> <corentin.chary at gmail.com> wrote:
> > On Wed, Oct 21, 2009 at 3:16 PM, Corentin Chary
> > <corentin.chary at gmail.com> wrote:
> >> First, some background:
> >>  - getpid() returns current->tgid which is the pid of the first
> thread
> >>  - gettid() returns current->pid which is the pid of the current
> thread
> >> For all threads, getpid() is the same.
> >>


Corentin,
   Good analysis. We actually do have this corresponding patch in the
glfs patched fuse kernel module to use gettgid() instead of getpid()
to fill up the pid field in the upcalls. In fact moving over to using
lock_owner field has been in the works and currently there is a patch
floating around internally and will be posted on patches.gluster.com
soon. Please check whether the glfs patched fuse kernel module fixes
the sqlite problem for you. It somehow failed to occur to me that your
issue was related to the (previously known) tgid problem.

Thanks!
Avati