public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>,
	 Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: davem@davemloft.net,  netdev@vger.kernel.org,
	 edumazet@google.com,  pabeni@redhat.com,  andrew+netdev@lunn.ch,
	 horms@kernel.org,  Yiming Qian <yimingqian591@gmail.com>,
	 daniel.zahka@gmail.com
Subject: Re: [PATCH net] net: psp: check for device unregister when creating assoc
Date: Thu, 26 Mar 2026 16:46:04 -0400	[thread overview]
Message-ID: <willemdebruijn.kernel.5279c14a2134@gmail.com> (raw)
In-Reply-To: <20260326130459.7225ae28@kernel.org>

Jakub Kicinski wrote:
> On Tue, 24 Mar 2026 18:40:00 -0400 Willem de Bruijn wrote:
> > > @@ -320,6 +320,11 @@ int psp_assoc_device_get_locked(const struct genl_split_ops *ops,
> > >  	id = info->attrs[PSP_A_ASSOC_DEV_ID];
> > >  	if (psd) {
> > >  		mutex_lock(&psd->lock);
> > > +		if (!psp_dev_is_registered(psd)) {
> > > +			mutex_unlock(&psd->lock);
> > > +			err = -ENODEV;
> > > +			goto err_psd_put;
> > > +		}  
> > 
> > This ensures that psd is valid for this caller of psp_dev_get_for_sock
> > and psp_dev_tryget, which is its only one (for now).
> > 
> > But is it confusing that psd can be cleared out while a reference is
> > held? Is the assumption that psp_dev_unregister usually holds the last
> > reference and its psp_dev_put will complete the clean up by calling
> > psp_dev_free. If so, would it make sense to defer everything
> > to psp_dev_free?
> > 
> > This is a simpler changes and fixes the issue for the only caller, so
> > LGTM. Just curious.
> 
> Meaning we should add a dance around removal like netdev does?
> Sleep until all the references are gone?
> Subjectively I think it's ugly, and in netdev it didn't really
> prevent races. Dunno, definitely subjective.

Yeah, if any caller of psp_dev_unregister has to know that the device
is gone to proceed, it would require something like that. Okay, I see
that that is needlessly messy.

      reply	other threads:[~2026-03-26 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 20:51 [PATCH net] net: psp: check for device unregister when creating assoc Jakub Kicinski
2026-03-24 22:40 ` Willem de Bruijn
2026-03-26 20:04   ` Jakub Kicinski
2026-03-26 20:46     ` Willem de Bruijn [this message]

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=willemdebruijn.kernel.5279c14a2134@gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=daniel.zahka@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=yimingqian591@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox