[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071203.101346.261427003.davem@davemloft.net>
Date: Mon, 03 Dec 2007 10:13:46 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: ebiederm@...ssion.com
Cc: romanol@...omillas.es, lkml@....ca,
shemminger@...ux-foundation.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, containers@...ts.osdl.org
Subject: Re: namespace support requires network modules to say "GPL"
From: ebiederm@...ssion.com (Eric W. Biederman)
Date: Mon, 03 Dec 2007 11:03:38 -0700
> Based on my experience with in-tree code and the few glimpses I
> have gotten of out of tree code the reason the out of tree code broke
> is because it is doing very questionable things.
Calling dev_get_by_foo() was never ever a very questionable thing.
Stop saying bullshit, because that's all that is coming out of your
mouth in this thread.
The fact is, these modules called perfectly fine interfaces and by
adding namespaces YOU BROKE THEM.
That by itself is OK, they can make the code changes to adapt and use
the init namespace.
Enforcing new licensing restrictions on them for existing interfaces
just because you add a new freaking argument that is practically
speaking a constant and always the same right now, on the other hand,
IS NOT FINE and you must fix this now.
I don't care how you do it.
If you don't want them to get at the init namespace symbol, fine,
revert all the dev_get_by_*() interfaces to not take the namespace
symbol and make them internally use the init namespace albeit
invisibly to the caller.
Then you make all the existing call sites invoke new dev_get_by_*_ns()
interfaces that take an explicit argument. But only do this where it
is truly necessary, everything uses the init namespace practically
speaking and it's clearer if you conver to the *_ns() variant when the
code itself is converted.
--
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