| 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
| ||
|
Date: Fri, 2 Dec 2011 09:42:13 +0100 From: Alessandro Rubini <rubini@...dd.com> To: rusty@...abs.org Cc: greg@...ah.com, linux-kernel@...r.kernel.org, siglesia@...n.ch, manohar.vanga@...n.ch, dave.martin@...aro.org Subject: Re: [RFC PATCH V2 0/1] making order in file2alias > But splitting 15-line functions into separate files? Less compact, less > simple. Personally, I'm more interested in the addition of new busses (as drop-in files) than the split up of current ones. But I see your point. >> > step 1: create the ELF section so ENTRY() lines can leave the array >> > (and change name accordingly). >> > >> > step 2: each ENTRY() line can be moved just after the associated code >> > (this means that a new bus is just a single hunk, not 2 of them) >> > >> > step 3: I create the headers needed to move code and ENTRY in separate >> > files. This is some movement around, not trivial so it may >> > deserve a patch in itself. > If you *really* want to use separate files, then this patch will let you > do it. You'll need to expose some stuff in a header though. Fine with me. This is 1 and 2 of my list above. And the "need to expose" is my step 3. So I agree with this. thanks /alessandro -- 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/
Powered by blists - more mailing lists