netdev - Re: [Intel-wired-lan] [PATCH iwl-net] idpf: cap maximum Rx buffer size

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251230232400.3515704-1-decot+git@google.com>
Date: Tue, 30 Dec 2025 15:23:46 -0800
From: David Decotigny <decot+git@...gle.com>
To: intel-wired-lan@...ts.osuosl.org
Cc: netdev@...r.kernel.org, Joshua Hay <joshua.a.hay@...el.com>, 
	Alexander Lobakin <aleksander.lobakin@...el.com>, Madhu Chittim <madhu.chittim@...el.com>, 
	David Decotigny <ddecotig@...gle.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net] idpf: cap maximum Rx buffer size

On 11/3/2025 1:20 PM, Joshua Hay wrote:
> The HW only supports a maximum Rx buffer size of 16K-128. On systems
> using large pages, the libeth logic can configure the buffer size to be
> larger than this. The upper bound is PAGE_SIZE while the lower bound is
> MTU rounded up to the nearest power of 2. For example, ARM systems with
> a 64K page size and an mtu of 9000 will set the Rx buffer size to 16K,
> which will cause the config Rx queues message to fail.
> 
> Initialize the bufq/fill queue buf_len field to the maximum supported
> size. This will trigger the libeth logic to cap the maximum Rx buffer
> size by reducing the upper bound.
> 
> Fixes: 74d1412ac8f37 ("idpf: use libeth Rx buffer management for payload buffer")
> Signed-off-by: Joshua Hay <joshua.a.hay@...el.com>
> Acked-by: Alexander Lobakin <aleksander.lobakin@...el.com>
> Reviewed-by: Madhu Chittim <madhu.chittim@...el.com>
> ---

Reviewed-by: David Decotigny <ddecotig@...gle.com>