All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Tariq Toukan <ttoukan.linux@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, ast@kernel.org, daniel@iogearbox.net,
	hawk@kernel.org, john.fastabend@gmail.com, tariqt@nvidia.com,
	bpf@vger.kernel.org
Subject: Re: [PATCH net] net: xdp: don't call notifiers during driver init
Date: Thu, 16 Mar 2023 12:03:57 +0100	[thread overview]
Message-ID: <ZBL3nVZ4LVWUPRva@localhost.localdomain> (raw)
In-Reply-To: <ebe10b79-34c2-4e85-2cf7-b7491266748e@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]

> 
> 
> On 16/03/2023 2:29, Jakub Kicinski wrote:
> > Drivers will commonly perform feature setting during init, if they use
> > the xdp_set_features_flag() helper they'll likely run into an ASSERT_RTNL()
> > inside call_netdevice_notifiers_info().
> > 
> > Don't call the notifier until the device is actually registered.
> > Nothing should be tracking the device until its registered.
> > 
> > Fixes: 4d5ab0ad964d ("net/mlx5e: take into account device reconfiguration for xdp_features flag")
> > Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> > ---
> > CC: ast@kernel.org
> > CC: daniel@iogearbox.net
> > CC: hawk@kernel.org
> > CC: john.fastabend@gmail.com
> > CC: lorenzo@kernel.org
> > CC: tariqt@nvidia.com
> > CC: bpf@vger.kernel.org
> > ---
> >   net/core/xdp.c | 3 +++
> >   1 file changed, 3 insertions(+)
> > 
> > diff --git a/net/core/xdp.c b/net/core/xdp.c
> > index 87e654b7d06c..5722a1fc6e9e 100644
> > --- a/net/core/xdp.c
> > +++ b/net/core/xdp.c
> > @@ -781,6 +781,9 @@ void xdp_set_features_flag(struct net_device *dev, xdp_features_t val)
> >   		return;
> >   	dev->xdp_features = val;
> > +
> > +	if (dev->reg_state < NETREG_REGISTERED)
> > +		return;
> 
> I maybe need to dig deeper, but, it looks strange to still
> call_netdevice_notifiers in cases > NETREG_REGISTERED.
> 
> Isn't it problematic to call it with NETREG_UNREGISTERED ?
> 
> For comparison, netif_set_real_num_tx_queues has this ASSERT_RTNL() only
> under dev->reg_state == NETREG_REGISTERED || dev->reg_state ==
> NETREG_UNREGISTERING.

does it make sense to run call_netdevice_notifiers() in xdp_set_features_flag()
just if dev->reg_state is NETREG_REGISTERED?
Moreover, looking at the code it seems netdev code can run with dev->reg_state
set to NETREG_UNREGISTERED and without holding RTNL lock, right?

Regards,
Lorenzo

> 
> >   	call_netdevice_notifiers(NETDEV_XDP_FEAT_CHANGE, dev);
> >   }
> >   EXPORT_SYMBOL_GPL(xdp_set_features_flag);

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-03-16 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16  0:29 [PATCH net] net: xdp: don't call notifiers during driver init Jakub Kicinski
2023-03-16  5:31 ` John Fastabend
2023-03-16  6:49 ` Tariq Toukan
2023-03-16 11:03   ` Lorenzo Bianconi [this message]
2023-03-16 21:54     ` Jakub Kicinski
2023-03-16 21:59       ` Jakub Kicinski

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=ZBL3nVZ4LVWUPRva@localhost.localdomain \
    --to=lorenzo@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tariqt@nvidia.com \
    --cc=ttoukan.linux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.