netdev - Re: [PATCH net-next 06/20] net, ynl: Add peer info to queue-get response

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: <20250922183254.5990893d@kernel.org>
Date: Mon, 22 Sep 2025 18:32:54 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Daniel Borkmann <daniel@...earbox.net>
Cc: netdev@...r.kernel.org, bpf@...r.kernel.org, davem@...emloft.net,
 razor@...ckwall.org, pabeni@...hat.com, willemb@...gle.com,
 sdf@...ichev.me, john.fastabend@...il.com, martin.lau@...nel.org,
 jordan@...fe.io, maciej.fijalkowski@...el.com, magnus.karlsson@...el.com,
 David Wei <dw@...idwei.uk>
Subject: Re: [PATCH net-next 06/20] net, ynl: Add peer info to queue-get
 response

On Fri, 19 Sep 2025 23:31:39 +0200 Daniel Borkmann wrote:
> +    name: peer-info
> +    attributes:
> +      -
> +        name: id
> +        doc: Queue index of the netdevice to which the peer queue belongs.
> +        type: u32
> +      -
> +        name: ifindex
> +        doc: ifindex of the netdevice to which the peer queue belongs.
> +        type: u32

Oh, we have an ifindex in the local netns. So the API is to bind a
queue to one side of a netkit and then the other side of the netkit
actually gets to use it? Should we not be "binding" to the device that
is of interest rather than its peer?