From: "Yanjun.Zhu" <yanjun.zhu@linux.dev>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Jason Gunthorpe <jgg@ziepe.ca>
Cc: Jiri Pirko <jiri@resnulli.us>,
linux-rdma@vger.kernel.org, leon@kernel.org, msanalla@nvidia.com,
maorg@nvidia.com, parav@nvidia.com, mbloch@nvidia.com,
markzhang@nvidia.com, marco.crivellari@suse.com,
roman.gushchin@linux.dev, wangliang74@huawei.com
Subject: Re: [PATCH] RDMA/core: Fix stale RoCE GIDs during netdev events at registration
Date: Tue, 27 Jan 2026 14:54:42 -0800 [thread overview]
Message-ID: <f3402d0f-40a1-4792-a8e2-be65c71a176b@linux.dev> (raw)
In-Reply-To: <9975b59a-58e2-4766-9e4e-c927a1d7a3d0@I-love.SAKURA.ne.jp>
On 1/27/26 2:16 PM, Tetsuo Handa wrote:
> On 2026/01/28 6:17, Yanjun.Zhu wrote:
>>> Can we feed it to syzkaller please and see if it does actually clear
>>> it's repo? That particular bug already has 5 patches claiming to fix
>>> it.
>>
>> #syz test: repository_link branch
>>
>> The above command will make syzkaller test your commit.
>>
>> BTW, your commit should be the topmost commit.
> No, we can't ask syzbot to test this patch.
>
> All kinds of refcounting errors that appear as
>
> unregister_netdevice: waiting for $dev to become free. Usage count = $count
>
> problem are reported there, but syzbot has not found a reproducer for
> the bug this patch addresses.
>
> I can test this patch using linux-next tree via my tree if you like.
Thanks. Currently, syzbot does not have a reproducer to reproduce and
verify this issue.
However, you have a test environment to reproduce the problem, and you
can verify this commit.
Is that correct?
If so, that would be very helpful.
Zhu Yanjun
>
>>
>> Thanks,
>>
>> Zhu Yanjun
>>
>>> It has become some kind of catch all of all kinds of refcounting errors
>>>
>>> [ 247.188486][ T6052] unregister_netdevice: waiting for vcan0 to become free. Usage count = 2
>>>
>>> Does this actually change the refcounting around that could fix that?
>>> Looked like no?
>>>
>>> Jason
next prev parent reply other threads:[~2026-01-27 22:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 9:38 [PATCH] RDMA/core: Fix stale RoCE GIDs during netdev events at registration Jiri Pirko
2026-01-27 11:14 ` Tetsuo Handa
2026-01-27 11:58 ` Jiri Pirko
2026-01-27 16:00 ` Jason Gunthorpe
2026-01-27 21:17 ` Yanjun.Zhu
2026-01-27 22:16 ` Tetsuo Handa
2026-01-27 22:54 ` Yanjun.Zhu [this message]
2026-01-28 4:52 ` Tetsuo Handa
2026-01-28 8:26 ` Tetsuo Handa
2026-01-28 13:40 ` Jiri Pirko
2026-01-29 6:06 ` Tetsuo Handa
2026-01-29 12:38 ` Jiri Pirko
2026-01-29 13:48 ` Tetsuo Handa
2026-01-29 14:58 ` Jiri Pirko
2026-02-02 14:20 ` Tetsuo Handa
2026-02-02 23:51 ` Jason Gunthorpe
2026-02-03 3:52 ` Tetsuo Handa
2026-02-10 8:58 ` Jiri Pirko
2026-02-10 10:22 ` Tetsuo Handa
2026-02-10 15:42 ` Jason Gunthorpe
2026-02-11 1:30 ` Tetsuo Handa
2026-02-03 9:07 ` Jiri Pirko
2026-01-28 13:43 ` Jiri Pirko
2026-02-24 8:59 ` Leon Romanovsky
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=f3402d0f-40a1-4792-a8e2-be65c71a176b@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=jiri@resnulli.us \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=marco.crivellari@suse.com \
--cc=markzhang@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=msanalla@nvidia.com \
--cc=parav@nvidia.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=roman.gushchin@linux.dev \
--cc=wangliang74@huawei.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.