All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	Bernard Metzler <bmt@zurich.ibm.com>,
	Ursula Braun <ubraun@linux.ibm.com>,
	OFED mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH] RDMA: don't ignore client->add() failures
Date: Sat, 1 Apr 2023 21:30:56 +0300	[thread overview]
Message-ID: <20230401183056.GB831478@unreal> (raw)
In-Reply-To: <2e7a122d-78a9-efec-9140-6d21bceb7e04@I-love.SAKURA.ne.jp>

On Sat, Apr 01, 2023 at 04:30:08PM +0900, Tetsuo Handa wrote:
> On 2023/04/01 1:23, Jason Gunthorpe wrote:
> > On Sat, Apr 01, 2023 at 01:19:47AM +0900, Tetsuo Handa wrote:
> >> I guess that either dev_net(netdev) is not appropriately initialized or
> >> dev_net(netdev) != &init_net is too restrictive to call ib_unregister_device_queued().
> >> Where is dev_net(netdev) initialized?
> > 
> > Bernard? What is this net ns check for? It seems surprising this would
> > be here
> > 
> 
> Commit bdcf26bf9b3a ("rdma/siw: network and RDMA core interface") implemented
> siw_netdev_event() with
> 
> 	if (dev_net(netdev) != &init_net)
> 		return NOTIFY_OK;
> 
> check. But why this check is needed was not explained.
> Maybe ib_devices_shared_netns is relevant?
> 
> Since network devices created upon/after unshare(CLONE_NEWNET) have network
> namespace other than init_net, this check completely disables siw_netdev_event()
> after unshare(CLONE_NEWNET). Thus, removing this check looks reasonable.

I agree with Jason, this check is not supposed to be in siw in first place
and needs to be removed.

Thanks

      reply	other threads:[~2023-04-01 18:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 10:52 [PATCH] RDMA: don't ignore client->add() failures Tetsuo Handa
2023-03-28 11:24 ` Jason Gunthorpe
2023-03-28 11:33   ` Tetsuo Handa
2023-03-28 11:34     ` Jason Gunthorpe
2023-03-28 14:59       ` Tetsuo Handa
2023-03-28 16:18         ` Jason Gunthorpe
2023-03-28 22:17           ` Tetsuo Handa
2023-03-29 15:44             ` Jason Gunthorpe
2023-03-29 23:51               ` Tetsuo Handa
2023-03-30 23:39                 ` Jason Gunthorpe
2023-03-31 16:19                   ` Tetsuo Handa
2023-03-31 16:23                     ` Jason Gunthorpe
2023-04-01  7:30                       ` Tetsuo Handa
2023-04-01 18:30                         ` Leon Romanovsky [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=20230401183056.GB831478@unreal \
    --to=leon@kernel.org \
    --cc=bmt@zurich.ibm.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=ubraun@linux.ibm.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.