linux-kernel - Re: [stable] [PATCH 1/14] uml: fix build when SLOB is enabled

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: <20080802010044.GA16405@c2.user-mode-linux.org>
Date:	Fri, 1 Aug 2008 21:00:44 -0400
From:	Jeff Dike <jdike@...toit.com>
To:	Greg KH <greg@...ah.com>
Cc:	stable@...nel.org, WANG Cong <xiyou.wangcong@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	uml-devel <user-mode-linux-devel@...ts.sourceforge.net>
Subject: Re: [stable] [PATCH 1/14] uml: fix build when SLOB is enabled

On Fri, Aug 01, 2008 at 04:06:24PM -0700, Greg KH wrote:
> On Fri, Aug 01, 2008 at 06:41:25PM -0400, Jeff Dike wrote:
> > >From 94409ded7768e15b0d0a5a172d611073c72308de Mon Sep 17 00:00:00 2001
> 
> These git commit ids don't match up to anything in Linus's tree at all
> :(

Hmmm, OK I'll figure out where the commit ids came from.  I
cherry-picked them from 2.6.26 into 2.6.25.13, so I guess they got new
ids when I did that.

I'll resend with the original ids...

> Oh, in the future it is simple to get patches into the -stable tree
> automatically, just add:
> 	Cc: Stable <stable@...nel.org>
> to the signed-off-by: area of the patch.  When it goes into Linus's
> tree, it will be automatically sent to us for inclusion in the next
> -stable release.

Yeah, I'll do that in future, but it was a little late for these
patches.

				Jeff

-- 
Work email - jdike at linux dot intel dot com
--
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/