linux-kernel - Re: [PATCH] x86: used used_vectors in init

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: <20090415194705.GA8290@elte.hu>
Date:	Wed, 15 Apr 2009 21:47:05 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Joerg Roedel <joerg.roedel@....com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	stable@...nel.org, Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [PATCH] x86: used used_vectors in init_IRQ


* Yinghai Lu <yinghai@...nel.org> wrote:

> Ingo Molnar wrote:
> > * Yinghai Lu <yinghai@...nel.org> wrote:
> > 
> >> Ingo Molnar wrote:
> >>
> >>> Note, i removed the -stable tag because i dont think .29 nor 
> >>> .30-rc2 is affected. Your patch to irqinit*.c (and the later 
> >>> unification by Pekka) is something still pending in the 
> >>> perfcounters and x86 trees, queued for .31.
> >> not sure .29, but it seems we need this for 2.6.30
> >>
> 
> you are right...
> 
> in trap_init with linus tree
> 
> still have
> #ifdef CONFIG_X86_64
>         set_bit(IA32_SYSCALL_VECTOR, used_vectors);
> #else
>         set_bit(SYSCALL_VECTOR, used_vectors);
> #endif
> 
> 
> so one patch (merge irqinit_32/64) in tip for .31 expose that bug.
> 
> aka we don't back port ...

ok, good!

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