netdev - Re: [PATCH iwl-net v2] ice: Add support for devlink loopback param.

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: <20240528121658.0bb99e8e@kernel.org>
Date: Tue, 28 May 2024 12:16:58 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Wojciech Drewek <wojciech.drewek@...el.com>
Cc: netdev@...r.kernel.org, intel-wired-lan@...ts.osuosl.org,
 jiri@...nulli.us
Subject: Re: [PATCH iwl-net v2] ice: Add support for devlink loopback param.

On Tue, 28 May 2024 13:01:32 +0200 Wojciech Drewek wrote:
> Subject: [PATCH iwl-net v2] ice: Add support for devlink loopback param.

iwl-next, presumably

Param makes sense, although the name keeps giving me pause.
I expect "loopback" will control either port loopback or something 
like hairpin. Would "local-forwarding" not be a better name?
Not a big deal, I guess.

> +        ``enabled`` - loopback traffic is not allowed on port
> +
> +        ``disabled`` - loopback traffic is allowed on this port

The meaning seems inverted?