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]
Date: Fri, 3 Nov 2023 15:03:14 +0100
From: Alexander Lobakin <>
To: Larysa Zaremba <>
CC: <>, <>, Alexei Starovoitov
	<>, Daniel Borkmann <>, "David S. Miller"
	<>, Jakub Kicinski <>, "Jesper Dangaard
 Brouer" <>, Eric Dumazet <>, "Magnus
 Karlsson" <>, Willem de Bruijn
	<>, Yunsheng Lin <>,
	Maciej Fijalkowski <>, John Fastabend
Subject: Re: [PATCH bpf-next v2] net, xdp: allow metadata > 32

From: Larysa Zaremba <>
Date: Tue, 31 Oct 2023 18:57:37 +0100

It doesn't have "From: Alexa..." here, so that you'll be the author once
this is applied. Is this intended? ^.^

> 32 bytes may be not enough for some custom metadata. Relax the restriction,
> allow metadata larger than 32 bytes and make __skb_metadata_differs() work
> with bigger lengths.
> Now size of metadata is only limited by the fact it is stored as u8
> in skb_shared_info, so the upper limit is now is 255. Other important
> conditions, such as having enough space for xdp_frame building, are already
> checked in bpf_xdp_adjust_meta().



Powered by blists - more mailing lists