linux-kernel - Re: [PATCH] x86/asm/entry/64: Clean up entry

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: <559D4437.5040604@oracle.com>
Date:	Wed, 08 Jul 2015 11:39:35 -0400
From:	Sasha Levin <sasha.levin@...cle.com>
To:	Andy Lutomirski <luto@...capital.net>,
	Ingo Molnar <mingo@...nel.org>
CC:	Denys Vlasenko <dvlasenk@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Brian Gerst <brgerst@...il.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Borislav Petkov <bp@...en8.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86/asm/entry/64: Clean up entry_64.S

On 07/06/2015 02:39 PM, Andy Lutomirski wrote:
>> I can reproduce the difference now.  Give me a few minutes to see if I
>> > can figure out what's causing it.
> It's debug info.  If I strip the two .o files, the results are
> identical.  I think the differences are just line numbers.
> 
> Why would this matter?  Sasha, can you double-check that this patch
> really introduced the problem?

I wasn't sure that that patch is causing the problem to begin with, I just
singled it out because I saw it generated changes and git blame pointed
to it wrt to modified lines.

I wasn't able to reproduce that issue again, I'll update when/if I do.


Thanks,
Sasha
--
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/