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

Message-ID: <20250423060040-mutt-send-email-mst@kernel.org>
Date: Wed, 23 Apr 2025 06:01:43 -0400
From: "Michael S. Tsirkin" <mst@...hat.com>
To: David George <dgeorgester@...il.com>
Cc: netdev@...r.kernel.org, jasowang@...hat.com
Subject: Re: Supporting out of tree custom vhost target modules

On Wed, Apr 23, 2025 at 11:47:49AM +0200, David George wrote:
> Hello all
> 
> I am in the process of writing an out of tree kernel module that does a very
> similar job to vhost_net.  The problem is that plain tap devices aren't quite
> going to cover what I want to do (1:N device mapping and various exotic
> offloads).
> 
> The approach I am taking at the moment is to tweak vhost/net.c to suit my needs
> and operate it as an out of tree module. The problem with this approach is the
> "vhost.h" is not in include/ so won't be usable without the whole source tree
> to compile against.
> 
> Is promoting vhost.h from drivers/vhost to include/xyz/ something that could be
> considered?
> 
> Alternatively, what I want to do could perhaps be done through an API to
> register a custom socket associated with a custom misc dev within vhost_net,
> but that is a lot more invasive.
> 
> Thanks,
> David George

See no good reason for that, that header is there so modules outside
of vhost don't use it by mistake.