From: Larysa Zaremba <larysa.zaremba@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Shinas Rasheed <srasheed@marvell.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Haseeb Gani <hgani@marvell.com>,
"Sathesh B Edara" <sedara@marvell.com>,
Vimlesh Kumar <vimleshk@marvell.com>,
"thaller@redhat.com" <thaller@redhat.com>,
"wizhao@redhat.com" <wizhao@redhat.com>,
"kheib@redhat.com" <kheib@redhat.com>,
"konguyen@redhat.com" <konguyen@redhat.com>,
"horms@kernel.org" <horms@kernel.org>,
"einstein.xue@synaxg.com" <einstein.xue@synaxg.com>,
Veerasenareddy Burru <vburru@marvell.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Abhijit Ayarekar <aayarekar@marvell.com>,
Satananda Burla <sburla@marvell.com>
Subject: Re: [EXTERNAL] Re: [PATCH net v2 1/4] octeon_ep: fix race conditions in ndo_get_stats64
Date: Wed, 18 Dec 2024 15:49:32 +0100 [thread overview]
Message-ID: <Z2Lg/LDjrB2hDJSO@lzaremba-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <CANn89iJXNYRNn7N9AHKr0jECxn0Lh6_CtKG7kk9xjqhbVjjkjQ@mail.gmail.com>
On Wed, Dec 18, 2024 at 03:21:12PM +0100, Eric Dumazet wrote:
> On Wed, Dec 18, 2024 at 2:25 PM Larysa Zaremba <larysa.zaremba@intel.com> wrote:
>
> >
> > It is hard to know without testing (but testing should not be hard). I think the
> > phrase "Statistics must persist across routine operations like bringing the
> > interface down and up." [0] implies that bringing the interface down may not
> > necessarily prevent stats calls.
>
> Please don't add workarounds to individual drivers.
>
> I think the core networking stack should handle the possible races.
>
> Most dev_get_stats() callers are correctly testing dev_isalive() or
> are protected by RTNL.
>
> There are few nested cases that are not properly handled, the
> following patch should take care of them.
>
I was under the impression that .ndo_stop() being called does not mean the
device stops being NETREG_REGISTERED, such link would be required to solve the
original problem with your patch alone (though it is generally a good change).
Could you please explain this relation?
>
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index 2593019ad5b1614f3b8c037afb4ba4fa740c7d51..768afc2a18d343d051e7a1b631124910af9922d2
> 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -5342,6 +5342,12 @@ static inline const char
> *netdev_reg_state(const struct net_device *dev)
> return " (unknown)";
> }
>
> +/* Caller holds RTNL or RCU */
> +static inline int dev_isalive(const struct net_device *dev)
> +{
> + return READ_ONCE(dev->reg_state) <= NETREG_REGISTERED;
> +}
> +
> #define MODULE_ALIAS_NETDEV(device) \
> MODULE_ALIAS("netdev-" device)
>
> diff --git a/net/core/dev.c b/net/core/dev.c
> index c7f3dea3e0eb9eb05865e49dd7a8535afb974149..f11f305f3136f208fcb285c7b314914aef20dfad
> 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -11044,8 +11044,13 @@ struct rtnl_link_stats64
> *dev_get_stats(struct net_device *dev,
> const struct net_device_ops *ops = dev->netdev_ops;
> const struct net_device_core_stats __percpu *p;
>
> + memset(storage, 0, sizeof(*storage));
> + rcu_read_lock();
> +
> + if (unlikely(!dev_isalive(dev)))
> + goto unlock;
> +
> if (ops->ndo_get_stats64) {
> - memset(storage, 0, sizeof(*storage));
> ops->ndo_get_stats64(dev, storage);
> } else if (ops->ndo_get_stats) {
> netdev_stats_to_stats64(storage, ops->ndo_get_stats(dev));
> @@ -11071,6 +11076,8 @@ struct rtnl_link_stats64 *dev_get_stats(struct
> net_device *dev,
> storage->rx_otherhost_dropped +=
> READ_ONCE(core_stats->rx_otherhost_dropped);
> }
> }
> +unlock:
> + rcu_read_unlock();
> return storage;
> }
> EXPORT_SYMBOL(dev_get_stats);
> diff --git a/net/core/net-sysfs.c b/net/core/net-sysfs.c
> index 2d9afc6e2161efa51ffa62813ec10c8f43944bce..3f4851d67015c959dd531c571c46fc2ac18beb65
> 100644
> --- a/net/core/net-sysfs.c
> +++ b/net/core/net-sysfs.c
> @@ -36,12 +36,6 @@ static const char fmt_uint[] = "%u\n";
> static const char fmt_ulong[] = "%lu\n";
> static const char fmt_u64[] = "%llu\n";
>
> -/* Caller holds RTNL or RCU */
> -static inline int dev_isalive(const struct net_device *dev)
> -{
> - return READ_ONCE(dev->reg_state) <= NETREG_REGISTERED;
> -}
> -
> /* use same locking rules as GIF* ioctl's */
> static ssize_t netdev_show(const struct device *dev,
> struct device_attribute *attr, char *buf,
next prev parent reply other threads:[~2024-12-18 14:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 7:58 [PATCH net v2 0/4] Fix " Shinas Rasheed
2024-12-16 7:58 ` [PATCH net v2 1/4] octeon_ep: fix " Shinas Rasheed
2024-12-16 14:30 ` Larysa Zaremba
2024-12-16 14:46 ` Larysa Zaremba
2024-12-16 18:28 ` [EXTERNAL] " Shinas Rasheed
2024-12-17 17:06 ` Larysa Zaremba
2024-12-17 17:49 ` Shinas Rasheed
2024-12-18 13:25 ` Larysa Zaremba
2024-12-18 13:58 ` Shinas Rasheed
2024-12-18 14:21 ` Eric Dumazet
2024-12-18 14:49 ` Larysa Zaremba [this message]
2024-12-18 15:03 ` Eric Dumazet
2024-12-18 15:25 ` Shinas Rasheed
2024-12-18 15:39 ` Eric Dumazet
2024-12-19 16:28 ` Shinas Rasheed
2024-12-19 16:35 ` Eric Dumazet
2024-12-16 18:24 ` Shinas Rasheed
2024-12-16 7:58 ` [PATCH net v2 2/4] octeon_ep: remove firmware stats fetch " Shinas Rasheed
2024-12-16 14:40 ` Larysa Zaremba
2024-12-16 18:31 ` [EXTERNAL] " Shinas Rasheed
2024-12-17 16:37 ` Larysa Zaremba
2024-12-16 7:58 ` [PATCH net v2 3/4] octeon_ep_vf: fix race conditions " Shinas Rasheed
2024-12-16 7:58 ` [PATCH net v2 4/4] octeon_ep_vf: remove firmware stats fetch " Shinas Rasheed
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=Z2Lg/LDjrB2hDJSO@lzaremba-mobl.ger.corp.intel.com \
--to=larysa.zaremba@intel.com \
--cc=aayarekar@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=einstein.xue@synaxg.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=kheib@redhat.com \
--cc=konguyen@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sburla@marvell.com \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.com \
--cc=thaller@redhat.com \
--cc=vburru@marvell.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@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
all inboxes | Powered by JetHome®