From: Olaf Hering <olh@suse.de>
To: Olaf Kirch <okir@suse.de>
Cc: nfs@lists.sourceforge.net, akpm@osdl.org
Subject: Re: [PATCH fs/locks 2 of 3] Use proper tgid in locks_remove_posix
Date: Sat, 16 Jul 2005 17:15:27 +0200 [thread overview]
Message-ID: <20050716151527.GA7726@suse.de> (raw)
In-Reply-To: <20050711103250.GH27163@suse.de>
On Mon, Jul 11, Olaf Kirch wrote:
> # Subject: [NFS] Use proper tgid in locks_remove_posix
> #
> # This patch fixes a problem with lost unlock calls in multithreaded
> # applications. locks_remove_posix would send a single unlock call with
> # the task group ID of the current process, which may not be the same as
> # the tgid of the lock. This patch ensures that we send separate unlock
> # calls for different fl_pid values.
> #
> # Signed-off-by: Olaf Kirch <okir@suse.de>
>
> Index: linux-2.6.12/fs/locks.c
This leads to glibc make check errors on ppc64:
cat /usr/src/packages/BUILD/glibc-2.3/cc-nptl/nptl/tst-cancel16.out
Timed out: killed the child process
1
tested with 2.6.13-rc3 and 'powerpc32 make check'
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-07-16 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 10:32 [PATCH fs/locks 2 of 3] Use proper tgid in locks_remove_posix Olaf Kirch
2005-07-11 12:16 ` Trond Myklebust
2005-07-11 12:48 ` Olaf Kirch
2005-07-11 13:02 ` Trond Myklebust
2005-07-11 13:16 ` Olaf Kirch
2005-07-11 13:33 ` Peter Staubach
2005-07-11 13:52 ` Trond Myklebust
2005-07-11 14:23 ` Olaf Kirch
2005-07-16 15:15 ` Olaf Hering [this message]
2005-07-17 16:42 ` Olaf Kirch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050716151527.GA7726@suse.de \
--to=olh@suse.de \
--cc=akpm@osdl.org \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.