From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, edumazet@google.com, f6bvp@free.fr,
duoming@zju.edu.cn
Subject: Re: [PATCH net] ax25: fix incorrect dev_tracker usage
Date: Fri, 29 Jul 2022 05:30:13 +0000 [thread overview]
Message-ID: <165907261360.17632.6329795270179343317.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220728051821.3160118-1-eric.dumazet@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 Jul 2022 22:18:21 -0700 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> While investigating a separate rose issue [1], and enabling
> CONFIG_NET_DEV_REFCNT_TRACKER=y, Bernard reported an orthogonal ax25 issue [2]
>
> An ax25_dev can be used by one (or many) struct ax25_cb.
> We thus need different dev_tracker, one per struct ax25_cb.
>
> [...]
Here is the summary with links:
- [net] ax25: fix incorrect dev_tracker usage
https://git.kernel.org/netdev/net/c/d7c4c9e075f8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-07-29 5:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 5:18 [PATCH net] ax25: fix incorrect dev_tracker usage Eric Dumazet
2022-07-29 5:30 ` patchwork-bot+netdevbpf [this message]
2022-07-29 17:32 ` Matthieu Baerts
2022-08-03 6:23 ` Paolo Abeni
2022-08-03 6:46 ` Eric Dumazet
2022-08-03 7:03 ` Paolo Abeni
2022-08-03 7:15 ` Eric Dumazet
2022-09-03 8:56 ` Bernard Pidoux
2022-09-03 16:47 ` Eric Dumazet
2022-09-04 10:37 ` [AX25] [ROSE] refcount_t: decrement hit 0; leaking memory Bernard Pidoux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=165907261360.17632.6329795270179343317.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=f6bvp@free.fr \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).