All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] __ipipe_root_status exported GPL only but used to be not GPL only and is breaking other code
Date: Wed, 10 Dec 2014 20:12:28 +0100	[thread overview]
Message-ID: <20141210191228.GS1524@hermes.click-hack.org> (raw)
In-Reply-To: <20141210190939.GD24110@csclub.uwaterloo.ca>

On Wed, Dec 10, 2014 at 02:09:39PM -0500, Lennart Sorensen wrote:
> On Wed, Dec 10, 2014 at 08:05:09PM +0100, Gilles Chanteperdrix wrote:
> > Ah, you mean the problem is with a module which does not use Xenomai
> > ? That is unfortunate.
> 
> Yes, and only becasue ipipe messes with the task structures in some way
> and the change in the export of that symbol is causing the problem.
> 
> Certainly the mainline kernel does not allow existing calls to get broken
> by other changes.  Perhaps ipipe should follow the same rule and revert
> the change to that symbol.

The I-pipe messing with task_struct is not involved here. Using
EXPORT_SYMBOL_GPL instead of EXPORT_SYMBOL is what causes the kernel
to refuse loading a module not using the GPL license trying to use
that symbol. That is the purpose of EXPORT_SYMBOL_GPL.

Using EXPORT_SYMBOL_GPL is done by a lot of modules which "follow
the rules", I-pipe included.

-- 
					    Gilles.


  parent reply	other threads:[~2014-12-10 19:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 18:37 [Xenomai] __ipipe_root_status exported GPL only but used to be not GPL only and is breaking other code Lennart Sorensen
2014-12-10 18:42 ` Gilles Chanteperdrix
2014-12-10 19:02   ` Lennart Sorensen
2014-12-10 19:04     ` Lennart Sorensen
2014-12-10 19:05     ` Gilles Chanteperdrix
2014-12-10 19:09       ` Lennart Sorensen
2014-12-10 19:11         ` Lennart Sorensen
2014-12-10 19:12         ` Gilles Chanteperdrix [this message]
2014-12-10 19:13         ` Gilles Chanteperdrix
2014-12-10 19:19           ` Lennart Sorensen
2014-12-10 19:24             ` Gilles Chanteperdrix
2014-12-10 19:39               ` Lennart Sorensen
2014-12-10 19:47                 ` Gilles Chanteperdrix
2014-12-10 19:55                   ` Lennart Sorensen
2014-12-10 19:59                     ` Gilles Chanteperdrix
2014-12-10 20:05                     ` Lennart Sorensen
2014-12-10 19:44             ` Gilles Chanteperdrix
2014-12-10 19:52               ` Lennart Sorensen
2014-12-10 19:57                 ` Gilles Chanteperdrix
2014-12-10 20:12                   ` Lennart Sorensen
2014-12-10 19:45             ` Philippe Gerum
2014-12-10 19:44               ` Lennart Sorensen
2014-12-10 20:13                 ` Philippe Gerum
2014-12-10 20:11                   ` Lennart Sorensen
2014-12-10 20:38                     ` Philippe Gerum
2014-12-10 21:16                       ` Lennart Sorensen
2014-12-10 21:23                     ` Lennart Sorensen
2014-12-10 21:55                       ` Jeff Webb
2014-12-10 22:01                         ` Lennart Sorensen
2014-12-10 23:18                           ` Jeff Webb
2014-12-10 20:53                   ` Jeff Webb
2014-12-10 21:58                     ` Gilles Chanteperdrix
2014-12-22 10:06                   ` Jan Kiszka
2014-12-22 11:19                     ` Philippe Gerum
2014-12-22 14:46                       ` Lennart Sorensen
2014-12-22 15:00                         ` Philippe Gerum
2014-12-22 19:08                           ` Lennart Sorensen
2014-12-22 14:42                     ` Lennart Sorensen
2014-12-22 14:44                       ` Jan Kiszka

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=20141210191228.GS1524@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=xenomai@xenomai.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.