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

Message-ID: <20250423083349-mutt-send-email-mst@kernel.org>
Date: Wed, 23 Apr 2025 08:34:26 -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 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. If you don't see this
> as being useful outside of my use, or my case too narrow, then I
> suppose there probably is no good reason.
> 
> Alternatively, what did you think of the suggestion of introducing a
> mechanism of a custom backend for vhost_net? In principal it could
> make the existing mechanism a little neater perhaps?
> 
> David

An out of tree module isn't a usecase I care about.
If you make the code neater, I'll be happy to accept the patch.

-- 
MST