From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jt@hpl.hp.com
Cc: linux-kernel@vger.kernel.org (Linux kernel mailing list),
alan@lxorguk.ukuu.org.uk (Alan Cox),
jgarzik@mandrakesoft.com (Jeff Garzik)
Subject: Re: [QUESTION] How to use interruptible_sleep_on() without races ?
Date: Fri, 5 Apr 2002 04:20:04 +0100 (BST) [thread overview]
Message-ID: <E16tKGi-0007Sy-00@the-village.bc.nu> (raw)
In-Reply-To: <20020404185232.B27209@bougret.hpl.hp.com> from "Jean Tourrilhes" at Apr 04, 2002 06:52:32 PM
> if(my_condition == TRUE)
> interruptible_sleep_on(&my_wait_queue);
> ----------------------------------
>
> Then, at some point, a timer/BH/soft-irq will do :
> -------------------------------
> my_condition == FALSE;
> wake_up_interruptible(&my_wait_queue);
>
> 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
> interruptible_sleep_on() but use some complex code around schedule()
> (and there must be a simpler and cleaner solution for such a simple
> problem).
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.
Alan
next prev parent reply other threads:[~2002-04-05 3:03 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 [this message]
2002-04-05 3:08 ` Jean Tourrilhes
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=E16tKGi-0007Sy-00@the-village.bc.nu \
--to=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 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®