public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chow <davidchow@shaolinmicro.com>
To: linux-kernel@vger.kernel.org
Subject: dequeue_signal() in signal.c disabilities
Date: Mon, 22 Nov 2004 10:25:15 +0800	[thread overview]
Message-ID: <41A14E0B.3030608@shaolinmicro.com> (raw)

Is there any reason to explicitly export dequeue_signal() as GPL in
signal.c ? I am not sure it is done by accident or not, but it is
definitely not quite reasonable to do this while other symbols in the
same source file are using EXPORT_SYMBOL() instead of EXPORT_SYMBOL_GPL().

This causes disabilities with modules that are non pure GPL licensed,
this causes kernel threads or possibly other interrupts unable to be
handled properly. I've tried both BSD and LGPL which doesn't work. The
dequeue_signal() is essential to anyone who use sleeps with signals and
will force non-pure-GPL'ed modules unable to handle signals properly.
Can anyone fix this in the next release of the kernel or give me a
simple reponse? Thanks.

David



             reply	other threads:[~2004-11-22  2:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22  2:25 David Chow [this message]
2004-11-24 23:07 ` dequeue_signal() in signal.c disabilities Alan Cox

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=41A14E0B.3030608@shaolinmicro.com \
    --to=davidchow@shaolinmicro.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox