From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: jgg@ziepe.ca, leon@kernel.org, linux-rdma@vger.kernel.org
Cc: "Zhu Yanjun" <yanjun.zhu@linux.dev>,
syzbot+b0da83a6c0e2e2bddbd4@syzkaller.appspotmail.com
Subject: [PATCH rdma-next 1/1] RDMA/core: Fix WARNING in gid_table_release_one
Date: Mon, 3 Nov 2025 18:08:45 -0800 [thread overview]
Message-ID: <20251104020845.254870-1-yanjun.zhu@linux.dev> (raw)
From: "Zhu Yanjun" <yanjun.zhu@linux.dev>
GID entry ref leak for dev syz1 index 2 ref=615
...
Call Trace:
<TASK>
ib_device_release+0xd2/0x1c0 drivers/infiniband/core/device.c:509
device_release+0x99/0x1c0 drivers/base/core.c:-1
kobject_cleanup lib/kobject.c:689 [inline]
kobject_release lib/kobject.c:720 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x228/0x480 lib/kobject.c:737
process_one_work kernel/workqueue.c:3263 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x47c/0x820 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
When the state of a GID is GID_TABLE_ENTRY_PENDING_DEL, it indicates
that the GID is about to be released soon. Therefore, it does not
appear to be a leak.
The release_gid_table() function also waits for a short period; if the
GID still exists after that, a GID leak warning will be triggered.
Fixes: b150c3862d21 ("IB/core: Introduce GID entry reference counts")
Reported-by: syzbot+b0da83a6c0e2e2bddbd4@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=b0da83a6c0e2e2bddbd4
Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
---
drivers/infiniband/core/cache.c | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/drivers/infiniband/core/cache.c b/drivers/infiniband/core/cache.c
index 81cf3c902e81..451325ce6fa5 100644
--- a/drivers/infiniband/core/cache.c
+++ b/drivers/infiniband/core/cache.c
@@ -800,13 +800,24 @@ static void release_gid_table(struct ib_device *device,
return;
for (i = 0; i < table->sz; i++) {
+ int cnt = 200;
+
if (is_gid_entry_free(table->data_vec[i]))
continue;
- WARN_ONCE(true,
- "GID entry ref leak for dev %s index %d ref=%u\n",
+ WARN_ONCE(table->data_vec[i]->state != GID_TABLE_ENTRY_PENDING_DEL,
+ "GID entry ref leak for dev %s index %d ref=%u, state: %d\n",
dev_name(&device->dev), i,
- kref_read(&table->data_vec[i]->kref));
+ kref_read(&table->data_vec[i]->kref), table->data_vec[i]->state);
+
+ while ((kref_read(&table->data_vec[i]->kref) > 0) && (cnt > 0)) {
+ cnt--;
+ msleep(10);
+ }
+
+ if (cnt <= 0)
+ pr_warn_ratelimited("Possibly kref leak, ref:%u, state: %d\n",
+ kref_read(&table->data_vec[i]->kref), table->data_vec[i]->state);
}
mutex_destroy(&table->lock);
--
2.51.0
next reply other threads:[~2025-11-04 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 2:08 Zhu Yanjun [this message]
2025-11-04 13:00 ` [PATCH rdma-next 1/1] RDMA/core: Fix WARNING in gid_table_release_one Jason Gunthorpe
2025-11-04 15:39 ` Zhu Yanjun
2025-11-05 13:02 ` 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=20251104020845.254870-1-yanjun.zhu@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=syzbot+b0da83a6c0e2e2bddbd4@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).