netdev - Re: [PATCH net-next v4 0/2] Handle alternate miss-completions

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: <Y3YWnS1ZEY8ocXCQ@unreal>
Date:   Thu, 17 Nov 2022 13:10:21 +0200
From:   Leon Romanovsky <leon@...nel.org>
To:     Jeroen de Borst <jeroendb@...gle.com>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
        jesse.brandeburg@...el.com
Subject: Re: [PATCH net-next v4 0/2] Handle alternate miss-completions

On Wed, Nov 16, 2022 at 10:17:23AM -0800, Jeroen de Borst wrote:
> Some versions of the virtual NIC present miss-completions in
> an alternative way. Let the diver handle these alternate completions
> and announce this capability to the device.
> 
> The capability is announced uing a new AdminQ command that sends
> driver information to the device. The device can refuse a driver
> if it is lacking support for a capability, or it can adopt it's
> behavior to work around it.
> 
> Changed in v4:
> - Clarified new AdminQ command in cover letter
> - Changed EOPNOTSUPP to ENOTSUPP to match device's response

If you rely on the error code, please use the correct one and
fix the driver to use EOPNOTSUPP and not ENOTSUPP.

Thanks