netdev - Re: [PATCH net-next 05/15] net: page

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]

Date: Tue, 24 Oct 2023 13:19:35 -0600
From: David Ahern <dsahern@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 pabeni@...hat.com, almasrymina@...gle.com, hawk@...nel.org,
 ilias.apalodimas@...aro.org
Subject: Re: [PATCH net-next 05/15] net: page_pool: record pools per netdev

On 10/24/23 11:49 AM, Jakub Kicinski wrote:
> On Tue, 24 Oct 2023 11:31:46 -0600 David Ahern wrote:
>> On 10/24/23 10:02 AM, Jakub Kicinski wrote:
>>> Link the page pools with netdevs. This needs to be netns compatible
>>> so we have two options. Either we record the pools per netns and
>>> have to worry about moving them as the netdev gets moved.
>>> Or we record them directly on the netdev so they move with the netdev
>>> without any extra work.
>>>
>>> Implement the latter option. Since pools may outlast netdev we need
>>> a place to store orphans. In time honored tradition use loopback
>>> for this purpose.
>>
>> blackhole_netdev might be a better choice than loopback
> 
> With loopback we still keep it per netns, and still accessible 
> via netlink.

and if the namespace and loopback device get deleted?