linux-kernel - Re: [PATCH] x86,nmi: Fix section mismatch warnings on 32-bit

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: <4FCE44FC0200007800088524@nat28.tlf.novell.com>
Date:	Tue, 05 Jun 2012 16:42:20 +0100
From:	"Jan Beulich" <JBeulich@...e.com>
To:	"Don Zickus" <dzickus@...hat.com>
Cc:	<x86@...nel.org>, "LKML" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86,nmi: Fix section mismatch warnings on 32-bit

>>> On 05.06.12 at 16:47, Don Zickus <dzickus@...hat.com> wrote:
> On Tue, Jun 05, 2012 at 09:12:13AM +0100, Jan Beulich wrote:
>> So before applying a change like this, I'd really like to understand
>> the issue itself. Could you simply attach the nmi_selftest.o file
>> that you get without your patch here (and indicate which
>> upstream version or revision the corresponding source file was
>> from, to be able to re-construct what the compiler actually did)?
> 
> I could but it might be easier for you to re-create it on your end.
> Using gcc-4.4.4 on an x86_64 box and v3.5-rc1, I just set
> CONFIG_DEBUG_NMI_SELFTEST to 'y' and compile with
> 
> make ARCH=i386 O=out/i686
> 
> and it easily reproduces for me.

I don't think I have a plain 4.4.4 around anywhere, nor is it clear
whether you used a plain one (and how it was configured). For
tricky, highly version dependent things like this (where a compiler
bug also can't be excluded), having the _exact_ object file the
problem was seen with would be much easier than trying to hunt
down a compiler version that I can reproduce this with.

Jan

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