linux-kernel - Re: Re-enabling non-GPL driver access to disk partition information

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: <4B699625.5040808@davidnewall.com>
Date:	Thu, 04 Feb 2010 01:58:37 +1030
From:	David Newall <davidn@...idnewall.com>
To:	Greg KH <greg@...ah.com>
CC:	Derek Atkins <warlord@....edu>, linux-kernel@...r.kernel.org
Subject: Re: Re-enabling non-GPL driver access to disk partition information

Greg KH wrote:
> On Sat, Jan 30, 2010 at 02:32:20PM +1030, David Newall wrote:
>   
>> Greg KH wrote:
>>     
>>> On Fri, Jan 29, 2010 at 09:15:09AM -0500, Derek Atkins wrote:
>>>   
>>>       
>>>> -EXPORT_SYMBOL_GPL(put_device);
>>>> +EXPORT_SYMBOL(put_device);
>>>>     
>>>>         
>>> No, sorry, [...] I can not, and will not, make this change.
>>>   
>>>       
>> Derek,
>>
>> Consider writing a GPL wrapper module.
>>     
>
> Ah, the old "GPL condom" try.  Sorry, but this has been tried many times
> in the past, and have been shut down every time.  See the Samba history
> of this for lots of details as to why this does not work.


Samba vs The Money merely shows that The Money failed to put up a 
sufficient defence. Good result for FOSS, but I recommend against you 
betting your home on it.

Anyway, I was thinking of something a little more substantial that what 
you perhaps read into my suggestion. There's usually a substantial gap 
between the pure needs of a driver and the facilities offered by an 
operating system. In the case in question, for example, the need is to 
count the number of partitions, and the facility offered is get_device, 
or something. A tiny GPL module that calls get_device and returns a 
count sounds eminently defensible.

In addition--and please keep in mind that I'm unfamiliar with the 
internals of the kernel--it seems to me there's an obvious similarity 
with USL vs BSD, alleging copyright for verbatim copying of macro 
constants, amongst other things. A lesson that learned then was that you 
can't prevent someone from using provided facilities necessary for use 
of the operating system. I don't know what put_device does, but I know 
what it sounds like; it sounds like it's something that you have to use, 
and so one can use it, even in proprietary code. I imagine this idea 
will irritate those who put in the hard yards, but FOSS has to play by 
the same rules as the monied end of town. You might want to think about 
this carefully, because if it's taken all the way through court and the 
GPL-only claim rejected, there may well be a run-on effect on all of the 
symbols marked GPL-only. Those who want to thwart proprietary kernel 
modules may find it prudent to generously give up this symbol rather 
than risking the lot.
--
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/