netdev - Re: Supporting out of tree custom vhost target modules

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: <ff6106ce-f0c9-4dc8-9e97-14c44b0b1036@lunn.ch>
Date: Wed, 23 Apr 2025 14:34:04 +0200
From: Andrew Lunn <andrew@...n.ch>
To: David George <dgeorgester@...il.com>
Cc: "Michael S. Tsirkin" <mst@...hat.com>, netdev@...r.kernel.org,
	jasowang@...hat.com
Subject: Re: Supporting out of tree custom vhost target modules

On Wed, Apr 23, 2025 at 12:48:59PM +0200, David George wrote:
> Thanks for the response Michael.
> 
> And apologies for the earlier html content.
> 
> > See no good reason for that, that header is there so modules outside
> > of vhost don't use it by mistake.
> 
> I suppose what I would really be suggesting is adding the possibility
> of a driver outside of vhost/ being able to include _something_,
> enough for it to implement its own vhost target.

Putting the header somewhere private is a design feature to stop the
internal API from being abused.

Now, you are creating an out of tree module, you can abuse anything
how you want, nobody cares. You can simply say your driver needs to be
built against the kernel sources, not just the includes, and you can
extend the include path to go deep into the tree.

	Andrew