All of lore.kernel.org
 help / color / mirror / Atom feed
From: Massimo Maggi <me@massimo-maggi.eu>
To: linux-fsdevel@vger.kernel.org
Subject: Posix ACL on non-GPL modules.
Date: Sat, 12 Oct 2013 01:30:35 +0200	[thread overview]
Message-ID: <52588A1B.3040407@massimo-maggi.eu> (raw)

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'

             reply	other threads:[~2013-10-11 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 23:30 Massimo Maggi [this message]
2013-10-12  8:14 ` Posix ACL on non-GPL modules Christoph Hellwig
2013-10-12 12:51   ` Massimo Maggi
     [not found]   ` <CAOPrR7qkkBbYi2esgwbN3-OrkPeP=W9OG59ArUSqLf67ia8DSg@mail.gmail.com>
2013-10-12 14:48     ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52588A1B.3040407@massimo-maggi.eu \
    --to=me@massimo-maggi.eu \
    --cc=linux-fsdevel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.