From: Oleg Nesterov <oleg@redhat.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ben Hutchings <ben@decadent.org.uk>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Herton Krzesinski <herton.krzesinski@canonical.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH -stable 0/1] freezer: PF_FREEZER_NOSIG should be cleared along with PF_NOFREEZE
Date: Fri, 7 Dec 2012 15:49:01 +0100 [thread overview]
Message-ID: <20121207144901.GA6478@redhat.com> (raw)
In-Reply-To: <50C10391.4040903@canonical.com>
On 12/06, Joseph Salisbury wrote:
>
> A couple of people have tested your patch and report if fixes the
> suspend/resume bug[0].
Great, thanks a lot.
> Will you be
> requesting this patch in the stable kernels?
I have to ;)
I tried to explain this in the changelog, but once again just in case...
This patch is only for -stable. It is only needed if a) b40a7959 was
backported and b) the kernel still has PF_FREEZER_NOSIG removed in 3.3.
Alernatively, b40a7959 can be reverted. But please note that this will
just hide the problem revealed by "incomplete" b40a7959.
Oleg.
next prev parent reply other threads:[~2012-12-07 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50BF9CC2.7070705@canonical.com>
[not found] ` <1354762294.17107.157.camel@deadeye.wl.decadent.org.uk>
2012-12-06 12:42 ` freezer: exec should clear PF_NOFREEZE along with PF_KTHREAD Oleg Nesterov
2012-12-06 20:44 ` Joseph Salisbury
2012-12-07 14:49 ` Oleg Nesterov [this message]
2012-12-07 14:49 ` [PATCH -stable 1/1] freezer: PF_FREEZER_NOSIG should be cleared along with PF_NOFREEZE Oleg Nesterov
2012-12-09 23:04 ` Ben Hutchings
2012-12-10 20:34 ` Greg Kroah-Hartman
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=20121207144901.GA6478@redhat.com \
--to=oleg@redhat.com \
--cc=ben@decadent.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=herton.krzesinski@canonical.com \
--cc=joseph.salisbury@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stable@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 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.