All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Oleg Nesterov <oleg@redhat.com>, Alan Cox <alan@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysrq: Use SEND_SIG_FORCED instead of force_sig()
Date: Tue, 27 Mar 2012 17:03:37 +0400	[thread overview]
Message-ID: <20120327130337.GA7972@lizard> (raw)
In-Reply-To: <20120326154303.86126785.akpm@linux-foundation.org>

On Mon, Mar 26, 2012 at 03:43:03PM -0700, Andrew Morton wrote:
> On Sat, 24 Mar 2012 15:00:24 +0400
[...]
> > > force_sig() can't kill the process if the main thread has already
> > > exited. IOW, it is trivial to create the process which can't be
> > > killed by sysrq.
> > 
> > So, this patch fixes the issue.
[...]
> It's unclear how serious this race is (I'm guessing "not very"), but
> this patch looks like 3.3 material anyway, yes?

Yep, 3.3 looks like a good target.

Thanks,

-- 
Anton Vorontsov
Email: cbouatmailru@gmail.com

  reply	other threads:[~2012-03-27 13:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 11:00 [PATCH] sysrq: Use SEND_SIG_FORCED instead of force_sig() Anton Vorontsov
2012-03-26 22:43 ` Andrew Morton
2012-03-27 13:03   ` Anton Vorontsov [this message]
2012-03-28 20:52   ` Oleg Nesterov
2012-03-28 21:08     ` Andrew Morton
2012-03-28 21:26       ` Oleg Nesterov
     [not found] <13288070803232@kroah.org>
     [not found] ` <20120210201008.GA21009@redhat.com>
2012-02-14 22:50   ` Anton Vorontsov
2012-02-14 23:03     ` Greg Kroah-Hartman
2012-02-15 13:53     ` 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=20120327130337.GA7972@lizard \
    --to=cbouatmailru@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@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 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.