From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: [QUESTION] How to use interruptible_sleep_on() without races ?
Date: Thu, 4 Apr 2002 19:08:48 -0800 [thread overview]
Message-ID: <20020404190848.C27209@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020404185232.B27209@bougret.hpl.hp.com> <E16tKGi-0007Sy-00@the-village.bc.nu>
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...
> Actually the code it uses is clean, slightly verbose but clean. It puts
> the phases in the right order and that fixes the race cleanly. You
> could just use completions in that case or you could use
>
> wait_event_interruptible(&my_wait_queue, my_condition==FALSE)
>
> which is a macro that generates the right stuff.
And it might even want to be defined in include/linux/sched.h
as a replacement for interruptible_sleep_on(). It seems like a generic
need, and I would feel much safer if one of the guru wrote it properly
for me ;-)
> Alan
Regards,
Jean
next prev parent reply other threads:[~2002-04-05 3:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 2:52 [QUESTION] How to use interruptible_sleep_on() without races ? Jean Tourrilhes
2002-04-05 3:20 ` Alan Cox
2002-04-05 3:08 ` Jean Tourrilhes [this message]
2002-04-05 4:49 ` Linus Torvalds
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=20020404190848.C27209@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=jt@hpl.hp.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 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.