netdev - Re: [PATCH 2/7] CAN: Add PF

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]

Date:	Fri, 28 Sep 2007 22:28:18 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	David Miller <davem@...emloft.net>
Cc:	urs@...ogud.escape.de, shemminger@...ux-foundation.org,
	netdev@...r.kernel.org, kaber@...sh.net, joe@...ches.com,
	oliver@...tkopp.net, oliver.hartkopp@...kswagen.de
Subject: Re: [PATCH 2/7] CAN: Add PF_CAN core module

On Fri, 2007-09-28 at 13:20 -0700, David Miller wrote:
> That's not true with CAN.
> 
> With this CAN stuff, any driver you write for it is intimately
> integrated into the design and architecture of the CAN subsystem.  Any
> such driver cannot stand on it's own.  Look at how these drivers can
> get into the internals.

I'm just concerned about protocols, which have been designed and
implemented long ago outside of the kernel and are going to be wrapped
with glue code to fit into the socket can implementation. That's hard to
judge.

> If this code goes in without the _GPL() exports, that's fine, but it's
> setting incorrect expectations for people who think they can write
> binary-only drivers and link to these symbols.
> 
> And it will be the CAN folks who are guilty of setting these
> false premises.  Especially after I've explicitly warned about
> it here.

Fair enough.

	tglx


-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html