[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ffa2ea4f-dba9-5e44-95cb-4f4d3470884c@tessares.net>
Date: Fri, 29 Jul 2022 19:32:26 +0200
From: Matthieu Baerts <matthieu.baerts@...sares.net>
To: Eric Dumazet <eric.dumazet@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Cc: netdev <netdev@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>,
Bernard F6BVP <f6bvp@...e.fr>,
Duoming Zhou <duoming@....edu.cn>,
MPTCP Upstream <mptcp@...ts.linux.dev>
Subject: Re: [PATCH net] ax25: fix incorrect dev_tracker usage
Hello,
On 28/07/2022 07:18, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@...gle.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.
>
> After this patch is applied, we are able to focus on rose.
FYI, we got a small conflict when merging -net in net-next in the MPTCP
tree due to this patch applied in -net:
d7c4c9e075f8 ("ax25: fix incorrect dev_tracker usage")
and this one from net-next:
d62607c3fe45 ("net: rename reference+tracking helpers")
The conflict has been resolved on our side[1] and the resolution we
suggest is attached to this email.
I'm sharing this thinking it can help others but if it only creates
noise, please tell me! :-)
Cheers,
Matt
[1] https://github.com/multipath-tcp/mptcp_net-next/commit/b01791aa6b6c
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
View attachment "b01791aa6b6c783778b534f91997581a0e3caeb6.patch" of type "text/x-patch" (820 bytes)
Powered by blists - more mailing lists