All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, mst@redhat.com
Cc: Sam Ravnborg <sam@uranus.ravnborg.org>
Subject: Re: Add missing module license tag to vring helpers.
Date: Tue, 07 May 2013 21:29:35 +0930	[thread overview]
Message-ID: <87li7rngpk.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130506134123.GA8092@redhat.com>

Dave Jones <davej@redhat.com> writes:
> On Mon, May 06, 2013 at 05:06:23PM +0930, Rusty Russell wrote:
>  > Dave Jones <davej@redhat.com> writes:
>  > > [  624.286653] vringh: module license 'unspecified' taints kernel.
>  > >
>  > > Signed-off-by: Dave Jones <davej@redhat.com>
>  > 
>  > Thanks!  This is exactly right.
>  > 
>  > But note that the default license tag for otherwise-unlabelled modules
>  > would be "GPLv2".  "GPL" means v2 or later (which is what I want, but
>  > it's not the kernel default).
>
> It would be good if we could somehow catch missing tags at build-time
> rather than have to run around fixing them after they get merged.

Hmm, modpost seems to have code to detect that... but it doesn't.
That's because there's not .modinfo section at all, so for some reason
it doesn't warn.

Sam put this check in a few years ago, with a fairly useless commit
message:

commit 2fa365682943866baf85305ef701741fe41b27e0
Author: Sam Ravnborg <sam@uranus.ravnborg.org>
Date:   Sat Apr 26 21:07:26 2008 +0200

    kbuild: soften MODULE_LICENSE check
    
    Only modules that has other MODULE_* content
    shall have the MODULE_LICENSE() tag.
    
    This fixes allmodconfig build on my box.
    
    Signed-off-by: Sam Ravnborg <sam@ravnborg.org>

Ripped that out, and fast forward a few hours later when I've done an
allmodconfig build; OK, now I'm confused.  Why do we hand
init/built-in.o to modpost?

        WARNING: modpost: missing MODULE_LICENSE() in init/built-in.o

There were some real problems found, too:

WARNING: modpost: missing MODULE_LICENSE() in drivers/acpi/acpi_i2c.o
see include/linux/module.h for more information
WARNING: modpost: missing MODULE_LICENSE() in drivers/mfd/cros_ec.o
see include/linux/module.h for more information
WARNING: modpost: missing MODULE_LICENSE() in drivers/mtd/nand/denali_pci.o
see include/linux/module.h for more information
WARNING: modpost: missing MODULE_LICENSE() in drivers/thermal/cpu_cooling.o
see include/linux/module.h for more information
WARNING: modpost: missing MODULE_LICENSE() in drivers/usb/phy/phy-samsung-usb.o
see include/linux/module.h for more information
WARNING: modpost: missing MODULE_LICENSE() in drivers/vhost/vringh.o
see include/linux/module.h for more information
WARNING: modpost: missing MODULE_LICENSE() in sound/soc/atmel/snd-soc-atmel-pcm.o
see include/linux/module.h for more information
WARNING: modpost: missing MODULE_LICENSE() in sound/soc/codecs/snd-soc-wm-adsp.o
see include/linux/module.h for more information

Confused,
Rusty.

      reply	other threads:[~2013-05-07 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 20:40 Add missing module license tag to vring helpers Dave Jones
2013-05-06  7:36 ` Rusty Russell
2013-05-06 13:41   ` Dave Jones
2013-05-07 11:59     ` Rusty Russell [this message]

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=87li7rngpk.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.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.