linux-kernel - Re: kernel/module.c warning re: non-GPL modules looks wrong

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070609162409.GB31493@uranus.ravnborg.org>
Date:	Sat, 9 Jun 2007 18:24:09 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: kernel/module.c warning re: non-GPL modules looks wrong

On Sat, Jun 09, 2007 at 05:25:08AM -0400, Robert P. J. Day wrote:
> 
>   from kernel/module.c:
> ...
>         ks = lookup_symbol(name, __start___ksymtab_gpl_future,
>                                  __stop___ksymtab_gpl_future);
>         if (ks) {
>                 if (!gplok) {
>                         printk(KERN_WARNING "Symbol %s is being used "
>                           "by a non-GPL module, which will not "
>                           "be allowed in the future\n", name);
>                         printk(KERN_WARNING "Please see the file "
>                           "Documentation/feature-removal-schedule.txt "
>                           "in the kernel source tree for more "
>                           "details.\n");
> ...
> 
>   but there's nothing in the feature removal file that expands on that
> issue.  (there *is* an entry regarding *unused* symbols, but that
> doesn't seem to address the above.)
EXPORT_GPL_FUTURE is used to mark _functionality_ as no longer available
after a grace period. So when one marks a set of symbols as GPL_FUTURE
that functionality ougt to be described in feature-removal.
Did you see any _functionaliy_ where GPL_FUTURE are used where it
is not warned in fetaure-removal that that _functionality_ are supposed
to be changed?

Or in other words - please be more specific.

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/