linux-kernel - Re: [PATCH v2] [SCSI] scsi_dh: change scsi_dh_detach export to EXPORT

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]

Date:	Fri, 20 Apr 2012 21:41:20 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Mike Snitzer <snitzer@...hat.com>
Cc:	James.Bottomley@...senpartnership.com, linux-scsi@...r.kernel.org,
	Hannes Reinecke <hare@...e.de>,
	Chandra Seetharaman <sekharan@...ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] [SCSI] scsi_dh: change scsi_dh_detach export to
 EXPORT_SYMBOL

On Fri, 20 Apr 2012 13:34:05 -0400
Mike Snitzer <snitzer@...hat.com> wrote:

> Allow a proprietary non-GPL multipath driver, like EMC PowerPath, to
> detach a scsi_dh using scsi_dh_detach. 

That I doubt somehow. The GPL covers *all* derivative works.
EXPORT_SYMBOL doesn't magically make code non-derivative. If you need to
modify the kernel to make your driver work *and* you want to claim it is
not derivative then I hope there are good lawyers involved 8-)

The kernel is GPL, all derived works of a GPL codebase are required to be
GPL. There is no magic rule about modules. I've stated that repeatedly
for anything containing a line of code I own. GregKH has made it very
clear for his code, and so it goes on.

> End result is Linux and PowerPath can coexist without compromising
> Linux's default handling of multipath LUNs.

So your specific purpose seems to me to be to enable a third party piece
of non-free code to hook into a piece of GPL code that it needs (which to
me implies it is derivative if it does). There is an offence of
"conspiracy to commit copyright infringement" so merely grinning and
saying its for a third party doesn't let your company off the hook either.

You should probably forward it to your legal teams before taking any
other action. Deleting it won't make it go away. It's up to them to
decide if they think they can argue properly that the work is not
derivative. I shall be most intrigued to see anyone make that argument,
but hey I'm not a lawyer.

I'm dying to see anyone make the moral argument for it too.

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