From: Andrew Morton <akpm@linux-foundation.org>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Mike Galbraith <efault@gmx.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 2/3] ipc/sem.c: handle spurious wakeups
Date: Tue, 11 Oct 2011 14:54:41 -0700 [thread overview]
Message-ID: <20111011145441.228e4c94.akpm@linux-foundation.org> (raw)
In-Reply-To: <1316885831-11996-1-git-send-email-manfred@colorfullife.com>
On Sat, 24 Sep 2011 19:37:11 +0200
Manfred Spraul <manfred@colorfullife.com> wrote:
> semtimedop() does not handle spurious wakeups, it returns -EINTR to user space.
> Most other schedule() users would just loop and not return to user space.
> The patch adds such a loop to semtimedop()
What is a "spurious wakeup" and how can a process receive one?
I'm wondering about the userspace-visible effects of this change, and
any compatibility issues?
next prev parent reply other threads:[~2011-10-11 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 17:37 [PATCH 2/3] ipc/sem.c: handle spurious wakeups Manfred Spraul
2011-10-11 21:54 ` Andrew Morton [this message]
2011-10-12 7:09 ` Peter Zijlstra
2011-10-13 18:51 ` Manfred Spraul
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=20111011145441.228e4c94.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=tglx@linutronix.de \
/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.