linux-kernel - Re: wish: build time warning for missing MODULE

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: <20080401074311.GE23259@cs181133002.pp.htv.fi>
Date:	Tue, 1 Apr 2008 10:43:11 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Dave Jones <davej@...emonkey.org.uk>,
	Sam Ravnborg <sam@...nborg.org>, rusty@...tcorp.com.au,
	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: wish: build time warning for missing MODULE_LICENSE

On Mon, Mar 31, 2008 at 10:22:48PM -0400, Dave Jones wrote:
> On Sun, Mar 30, 2008 at 11:34:17PM +0300, Adrian Bunk wrote:
>  > On Sun, Mar 30, 2008 at 09:04:30PM +0200, Sam Ravnborg wrote:
>  > > On Sun, Mar 30, 2008 at 09:01:19PM +0300, Adrian Bunk wrote:
>  > > > I just fixed a bug where I had accidentally removed a MODULE_LICENSE() 
>  > > > from a file.
>  > > > 
>  > > > The problem is that such bugs are currently not discovered until someone 
>  > > > actually runs a kernel with this module loaded.
>  > > > 
>  > > > Could we get a build time warning/error for a missing MODULE_LICENSE?
>  > > 
>  > > Is it something as simple as this you are after?
>  > > [My dev box is dead atm so I have not done a kernel build
>  > > with this, only a single module].
>  > 
>  > Thanks, it seems to work - and I'm currently working on fixing the bugs 
>  > it catches.
>  > 
>  > Considering that these are trivial to fix I'd even suggest a fatal() 
>  > instead of the warn() for making them obvious for everyone doing build 
>  > testing.
>  
> In the Fedora kernel specfile, we have something to catch this at build time.
> Relevant pieces are (munged a bit for clarity) ..
> 
>     find . -name "*.ko" -type f >modnames
> 
>     while read i
>     do
>       echo -n "$i " >> modinfo
>       /sbin/modinfo -l $i >> modinfo
>     done < modnames
> 
>     egrep -v \
>           'GPL( v2)?$|Dual BSD/GPL$|Dual MPL/GPL$|GPL and additional rights$' \
>           modinfo && exit 1

I'd say the price for the most elegant solution goes to Sam.  ;)

> This hasn't been triggering though, so either it stopped working at some point,
> or we don't build the module you mention.  Which was it out of curiosity ?
> Or was your slip-up an -mm only thing?

My slip-up was the OSS ac97_codec in 2.6.25-rc.

The other ones I found until now are:
arch/x86/video/fbdev.c
drivers/ide/ide-pnp.c (bug introduced in 2.6.25-rc)
drivers/ide/pci/cmd640.c (bug introduced in 2.6.25-rc)
drivers/ide/ppc/mpc8xx.c (bug introduced in 2.6.25-rc)
drivers/ide/ppc/pmac.c (bug introduced in 2.6.25-rc)
drivers/ide/arm/ide_arm.c (bug introduced in 2.6.25-rc)
drivers/ide/cris/ide-cris.c (bug introduced in 2.6.25-rc)
drivers/ide/h8300/ide-h8300.c (bug introduced in 2.6.25-rc)
drivers/ide/legacy/gayle.c (bug introduced in 2.6.25-rc)
drivers/ide/legacy/buddha.c (bug introduced in 2.6.25-rc)
drivers/ide/legacy/falconide.c (bug introduced in 2.6.25-rc)
drivers/ide/legacy/macide.c (bug introduced in 2.6.25-rc)
drivers/ide/legacy/q40ide.c (bug introduced in 2.6.25-rc)
drivers/media/video/v4l2-int-device.c (bug introduced in 2.6.25-rc)
arch/arm/kernel/arthur.c

Most likely none of them is modular in the Fedora kernel and/or 
available on the architectures Fedora supports.

> 	Dave

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
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/