mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, oleg@redhat.com,
	peterz@infradead.org
Subject: Re: [PATCH] signals: work around random wakeups in sigsuspend()
Date: Mon, 25 Jan 2016 13:32:05 -0800	[thread overview]
Message-ID: <20160125133205.36542c86ada93761d8a9ff06@linux-foundation.org> (raw)
In-Reply-To: <1453735306-13519-1-git-send-email-sasha.levin@oracle.com>

On Mon, 25 Jan 2016 10:21:46 -0500 Sasha Levin <sasha.levin@oracle.com> wrote:

> A random wakeup can get us out of sigsuspend() without TIF_SIGPENDING
> being set.
> 
> Avoid that by making sure we were signaled, like sys_pause() does.

What we're lacking here is any description of the end-user-visible
effects of the bug.  Enough for people to be able to decide (and to
recognize!) whether their kernel needs this patch.</stdrefrain> 

  parent reply	other threads:[~2016-01-25 21:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 15:21 Sasha Levin
2016-01-25 19:09 ` Oleg Nesterov
2016-01-25 19:37   ` Peter Zijlstra
2016-02-25  3:18   ` Al Viro
2016-02-25  8:11     ` Peter Zijlstra
2016-02-25 17:34       ` Al Viro
2016-01-25 21:32 ` Andrew Morton [this message]
2016-01-26 21:10   ` Oleg Nesterov
2016-01-27  8:44     ` Peter Zijlstra
2016-01-27 16:41       ` Oleg Nesterov
2016-01-27 17:54         ` Peter Zijlstra
2016-01-27 18:39         ` Andrew Morton
2016-01-27 21:07           ` Oleg Nesterov
2016-01-27 17:24       ` Sasha Levin
2016-01-26  6:44 ` Ingo Molnar
2016-01-26 15:05   ` Oleg Nesterov

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=20160125133205.36542c86ada93761d8a9ff06@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sasha.levin@oracle.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

Powered by JetHome