[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL4WiipFY_YKMGbtEmYq0M=18yCEvLoGvXRSgui4+-NJR-ReiA@mail.gmail.com>
Date: Wed, 17 Nov 2021 11:13:03 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: [RFC net-next 1/2] net: add netdev_refs debug
On Wed, Nov 17, 2021 at 9:47 AM Jakub Kicinski <kuba@...nel.org> wrote:
>
> Debugging netdev ref leaks is still pretty hard. Eric added
> optional use of a normal refcount which is useful for tracking
> abuse of existing users.
>
> For new code, however, it'd be great if we could actually track
> the refs per-user. Allowing us to detect leaks where they happen.
> This patch introduces a netdev_ref type and uses the debug_objects
> infra to track refs being lost or misused.
>
> In the future we can extend this structure to also catch those
> who fail to release the ref on unregistering notification.
>
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
> ---
Interesting, I was working on something very different, let me send
the RFC (it is absolutely not complete at this point)
Powered by blists - more mailing lists