linux-kernel - Re: [PATCH] x86: fix lguest used

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]

Date:	Fri, 19 Dec 2008 14:34:33 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Rusty Russell <rusty@...tcorp.com.au>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: fix lguest used_vectors breakage

Ingo Molnar wrote:
> * Yinghai Lu <yinghai@...nel.org> wrote:
> 
>> Impact: fix and clean up
> 
> i tidied the changelog up - see it attached further below. Also Cc:-ed 
> Rusty as the motivation is to fix and standardize lguest's irq vector 
> allocation method.
> 
> One small detail, we'll need a -v2:
> 
>  In file included from 
>  /home/mingo/linux/linux/arch/x86/include/asm/elf.h:90,
>                  from include/linux/elf.h:8,
>                  from include/linux/module.h:15,
>                  from include/linux/crypto.h:22,
>                  from arch/x86/kernel/asm-offsets_32.c:8,
>                  from arch/x86/kernel/asm-offsets.c:3:
>  /home/mingo/linux/linux/arch/x86/include/asm/desc.h:324: error: 'NR_VECTORS' undeclared here (not in a function)
> 
> config attached. Please pick up the changelog (and subject line) below 
> when you iterate the patch. Thanks,

where is config?

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