From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: [QUESTION] How to use interruptible_sleep_on() without races ?
Date: Fri, 5 Apr 2002 04:49:28 +0000 (UTC) [thread overview]
Message-ID: <a8jaco$avc$1@penguin.transmeta.com> (raw)
In-Reply-To: <20020404185232.B27209@bougret.hpl.hp.com> <E16tKGi-0007Sy-00@the-village.bc.nu> <20020404190848.C27209@bougret.hpl.hp.com>
In article <20020404190848.C27209@bougret.hpl.hp.com>,
Jean Tourrilhes <jt@bougret.hpl.hp.com> wrote:
>On Fri, Apr 05, 2002 at 04:20:04AM +0100, Alan Cox wrote:
>> >
>> > I looked at it in every possible way, and I don't see how it
>> > is possible to use safely interruptible_sleep_on(). And I wonder :
>>
>> It isnt for interrupt stuff - its going back to the old kernel behaviour
>> when it used to be usable
>
> So, maybe it would be a nice idea to remove it from the 2.5.X
>kernel to force a "spring cleanup" of the old code. If it's no longer
>usable and only confusing, it should be purged...
It's still usable, but under rather specific conditions, namely:
- both sleeper and waker in process context and with BKL held.
- OR if missing a wakeup isn't a horrible problem.
And there does seem to be a lot of legacy users out there.
I wouldn't mind a spring cleaning, but the fact is that right now in
2.5.x I'd rather have driver writers wake up to the fact that we had a
spring cleaning in the block layer several months ago, rather than
introduce a new one ;)
Linus
next prev parent reply other threads:[~2002-04-05 4:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 2:52 Jean Tourrilhes
2002-04-05 3:20 ` Alan Cox
2002-04-05 3:08 ` Jean Tourrilhes
2002-04-05 4:49 ` Linus Torvalds [this message]
2002-04-05 7:54 ` bert hubert
2002-04-05 12:58 ` Alan Cox
2002-04-05 20:16 ` Jean Tourrilhes
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='a8jaco$avc$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--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®