From: Joel Fernandes <joel@joelfernandes.org>
To: Eric Dumazet <edumazet@google.com>
Cc: linux-kernel@vger.kernel.org,
Cong Wang <xiyou.wangcong@gmail.com>,
David Ahern <dsahern@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Jakub Kicinski <kuba@kernel.org>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
rcu@vger.kernel.org, rostedt@goodmis.org, paulmck@kernel.org,
fweisbec@gmail.com
Subject: Re: [PATCH rcu/dev 2/3] net: Use call_rcu_flush() for in_dev_rcu_put
Date: Fri, 18 Nov 2022 00:52:45 +0000 [thread overview]
Message-ID: <Y3bXXYOeZQPkhQmP@google.com> (raw)
In-Reply-To: <CANn89iK345JjXoCAPYK6hZF99zBBWRM1z7xCWbstQJLb4aBGQg@mail.gmail.com>
Hi Eric,
On Thu, Nov 17, 2022 at 01:58:18PM -0800, Eric Dumazet wrote:
> On Wed, Nov 16, 2022 at 7:16 PM Joel Fernandes (Google)
> <joel@joelfernandes.org> wrote:
> >
> > In a networking test on ChromeOS, we find that using the new CONFIG_RCU_LAZY
> > causes a networking test to fail in the teardown phase.
> >
> > The failure happens during: ip netns del <name>
> >
> > Using ftrace, I found the callbacks it was queuing which this series fixes. Use
> > call_rcu_flush() to revert to the old behavior. With that, the test passes.
> >
> > Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
> > ---
> > net/ipv4/devinet.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/net/ipv4/devinet.c b/net/ipv4/devinet.c
> > index e8b9a9202fec..98b20f333e00 100644
> > --- a/net/ipv4/devinet.c
> > +++ b/net/ipv4/devinet.c
> > @@ -328,7 +328,7 @@ static void inetdev_destroy(struct in_device *in_dev)
> > neigh_parms_release(&arp_tbl, in_dev->arp_parms);
> > arp_ifdown(dev);
> >
> > - call_rcu(&in_dev->rcu_head, in_dev_rcu_put);
> > + call_rcu_flush(&in_dev->rcu_head, in_dev_rcu_put);
> > }
>
> For this one, I suspect the issue is about device refcount lingering ?
>
> I think we should release refcounts earlier (and only delegate the
> freeing part after RCU grace period, which can be 'lazy' just fine)
>
> Something like:
The below diff where you reduce refcount before RCU grace period, also makes the
test pass.
If you are Ok with it, I can roll it into a patch with your Author tag and my
Tested-by. Let me know what you prefer?
Also, looking through the patch, I don't see any issue. One thing is
netdev_put() now happens before a grace period, instead of after. But I don't
think that's an issue.
thanks!
- Joel
>
> diff --git a/net/ipv4/devinet.c b/net/ipv4/devinet.c
> index e8b9a9202fecd913137f169f161dfdccc16f7edf..e0258aef4211ec6a72d062963470a32776e6d010
> 100644
> --- a/net/ipv4/devinet.c
> +++ b/net/ipv4/devinet.c
> @@ -234,13 +234,21 @@ static void inet_free_ifa(struct in_ifaddr *ifa)
> call_rcu(&ifa->rcu_head, inet_rcu_free_ifa);
> }
>
> +static void in_dev_free_rcu(struct rcu_head *head)
> +{
> + struct in_device *idev = container_of(head, struct in_device, rcu_head);
> +
> + kfree(rcu_dereference_protected(idev->mc_hash, 1));
> + kfree(idev);
> +}
> +
> void in_dev_finish_destroy(struct in_device *idev)
> {
> struct net_device *dev = idev->dev;
>
> WARN_ON(idev->ifa_list);
> WARN_ON(idev->mc_list);
> - kfree(rcu_dereference_protected(idev->mc_hash, 1));
> +
> #ifdef NET_REFCNT_DEBUG
> pr_debug("%s: %p=%s\n", __func__, idev, dev ? dev->name : "NIL");
> #endif
> @@ -248,7 +256,7 @@ void in_dev_finish_destroy(struct in_device *idev)
> if (!idev->dead)
> pr_err("Freeing alive in_device %p\n", idev);
> else
> - kfree(idev);
> + call_rcu(&idev->rcu_head, in_dev_free_rcu);
> }
> EXPORT_SYMBOL(in_dev_finish_destroy);
>
> @@ -298,12 +306,6 @@ static struct in_device *inetdev_init(struct
> net_device *dev)
> goto out;
> }
>
> -static void in_dev_rcu_put(struct rcu_head *head)
> -{
> - struct in_device *idev = container_of(head, struct in_device, rcu_head);
> - in_dev_put(idev);
> -}
> -
> static void inetdev_destroy(struct in_device *in_dev)
> {
> struct net_device *dev;
> @@ -328,7 +330,7 @@ static void inetdev_destroy(struct in_device *in_dev)
> neigh_parms_release(&arp_tbl, in_dev->arp_parms);
> arp_ifdown(dev);
>
> - call_rcu(&in_dev->rcu_head, in_dev_rcu_put);
> + in_dev_put(in_dev);
> }
>
> int inet_addr_onlink(struct in_device *in_dev, __be32 a, __be32 b)
next prev parent reply other threads:[~2022-11-18 0:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 3:15 [PATCH rcu/dev 1/3] net: Use call_rcu_flush() for qdisc_free_cb Joel Fernandes (Google)
2022-11-17 3:15 ` [PATCH rcu/dev 2/3] net: Use call_rcu_flush() for in_dev_rcu_put Joel Fernandes (Google)
2022-11-17 21:58 ` Eric Dumazet
2022-11-18 0:52 ` Joel Fernandes [this message]
2022-11-18 1:12 ` Eric Dumazet
2022-11-17 3:15 ` [PATCH rcu/dev 3/3] net: Use call_rcu_flush() for dst_destroy_rcu Joel Fernandes (Google)
2022-11-17 3:44 ` Eric Dumazet
2022-11-17 15:58 ` Joel Fernandes
2022-11-17 17:17 ` Eric Dumazet
2022-11-17 17:33 ` Eric Dumazet
2022-11-17 17:38 ` Joel Fernandes
2022-11-17 17:39 ` Eric Dumazet
2022-11-17 17:42 ` Joel Fernandes
2022-11-17 17:49 ` Eric Dumazet
2022-11-17 18:18 ` Joel Fernandes
2022-11-17 18:22 ` Eric Dumazet
2022-11-17 17:40 ` Joel Fernandes
2022-11-17 19:29 ` Paul E. McKenney
2022-11-17 21:16 ` Joel Fernandes
2022-11-17 21:29 ` Eric Dumazet
2022-11-18 1:05 ` Joel Fernandes
2022-11-17 21:44 ` [PATCH rcu/dev 1/3] net: Use call_rcu_flush() for qdisc_free_cb Eric Dumazet
2022-11-17 21:58 ` Joel Fernandes
2022-11-18 0:23 ` Joel Fernandes
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=Y3bXXYOeZQPkhQmP@google.com \
--to=joel@joelfernandes.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yoshfuji@linux-ipv6.org \
/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).