On Tue, 2007-11-27 at 15:49 +1100, Rusty Russell wrote:With my "Enterprise" hat on, I can see where Andi was coming from originally. Just like we do in RHEL, SuSE have a concept of a kernel ABI and we too have a concept of a whitelist of symbols - a subset of kernel ABI that is approved for use by third parties (this is nothing to do with licensing, this is to do with ABI stability we try to ensure). As part of figuring out what should and should not be used by external modules (outside of the core kernel), we've gained a bit of experience, and it would be nice to be able to help others - this is nothing to do with upstream "ABI stability", but just to be of a public service by documenting those functions that are never intended for modules but which necessarily are exported because they have one or two users. I suggested this exact idea privately at OLS. I still think it's the best compromise, though I like bits of the namespace idea. An EXPORT_SYMBOL_INTERNAL would indeed be trivial. Jon. -
| H. Peter Anvin | Re: [rft] s2ram wakeup moves to .c, could fix few machines |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Ingo Molnar | [patch] PID namespace design bug, workaround |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| Eric Dumazet | Re: Multicast packet loss |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
