[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20211209120343.3a6de4f5@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Thu, 9 Dec 2021 12:03:43 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: "David S . Miller" <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>
Subject: Re: [PATCH net-next 00/17] net: netns refcount tracking series
On Mon, 6 Dec 2021 16:51:25 -0800 Eric Dumazet wrote:
> We have 100+ syzbot reports about netns being dismantled too soon,
> still unresolved as of today.
>
> We think a missing get_net() or an extra put_net() is the root cause.
>
> In order to find the bug(s), and be able to spot future ones,
> this patch adds CONFIG_NET_NS_REFCNT_TRACKER and new helpers
> to precisely pair all put_net() with corresponding get_net().
>
> To use these helpers, each data structure owning a refcount
> should also use a "netns_tracker" to pair the get() and put().
>
> Small sections of codes where the get()/put() are in sight
> do not need to have a tracker, because they are short lived,
> but in theory it is also possible to declare an on-stack tracker.
Ugh, I realized after a week of waiting that vfs / sunrpc / audit folks
are not even CCed here. I think we should give them the courtesy of
being able to ack the patches.. Can you split out 1-4,6,7 for immediate
merging and repost the rest with the right CCs?
Powered by blists - more mailing lists