linux-kernel - Re: [PATCH v2 03/13] backports: allow for different backport prefix

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]

Date:	Thu, 6 Nov 2014 00:09:07 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	"Luis R. Rodriguez" <mcgrof@...e.com>
Cc:	Johannes Berg <johannes@...solutions.net>, andi@...stfloor.org,
	"Luis R. Rodriguez" <mcgrof@...not-panic.com>,
	backports@...r.kernel.org, linux-kernel@...r.kernel.org,
	yann.morin.1998@...e.fr, mmarek@...e.cz, sassmann@...nic.de
Subject: Re: [PATCH v2 03/13] backports: allow for different backport prefix

> You know, this use case seems unavoidable so I'll just proceed with the
> configurability of it. But note that it seems we're both in agreement
> that right now what you described requires more work before in any way
> shape or form folks start using it for the exact purpose you described.
> I also think Andi Kleen's module namespace might be a much better solution to
> that problem [0], we'd just have to carry the code ourselves as I am not

Just to clarify. My name spaces didn't really provide different
name spaces (like C++), it just added a ACL to exports to make it possible
to do "export only to module N". But the name space itself
was still flat

On the linker side doing real name spaces is probably not too hard,
but it would be difficult for linked in code without special linker
support.

> sure if this is ever going to get upstream as it was originally nacked.

May need to revisit that.

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