From: Jason Gunthorpe <jgg@ziepe.ca>
To: Hillf Danton <hdanton@sina.com>
Cc: Leon Romanovsky <leon@kernel.org>,
syzbot <syzbot+3fd8326d9a0812d19218@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
markzhang@nvidia.com, ohartoov@nvidia.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING: refcount bug in nldev_newlink
Date: Fri, 9 Dec 2022 10:06:54 -0400 [thread overview]
Message-ID: <Y5NA/oZ7RpeUXzJN@ziepe.ca> (raw)
In-Reply-To: <20221209134229.1987-1-hdanton@sina.com>
On Fri, Dec 09, 2022 at 09:42:29PM +0800, Hillf Danton wrote:
> On 9 Dec 2022 09:01:14 -0400 Jason Gunthorpe <jgg@ziepe.ca>
> > On Thu, Dec 08, 2022 at 11:14:39AM +0200, Leon Romanovsky wrote:
> >
> > > Jason, what do you think?
> >
> > No, the key to this report is that the refcount dec is inside the tracker:
> >
> > > > __refcount_dec include/linux/refcount.h:344 [inline]
> > > > refcount_dec include/linux/refcount.h:359 [inline]
> > > > ref_tracker_free+0x539/0x6b0 lib/ref_tracker.c:118
> > > > netdev_tracker_free include/linux/netdevice.h:4039 [inline]
> >
> > Which is not underflowing the refcount on the dev, it is actually
> > trying to say the tracker has become unbalanced.
> >
> > Eg this put is not matched with a hold that specified the tracker.
> >
> > Probably this:
> >
> > diff --git a/drivers/infiniband/core/device.c b/drivers/infiniband/core/device.c
> > index ff35cebb25e265..115b77c5e9a146 100644
> > --- a/drivers/infiniband/core/device.c
> > +++ b/drivers/infiniband/core/device.c
> > @@ -2192,6 +2192,7 @@ static void free_netdevs(struct ib_device *ib_dev)
> > if (ndev) {
> > spin_lock(&ndev_hash_lock);
> > hash_del_rcu(&pdata->ndev_hash_link);
> > + netdev_tracker_free(ndev, &pdata->netdev_tracker);
> > spin_unlock(&ndev_hash_lock);
> >
> > /*
> > @@ -2201,7 +2202,7 @@ static void free_netdevs(struct ib_device *ib_dev)
> > * comparisons after the put
> > */
> > rcu_assign_pointer(pdata->netdev, NULL);
> > - dev_put(ndev);
> > + __dev_put(ndev);
> > }
> > spin_unlock_irqrestore(&pdata->netdev_lock, flags);
> > }
>
> Wonder why this makes sense given rcu_assign_pointer(pdata->netdev, NULL)
> under pdata->netdev_lock.
Oh, yah, that is right, so we can just do the natural thing:
rcu_assign_pointer(pdata->netdev, NULL);
- dev_put(ndev);
+ netdev_put(ndev, &pdata->netdev_tracker);
Jason
prev parent reply other threads:[~2022-12-09 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 20:51 [syzbot] WARNING: refcount bug in nldev_newlink syzbot
2022-12-08 9:14 ` Leon Romanovsky
2022-12-08 11:42 ` Guoqing Jiang
2022-12-08 11:54 ` Leon Romanovsky
2022-12-09 0:48 ` Guoqing Jiang
2022-12-09 13:01 ` Jason Gunthorpe
[not found] ` <20221209134229.1987-1-hdanton@sina.com>
2022-12-09 14:06 ` Jason Gunthorpe [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=Y5NA/oZ7RpeUXzJN@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=hdanton@sina.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markzhang@nvidia.com \
--cc=ohartoov@nvidia.com \
--cc=syzbot+3fd8326d9a0812d19218@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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