Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: zyjzyj2000@gmail.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
	 Zhu Yanjun <yanjun.zhu@linux.dev>
Cc: syzbot+4edb496c3cad6e953a31@syzkaller.appspotmail.com
Subject: Re: [PATCH 1/1] RDMA/rxe: Fix "trying to register non-static key in rxe_qp_do_cleanup" bug
Date: Sun, 20 Apr 2025 11:26:37 -0400	[thread overview]
Message-ID: <174516279738.722044.3994618859935049405.b4-ty@kernel.org> (raw)
In-Reply-To: <20250419080741.1515231-1-yanjun.zhu@linux.dev>


On Sat, 19 Apr 2025 10:07:41 +0200, Zhu Yanjun wrote:
> Call Trace:
>  <TASK>
>  __dump_stack lib/dump_stack.c:94 [inline]
>  dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
>  assign_lock_key kernel/locking/lockdep.c:986 [inline]
>  register_lock_class+0x4a3/0x4c0 kernel/locking/lockdep.c:1300
>  __lock_acquire+0x99/0x1ba0 kernel/locking/lockdep.c:5110
>  lock_acquire kernel/locking/lockdep.c:5866 [inline]
>  lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5823
>  __timer_delete_sync+0x152/0x1b0 kernel/time/timer.c:1644
>  rxe_qp_do_cleanup+0x5c3/0x7e0 drivers/infiniband/sw/rxe/rxe_qp.c:815
>  execute_in_process_context+0x3a/0x160 kernel/workqueue.c:4596
>  __rxe_cleanup+0x267/0x3c0 drivers/infiniband/sw/rxe/rxe_pool.c:232
>  rxe_create_qp+0x3f7/0x5f0 drivers/infiniband/sw/rxe/rxe_verbs.c:604
>  create_qp+0x62d/0xa80 drivers/infiniband/core/verbs.c:1250
>  ib_create_qp_kernel+0x9f/0x310 drivers/infiniband/core/verbs.c:1361
>  ib_create_qp include/rdma/ib_verbs.h:3803 [inline]
>  rdma_create_qp+0x10c/0x340 drivers/infiniband/core/cma.c:1144
>  rds_ib_setup_qp+0xc86/0x19a0 net/rds/ib_cm.c:600
>  rds_ib_cm_initiate_connect+0x1e8/0x3d0 net/rds/ib_cm.c:944
>  rds_rdma_cm_event_handler_cmn+0x61f/0x8c0 net/rds/rdma_transport.c:109
>  cma_cm_event_handler+0x94/0x300 drivers/infiniband/core/cma.c:2184
>  cma_work_handler+0x15b/0x230 drivers/infiniband/core/cma.c:3042
>  process_one_work+0x9cc/0x1b70 kernel/workqueue.c:3238
>  process_scheduled_works kernel/workqueue.c:3319 [inline]
>  worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400
>  kthread+0x3c2/0x780 kernel/kthread.c:464
>  ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:153
>  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
>  </TASK>
> 
> [...]

Applied, thanks!

[1/1] RDMA/rxe: Fix "trying to register non-static key in rxe_qp_do_cleanup" bug
      https://git.kernel.org/rdma/rdma/c/1c7eec4d5f3b39

Best regards,
-- 
Leon Romanovsky <leon@kernel.org>


      reply	other threads:[~2025-04-20 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-19  8:07 [PATCH 1/1] RDMA/rxe: Fix "trying to register non-static key in rxe_qp_do_cleanup" bug Zhu Yanjun
2025-04-20 15:26 ` 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=174516279738.722044.3994618859935049405.b4-ty@kernel.org \
    --to=leon@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=syzbot+4edb496c3cad6e953a31@syzkaller.appspotmail.com \
    --cc=yanjun.zhu@linux.dev \
    --cc=zyjzyj2000@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