mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@intercode.com.au>
To: kuznet@ms2.inr.ac.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] sigurg/sigio cleanup for 2.5.31
Date: Fri, 16 Aug 2002 23:07:22 +1000 (EST)	[thread overview]
Message-ID: <Mutt.LNX.4.44.0208162239370.687-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <200208152236.CAA27992@sex.inr.ac.ru>

On Fri, 16 Aug 2002 kuznet@ms2.inr.ac.ru wrote:

> I do not know what forced you to use BKL.

All existing paths which write to the pid/uid/euid fields are protected by
the BKL (except for the futex code, which doesn't need it).  None of
these, or the new paths which grab the BKL, are performance critical, as
they're ioctl() or fcntl() handlers.

> But I daresay this is deadlock:

Yep.


- James
-- 
James Morris
<jmorris@intercode.com.au>




  reply	other threads:[~2002-08-16 13:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15 17:16 James Morris
2002-08-15 19:04 ` Matthew Wilcox
2002-08-16  0:10   ` James Morris
2002-08-15 22:36 ` kuznet
2002-08-16 13:07   ` James Morris [this message]
2002-08-16 14:50     ` kuznet
2002-08-16 15:03       ` James Morris
2002-08-16 15:16         ` kuznet
2002-08-16  7:06 ` Chris Wright
2002-08-16 16:25 ` Jeff Dike
2002-08-16 15:59   ` James Morris
2002-08-17 18:16     ` Alan Cox
2002-08-18  0:57       ` James Morris
2002-08-19  1:16         ` James Morris
2002-08-17  2:58 ` [PATCH][RFC] sigurg/sigio cleanup for 2.5.31 [version 2] James Morris
2002-08-19  2:28   ` Jeff Dike
2002-08-19  1:37     ` James Morris
2002-08-19 10:14   ` [PATCH][RFC] sigurg/sigio cleanup for 2.5.31 [version 3] James Morris

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=Mutt.LNX.4.44.0208162239370.687-100000@blackbird.intercode.com.au \
    --to=jmorris@intercode.com.au \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®