linux-kernel - Re: [PATCH v4 0/5] x86: Cleanup and simplify cpu-specific data

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAELBVzAPHfnZWRTU82V3yHuW9iY8SfAgDNmro1q4dpOvKTwnBg@mail.gmail.com>
Date:	Thu, 1 Mar 2012 09:06:55 -0400
From:	Kevin Winchester <kjwinchester@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Borislav Petkov <bp@...en8.de>,
	Randy Dunlap <rdunlap@...otime.net>,
	Nick Bowler <nbowler@...iptictech.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/5] x86: Cleanup and simplify cpu-specific data

On 28 February 2012 04:31, H. Peter Anvin <hpa@...or.com> wrote:
> Better yet, fix the problem...
>

It appears that some attempts have been made at fixing this problem already:

https://lkml.org/lkml/2011/7/6/6
https://lkml.org/lkml/2011/7/7/480

So perhaps I can just turn off that config setting for now.  I'm going
away for a few days, but I'll try to fix up the patch series next
week.


> Ingo Molnar <mingo@...e.hu> wrote:
>
>>
>>* H. Peter Anvin <hpa@...or.com> wrote:
>>
>>> >In function ‘copy_from_user’,
>>> >     inlined from ‘pktgen_if_write’ at net/core/pktgen.c:877:20:
>>>
>>>/home/kevin/linux/linux-2.6/arch/x86/include/asm/uaccess_32.h:211:26:
>>> >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
>>> >
>>> >On:
>>> >
>>> >gcc (GCC) 4.6.2 20120120 (prerelease)
>>> >
>>> >Is that my fault, or something else?
>>> >
>>> >Kevin
>>> >
>>>
>>> That comes from compiling with warnings as errors.  Not that someone
>>> shouldn't look at that kind of problem.
>>
>>Can probably be worked around by disabling:
>>
>>CONFIG_DEBUG_STRICT_USER_COPY_CHECKS
>>
--
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/