From: Leon Romanovsky <leon@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
"David S. Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Raed Salem <raeds@nvidia.com>
Subject: Re: [PATCH xfrm 1/2] xfrm: release all offloaded policy memory
Date: Thu, 20 Apr 2023 20:04:47 +0300 [thread overview]
Message-ID: <20230420170447.GD4423@unreal> (raw)
In-Reply-To: <CANn89i+3SDjwYb=0CAuGgUyGieCqHKso9cHCf=iSKYhV3rdi=Q@mail.gmail.com>
On Thu, Apr 20, 2023 at 06:51:52PM +0200, Eric Dumazet wrote:
> On Wed, Apr 19, 2023 at 2:19 PM Leon Romanovsky <leon@kernel.org> wrote:
> >
> > From: Leon Romanovsky <leonro@nvidia.com>
> >
> > Failure to add offloaded policy will cause to the following
> > error once user will try to reload driver.
> >
> > Unregister_netdevice: waiting for eth3 to become free. Usage count = 2
> >
> > This was caused by xfrm_dev_policy_add() which increments reference
> > to net_device. That reference was supposed to be decremented
> > in xfrm_dev_policy_free(). However the latter wasn't called.
> >
> > unregister_netdevice: waiting for eth3 to become free. Usage count = 2
> > leaked reference.
> > xfrm_dev_policy_add+0xff/0x3d0
> > xfrm_policy_construct+0x352/0x420
> > xfrm_add_policy+0x179/0x320
> > xfrm_user_rcv_msg+0x1d2/0x3d0
> > netlink_rcv_skb+0xe0/0x210
> > xfrm_netlink_rcv+0x45/0x50
> > netlink_unicast+0x346/0x490
> > netlink_sendmsg+0x3b0/0x6c0
> > sock_sendmsg+0x73/0xc0
> > sock_write_iter+0x13b/0x1f0
> > vfs_write+0x528/0x5d0
> > ksys_write+0x120/0x150
> > do_syscall_64+0x3d/0x90
> > entry_SYSCALL_64_after_hwframe+0x46/0xb0
> >
> > Fixes: 919e43fad516 ("xfrm: add an interface to offload policy")
> > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> > ---
>
> Reviewed-by: Eric Dumazet <edumazet@google.com>
>
> While reviewing this patch, I also saw xfrm_dev_policy_add() could use
> GFP_KERNEL ?
netdev_tracker_alloc(...) line was copied from commit e1b539bd73a7
("xfrm: add net device refcount tracker to struct xfrm_state_offload")
Thanks
>
> diff --git a/net/xfrm/xfrm_device.c b/net/xfrm/xfrm_device.c
> index bef28c6187ebdd0cfc34c8594aab96ac0b13dd24..508c96c90b3911eb88063ad680c77af2b317c95f
> 100644
> --- a/net/xfrm/xfrm_device.c
> +++ b/net/xfrm/xfrm_device.c
> @@ -363,7 +363,7 @@ int xfrm_dev_policy_add(struct net *net, struct
> xfrm_policy *xp,
> }
>
> xdo->dev = dev;
> - netdev_tracker_alloc(dev, &xdo->dev_tracker, GFP_ATOMIC);
> + netdev_tracker_alloc(dev, &xdo->dev_tracker, GFP_KERNEL);
> xdo->real_dev = dev;
> xdo->type = XFRM_DEV_OFFLOAD_PACKET;
> switch (dir) {
next prev parent reply other threads:[~2023-04-20 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 12:19 [PATCH xfrm 0/2] Couple of error unwind fixes to packet offload Leon Romanovsky
2023-04-19 12:19 ` [PATCH xfrm 1/2] xfrm: release all offloaded policy memory Leon Romanovsky
2023-04-20 15:10 ` Simon Horman
2023-04-20 16:51 ` Eric Dumazet
2023-04-20 17:04 ` Leon Romanovsky [this message]
2023-04-20 17:33 ` Eric Dumazet
2023-04-21 8:46 ` Steffen Klassert
2023-04-19 12:19 ` [PATCH xfrm 2/2] xfrm: Fix leak of dev tracker Leon Romanovsky
2023-04-20 15:10 ` Simon Horman
2023-04-20 16:44 ` Eric Dumazet
2023-04-21 8:45 ` [PATCH xfrm 0/2] Couple of error unwind fixes to packet offload Steffen Klassert
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=20230420170447.GD4423@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raeds@nvidia.com \
--cc=steffen.klassert@secunet.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).