linux-kernel - Re: [PATCH] fix 2.6.32.23 suspend regression caused by commit 6f6198a

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1285962251.9020.6.camel@marge.simson.net>
Date:	Fri, 01 Oct 2010 21:44:11 +0200
From:	Mike Galbraith <efault@....de>
To:	Greg KH <greg@...ah.com>
Cc:	stable <stable@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] fix 2.6.32.23 suspend regression caused by commit
 6f6198a

On Fri, 2010-10-01 at 12:16 -0700, Greg KH wrote:
> On Fri, Oct 01, 2010 at 07:04:11AM +0200, Mike Galbraith wrote:
> > Again, with a less bouncy address.
> > 
> > From: Mike Galbraith <efault@....de>
> > Date: Fri, 1 Oct 2010 05:57:59 +0200
> > Subject: [PATCH] fix 2.6.32.23 suspend regression caused by commit
> > 6f6198a
> > 
> > 6f6198a sched: kill migration thread in CPU_POST_DEAD instead of
> > CPU_DEAD
> > leaves migration threads lying about.  Mask out CPU_TASKS_FROZEN.
> > 
> > Signed-off-by: Mike Galbraith <efault@....de>
> 
> Is this patch upstream already?  If so, what's the git commit id of it?
> If not, why isn't it also needed there?

No, it's not upstream, and will never go upstream because they don't
need it.  It's only needed for -stable because the fix incorporated in
-stable is incomplete.  Upstream already does what this patch adds.

	-Mike

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/