linux-kernel - Re: [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on IA64 (try #3)

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: <44F431F5.7020703@sw.ru>
Date:	Tue, 29 Aug 2006 16:24:21 +0400
From:	Kirill Korotaev <dev@...ru>
To:	Greg KH <greg@...ah.com>
CC:	"Luck, Tony" <tony.luck@...el.com>,
	Fernando Vazquez <fernando@....ntt.co.jp>, gregkh@...e.de,
	akpm@...l.org, dev@...nvz.org, linux-ia64@...r.kernel.org,
	linux-kernel@...r.kernel.org, davem@...emloft.net,
	stable@...nel.org, kamezawa.hiroyu@...fujitsu.com, xemul@...nvz.org
Subject: Re: [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on IA64
 (try #3)

Greg KH wrote:
> On Mon, Aug 28, 2006 at 03:11:31PM -0700, Luck, Tony wrote:
> 
>>>The commit 8833ebaa3f4325820fe3338ccf6fae04f6669254 introduced a change that broke 
>>>IA64 compilation as shown below:
>>
>>What happened to the mainline version of the patch to which this
>>is a fix (local DoS with corrupted ELFs)?  I don't see it in 2.6.18-rc5.
>>Did it get fixed some other way, or is it just queued somewhere?  Or do
>>we have a fix in -stable that isn't in mainline?
> 
> 
> I thought this was a fix for a prior -stable patch that did not affect
> mainline.  Or was this thought wrong?
it should be passed to Linus.
Probably it is my fault, since I thought that patches which got into -stable
automatically go into Linus tree.

Thanks,
Kirill

-
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/