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  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:	Mon, 27 Feb 2012 20:52:55 -0400
From:	Kevin Winchester <>
To:	Ingo Molnar <>
Cc:	"H. Peter Anvin" <>,
	Thomas Gleixner <>,
	Borislav Petkov <>,
	Randy Dunlap <>,
	Nick Bowler <>,
Subject: Re: [PATCH v4 0/5] x86: Cleanup and simplify cpu-specific data

On 27 February 2012 07:59, Ingo Molnar <> wrote:
> * Kevin Winchester <> wrote:
>> Various per-cpu fields are define in arch/x86/kernel/smpboot.c
>> that are basically equivalent to the cpu-specific data in
>> struct cpuinfo_x86. By moving these fields into the structure,
>> a number of codepaths can be simplified since they no longer
>> need to care about those fields not existing on !SMP builds.
> Works mostly fine, except with the attached 32-bit UP !APIC
> config I get various build failures (resolved via the patch
> below) and a link failure (not resolved):

I get the following failure before I get to link time:

In file included from
                 from include/linux/irq.h:357,
                 from include/linux/hardirq.h:7,
                 from include/linux/interrupt.h:12,
                 from net/core/pktgen.c:135:
In function ‘copy_from_user’,
    inlined from ‘pktgen_if_write’ at net/core/pktgen.c:877:20:
error: call to ‘copy_from_user_overflow’ declared with attribute
error: copy_from_user() buffer size is not provably correct
make[2]: *** [net/core/pktgen.o] Error 1


gcc (GCC) 4.6.2 20120120 (prerelease)

Is that my fault, or something else?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists