linux-kernel - Re: [RFC PATCH] Rename ia32entry.S to entry_64_compat

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]

Date:	Fri, 5 Jun 2015 15:37:14 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	linux-kernel@...r.kernel.org,
	Andy Lutomirski <luto@...capital.net>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Brian Gerst <brgerst@...il.com>,
	Peter Zijlstra <peterz@...radead.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC PATCH] Rename ia32entry.S to entry_64_compat_32.S

On Fri, Jun 05, 2015 at 03:00:29PM +0200, Ingo Molnar wrote:
> I'm wondering what people think about this naming scheme:
> 
>                   entry_32.S            # 32-bit binaries on 32-bit kernels
>                   entry_64.S            # 64-bit binaries on 64-bit kernels
>                   entry_64_compat_32.S  # 32-bit binaries on 64-bit kernels
> 
> Another option would be:
> 
>    arch/x86/entry/sys_32.S
>    arch/x86/entry/sys_64.S
>    arch/x86/entry/sys_64_compat.S

I like this one better because entry_64_compat_32 kinda has both bitness in
there and confuses me more.

Just my 2 ¢. :)

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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/