From: Anthony Liguori <aliguori@us.ibm.com>
To: Sidney Cammeresi <sac@cheesecake.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: Licensing conflict with OpenAFS kernel module
Date: Wed, 26 Apr 2006 10:38:45 -0500 [thread overview]
Message-ID: <444F9405.9010108@us.ibm.com> (raw)
In-Reply-To: <20060426153332.GA32624@cheesecake.org>
Sidney Cammeresi wrote:
> On Wed, 26 Apr 2006 at 10.27.42 -0500, Anthony Liguori wrote:
>
>> Sidney Cammeresi wrote:
>>
>>> I recently upgraded two Xen domU instances from 2.6.12.6 to 2.6.16.
>>> Because I am running the OpenAFS client on each of them, I took the
>>> opportunity to upgrade that (from 1.4.0 to 1.4.1) which required building
>>> a new kernel module. (The AFS client is partly in userspace and partly
>>> in the kernel.)
>>>
>>> Loading the new module failed:
>>>
>>> openafs: Unknown symbol force_evtchn_callback
>>> openafs: Unknown symbol xen_features
>>>
>> I think you should urge OpenAFS to relicense their module under the GPL.
>>
>
> Well this is not their decision given that the code came from IBM in
> the first place.
>
> I note, however, your ibm.com e-mail address. Do you perhaps know the
> channels in IBM to go through to discuss IBM relicensing their code under
> the GPL?
>
I'd suggest bringing this up within the OpenAFS community. If they are
making direct use of Xen-specific functions, then they can potentially
find a work around.
If we've made it so that a non-GPL symbol depends on one of our GPL'd
symbols, then that may be a problem on our part. I don't know whether
this is an acceptable thing to do. Sounds like an issue that needs to
be discussed on LKML.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2006-04-26 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 14:07 Licensing conflict with OpenAFS kernel module Sidney Cammeresi
2006-04-26 15:27 ` Anthony Liguori
2006-04-26 15:33 ` Sidney Cammeresi
2006-04-26 15:38 ` Anthony Liguori [this message]
2006-04-26 15:51 ` Sidney Cammeresi
2006-04-26 16:24 ` Keir Fraser
2006-04-26 16:29 ` Anthony Liguori
2006-04-26 16:40 ` Keir Fraser
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=444F9405.9010108@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=sac@cheesecake.org \
--cc=xen-devel@lists.xensource.com \
/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.