linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Domenico Andreoli <cavokz@gmail.com>
To: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
Cc: linux-parisc@vger.kernel.org, jejb@parisc-linux.org,
	kyle@mcmartin.ca, deller@gmx.de, carlos@systemhalted.org,
	debian-hppa@lists.debian.org
Subject: Re: [PATCH] parisc: futex: Use same lock set as lws calls
Date: Mon, 17 Oct 2011 17:23:58 +0200	[thread overview]
Message-ID: <20111017152358.GA3518@glitch> (raw)
In-Reply-To: <20111009204010.GA22374@hiauly1.hia.nrc.ca>

Hi John,

On Sun, Oct 09, 2011 at 04:40:10PM -0400, John David Anglin wrote:
> In debugging the failure of the glibc tst-cond18 test on parisc, I realized
> that futexes need to use the same locks the lws calls.  This fixes all the
> pthread 'cond' tests.  Sadly, there are still problems with thread cancellation.

I applied your patch to 3.1-rc9 and tried to build Debian eglibc 2.13-21. It
passed tst-cond18 but is hanging on tst-fork1. Is it where you see the thread
cancellation issue?

Thank you for having looked at it.

Regards,
Domenico

  parent reply	other threads:[~2011-10-17 15:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 20:40 [PATCH] parisc: futex: Use same lock set as lws calls John David Anglin
2011-10-10 14:30 ` Rolf Eike Beer
2011-10-10 20:27   ` John David Anglin
2011-10-10 20:30     ` James Bottomley
2011-10-17 15:23 ` Domenico Andreoli [this message]
2011-10-17 15:47   ` Carlos O'Donell
2011-10-17 18:10     ` John David Anglin
2011-10-17 20:55       ` Carlos O'Donell
2011-10-17 21:09         ` John David Anglin
2011-10-17 21:57           ` Domenico Andreoli
2011-10-17 22:28             ` John David Anglin
2011-10-18  9:31               ` Domenico Andreoli
2011-10-18  9:33               ` Domenico Andreoli
2011-10-18 14:20                 ` John David Anglin
2011-10-18  3:01           ` Carlos O'Donell
2011-10-18  3:21             ` Carlos O'Donell
2011-10-18 21:22               ` Carlos O'Donell
2011-10-20 15:35           ` Carlos O'Donell
2011-10-20 17:57             ` Matt Turner
2011-10-20 18:11               ` Carlos O'Donell
2011-10-20 18:16                 ` Matt Turner
2011-10-20  1:47       ` John David Anglin
2011-10-21 14:49         ` Carlos O'Donell
2011-10-21 17:42           ` John David Anglin
2011-10-21 18:11             ` John David Anglin
2011-10-21 18:15               ` Carlos O'Donell
2011-10-30 15:04                 ` John David Anglin
2011-10-30 15:31                   ` Rolf Eike Beer
2011-10-30 16:13                     ` John David Anglin
2011-10-31  0:21                       ` Carlos O'Donell
2011-10-31  1:36                         ` John David Anglin
2011-10-31  9:41                           ` Domenico Andreoli
2011-10-31 12:28                             ` John David Anglin
2011-10-31 23:26                             ` John David Anglin
2011-11-01  9:15                               ` Domenico Andreoli
2011-11-01  2:15                           ` Carlos O'Donell
2011-11-01  9:19                             ` Domenico Andreoli
2011-11-01 19:56                               ` John David Anglin

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=20111017152358.GA3518@glitch \
    --to=cavokz@gmail.com \
    --cc=carlos@systemhalted.org \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=debian-hppa@lists.debian.org \
    --cc=deller@gmx.de \
    --cc=jejb@parisc-linux.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).