linux-kernel - Re: MODULE_LICENSE("GPL") not working for me

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAO3ZPq0JU7854=AYR9a8SRcacUn1=7BhfCP=s93SJFTtmpuGSQ@mail.gmail.com>
Date:	Fri, 7 Oct 2011 17:36:22 -0700
From:	Stephen Williams <steveicarus@...il.com>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: MODULE_LICENSE("GPL") not working for me

I've attached the Makefile as I have it so far, and I've also attached the
output from make ... V=2. The Makefile is a canonical multi-object-file
module makefile, with some extra trappings for version stamping
and my source code management.

When I look at the object files, NONE of the generated *.o files contains
a .modinfo section, even though there are MODULE_LICENSE("GPL");
lines in the linux.c source file.

Incidentally, the source files in the ../libvidforio directory are generic,
so do not include any kernel header files.

On Fri, Oct 7, 2011 at 11:18 AM, Sam Ravnborg <sam@...nborg.org> wrote:
> On Fri, Oct 07, 2011 at 10:20:46AM -0700, Stephen Williams wrote:
>> On Thu, Oct 6, 2011 at 3:30 PM, Stephen Williams <steveicarus@...il.com> wrote:
>> > I have some large drivers for use in embedded arm systems, and
>> > I want them to be GPL, because I want to use some symbols exported
>> > as GPL, and also because I just wanna. But it is not working for
>> > me. I've attached my Makefile. I'm building from outside the kernel
>> > tree, but that should be OK. (right?) I'm using the following script to
>> > actually build:
>>
>> More information: I can see that the vidfor.o object file, indeed
>> none of my *.o files, have a .modinfo section. In other situations
>> where the licens stamp works, the .modinfo section is present.
>> I'm using the CodeSourcery build of the arm toolchain, and in
>> the simple cases (module that is a single source file) the
>> modinfo information works. Hmm...
>
> I lost the original mail...
> Could you try to post the output of make V=2 when you build your module
> and the Makefile fragment again.
>
>        Sam
>



-- 
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

Download attachment "make.out" of type "application/octet-stream" (2194 bytes)

Download attachment "Makefile" of type "application/octet-stream" (941 bytes)