From: Rusty Russell <rusty@rustcorp.com.au>
To: alexander.riesen@synopsys.COM
Cc: akpm@zip.com.au, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Futex minor fixes
Date: Thu, 28 Aug 2003 10:49:10 +1000 [thread overview]
Message-ID: <20030828080404.0B1AD2C89E@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 27 Aug 2003 08:50:16 +0200." <20030827065016.GA11214@Synopsys.COM>
In message <20030827065016.GA11214@Synopsys.COM> you write:
> Btw, what could that spurious wakeups be?
I don't know, but every other primitive in the kernel handles it, so
we should too.
> It set to loop unconditionally, so if the source of wakeup insists on
> wakeing up the code could result in endless loop, right?
Yes. If someone wakes you up, you will wake up. If someone wakes you
up an infinite number of times, you will wake up an infinite number of
times. cf. waitqueues.
Hope that clarifies,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-08-28 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 3:05 [PATCH 1/2] Futex minor fixes Rusty Russell
2003-08-26 9:26 ` Alex Riesen
2003-08-27 2:40 ` Rusty Russell
2003-08-27 6:50 ` Alex Riesen
2003-08-28 0:49 ` Rusty Russell [this message]
2003-08-28 8:08 ` Alex Riesen
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=20030828080404.0B1AD2C89E@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@zip.com.au \
--cc=alexander.riesen@synopsys.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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