Posix ACL on non-GPL modules.
Dear Sirs,
Every Posix ACL-related symbol is currently exported also for non-GPL modules.
But the quite important function "posix_acl_release", declared inline in include/linux/posix_acl.h, uses the GPL-only symbol "kfree_call_rcu". So Posix ACL-related functionalities can't be used from non-GPL modules. Can someone please clarify this situation? It seems an unwanted side-effect. Small example pasted at the end of this message.
If this is effectively unwanted and a fix gets pulled by Linus, can someone recommend a workaround for older kernels?
Thank you,
Massimo Maggi
PS:I'm interested in using Posix ACL functions from code in another Open Source Initiative-approved license, NOT in proprietary closed-source code.
Building this module:
#include <linux/module.h>
#include <linux/fs.h>
#include <linux/posix_acl.h>
MODULE_LICENSE("CDDL");
static int __init startup(void)
{
struct posix_acl *a = posix_acl_alloc(1,0);
//DO SOMETHING POTENTIALLY USEFUL
posix_acl_release(a);
return 0;
}module_init(startup);
Leads to this error:
FATAL: modpost: GPL-incompatible module testmodule.ko uses GPL-only symbol 'kfree_call_rcu'
Quoted 2 lines · Massimo Maggi
PS:I'm interested in using Posix ACL functions from code in another Open Source Initiative-approved license, NOT in proprietary closed-source code.
That doens't really matter. It's still a derived work of the Linux kernel if you write to Linux filesystem APIs, and it still won't be distributable. If you want to hack on it privately anyway you're of course more than free to do so, but you should not expect help. Not that'd you'd need it as you can hack anything you want into your private non-redistributed tree.
Without sounding mean, but please go away with your attempts to bypas the license we put on the code and vilationg our copyrights.
Quoted 1 line · Christoph Hellwig
attempts to bypas the license we put on the code and vilationg our copyrights.
I seriously appreciate the clear description of what you were thinking
when reading my message.
I will also be clear: My intention is to fully respect developer's
decisions to protect APIs and (obviously) respect laws.
Original author's decision in this regard is clear:
posix_acl_init,posix_acl_alloc,posix_acl_valid,posix_acl_equiv_mode,posix_acl_from_mode,posix_acl_chmod, posix_acl_create are explicitly exported for modules with _ANY_ license.
Therefore I'm authorized to use them in a CDDL-licensed module.
There is one function, posix_acl_release, whose use is clearly related
to posix_acl_alloc, which does not have a clearly expressed export
policy, as it is an inline function written in a header file. Through
multiple macro expansions, it calls a GPL-only symbol. Being an inline
function, the linker won't allow that.
Do you agree with me that this is a quite weak to express the decision
to not allow the use of Posix ACL's functions in non-GPL modules?
This is the reason why I tought this might be an oversight.
If original authors think that Posix ACL APIs should not be used from
non-GPL modules, I suggest you to export also:posix_acl_initposix_acl_allocposix_acl_validposix_acl_equiv_modeposix_acl_from_modeposix_acl_chmodposix_acl_create
as GPL-only symbols. Currently, they are available to modules with any license. Your intent of protecting Filesystem APIs will be clear to anyone and will be respected without any more questions on this mailing list.
This is an inconsistency that IMHO should be fixed. Fixing it in a more liberal way or in a more strict way is up to the original authors. Sorry for the long message, but I felt misunderstood and wanted to make my point clear.
Regards,
Massimo Maggi
A message that is not in the archive (sent off-list or not yet received): CAOPrR7qkkBbYi2esgwbN3-OrkPeP=W9OG59ArUSqLf67ia8DSg@mail.gmail.com
Quoted 2 lines · Massimo Maggi
posix_acl_createare explicitly exported for modules with _ANY_ license. Therefore I'm authorized to use them in a CDDL-licensed module.
You're not. Read the GPL again.