netdev - Re: SO_RESERVE_MEM doesn't quite work, at least on UDP

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: <396f9c38e2e2a14120e629cbc13353ec0aa15a62.camel@redhat.com>
Date: Fri, 16 Feb 2024 09:11:19 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Andy Lutomirski <luto@...capital.net>, Wei Wang <weiwan@...gle.com>, 
 Network Development <netdev@...r.kernel.org>, Eric Dumazet
 <edumazet@...gle.com>, "David S. Miller" <davem@...emloft.net>
Subject: Re: SO_RESERVE_MEM doesn't quite work, at least on UDP

On Thu, 2024-02-15 at 13:17 -0800, Andy Lutomirski wrote:
> With SO_RESERVE_MEM, I can reserve memory, and it gets credited to
> sk_forward_alloc.  But, as far as I can tell, nothing keeps it from
> getting "reclaimed" (i.e. un-credited from sk_forward_alloc and
> uncharged).  So, for UDP at least, it basically doesn't work.

SO_RESERVE_MEM is basically not implemented (yet) for UDP. Patches are
welcome - even if I would be curious about the use-case.

Thanks,

Paolo