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
| ||
|
Message-ID: <20221027142125.k27ns6yan4rmxmwo@skbuf> Date: Thu, 27 Oct 2022 14:21:26 +0000 From: Vladimir Oltean <vladimir.oltean@....com> To: Claudiu Manoil <claudiu.manoil@....com> CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v2 net] net: enetc: survive memory pressure without crashing On Thu, Oct 27, 2022 at 07:03:31AM +0000, Claudiu Manoil wrote: > How do you trigger this "extreme case of memory pressure" where no enetc buffer > can be allocated? Do you simulate it? As far as I understand, making dev_alloc_page() predictably fail in some particular spot is hard and probabilistic (but possible given enough tries). The reason I stubled upon this particularly bad handling of low memory in the enetc driver is because with AF_XDP zero-copy sockets, memory for RX buffers comes directly from user space, which may simply opt to not put any buffers in the fill queue (see "xdpsock --txonly" for example). The fix for the case where the buffers come from the kernel's page allocator is simply analogous to that. It would be shady to add this exact same patch only as part of the XSK work, when it's clear that existing code suffers from this problem too, even if it's not easy to trigger it.
Powered by blists - more mailing lists