public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Hubertus Franke <frankeh@watson.ibm.com>
Cc: davidel@xmailserver.org, rml@tech9.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fast Userspace Mutexes III.
Date: Tue, 5 Mar 2002 15:48:38 +1100	[thread overview]
Message-ID: <20020305154838.66c82118.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20020304154848.A1055@elinux01.watson.ibm.com>
In-Reply-To: <1015271393.15277.112.camel@phantasy> <Pine.LNX.4.44.0203041208310.1561-100000@blue1.dev.mcafeelabs.com> <20020304154848.A1055@elinux01.watson.ibm.com>

On Mon, 4 Mar 2002 15:48:48 -0500
Hubertus Franke <frankeh@watson.ibm.com> wrote:

> Also, the check on PROT_SEM is missing. I tried this before and glibc filtered
> these flags out when set. But effectively, one still needs to check
> whether semaphores are allowed during the sys_futex call.

Neither arch I care about (ppc, x86) needs to do anything with PROT_SEM, so it's
OK.  glibc will have to be fixed on any architectures which require help here,
and a hook will be needed somewhere in the kernel for them.

I didn't implement it because I don't *know* which archs will need something,
and what they will need.  Hence my request for arch maintainers to step
forward (Linus said they exist, and I believe him).

Hope that clarifies this particular wart...
Rusty.
-- 
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  parent reply	other threads:[~2002-03-05  4:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-04  3:55 [PATCH] Fast Userspace Mutexes III Rusty Russell
2002-03-04 19:49 ` Robert Love
2002-03-04 20:13   ` Davide Libenzi
2002-03-04 20:20     ` Matthew Kirkwood
2002-03-04 20:48     ` Hubertus Franke
2002-03-04 22:15       ` Davide Libenzi
2002-03-05  1:50         ` Robert Love
2002-03-05  2:53           ` Davide Libenzi
2002-03-05  3:45           ` Rusty Russell
2002-03-05  3:55             ` Davide Libenzi
2002-03-05  6:11               ` Rusty Russell
2002-03-05 17:23                 ` Davide Libenzi
2002-03-05 15:09             ` Hubertus Franke
2002-03-05  4:30           ` Edgar Toernig
2002-03-07  1:58         ` Richard Henderson
2002-03-07  2:10           ` Davide Libenzi
2002-03-05  4:48       ` Rusty Russell [this message]
2002-03-05 15:15         ` Hubertus Franke
2002-03-06  1:31           ` Rusty Russell
2002-03-05  1:34   ` Rusty Russell
2002-03-07  1:52 ` Richard Henderson
2002-03-07  3:39   ` Rusty Russell
2002-03-07  8:48     ` Richard Henderson
2002-03-07  9:17       ` Rusty Russell

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=20020305154838.66c82118.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=davidel@xmailserver.org \
    --cc=frankeh@watson.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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