linux-kernel - Re: [RFC PATCH 0/7] x86/entry: Create a home for the x86 entry code in arch/x86/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: <20150603172146.GA16278@gmail.com>
Date:	Wed, 3 Jun 2015 19:21:47 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Brian Gerst <brgerst@...il.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Borislav Petkov <bp@...en8.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC PATCH 0/7] x86/entry: Create a home for the x86 entry code
 in arch/x86/entry/


* Ingo Molnar <mingo@...nel.org> wrote:

> 
> * Andy Lutomirski <luto@...capital.net> wrote:
> 
> > On Wed, Jun 3, 2015 at 10:11 AM, Ingo Molnar <mingo@...nel.org> wrote:
> > >
> > > * H. Peter Anvin <hpa@...or.com> wrote:
> > >
> > >> I like the patch set (and you can add my Acked-by:) *except* 7/7, and the reason
> > >> for that is that it really isn't entry code, it is user space code.
> > >
> > > Well, I think arch/x86/entry/ should be a broader category for all things entry
> > > code: and the vsyscall code is closely related to the syscall entry/exit code so
> > > it's in a better place there than just being in the generic arch/x86/kernel/
> > > directory.
> > >
> > > I kept it separate in arch/x86/entry/vsyscall/ so it doesn't mix with other entry
> > > code.
> > 
> > ...and my reading comprehension is way off this morning.  You already called it 
> > arch/x86/entry, so there was no reason for me to suggest that :)
> > 
> > Anyway, arch/x86/entry/vdso isn't so bad.  It's just a bit odd sounding to me.
> 
> We could make it arch/x86/sys/? Sounds a bit too generic though.
> 
> Didn't want to limit it to system calls only, because there's various other 
> entry methods (irqs, traps, NMI, etc.) that we want to handle in a coherent 
> fashion. [ Which you are intimately aware of ;-) ]

Another tweak would be to move the kernel side entry code into 
arch/x86/entry/system/ or so, to create the following organization:

    arch/x86/entry:            all things entry methods

    arch/x86/entry/system/:    system/kernel mode entry code
    arch/x86/entry/vdso/:      user mode entry code
    arch/x86/entry/vsyscall/:  [legacy vsyscall entry code]

    arch/x86/entry/syscalls/:  build-time syscall table generation code

My primary goal is to have them all close to each other, so that we can have 
better structure, more coherency and easier overview. The names are negotiable, 
the concept is not ;-)

Thanks,

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