mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eduard Zateev <hackerowskiy@gmail.com>
To: Hillf Danton <hdanton@sina.com>
Cc: linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, rds-devel@oss.oracle.com
Subject: Re: [syzbot] [rdma?] possible deadlock in rds_trans_get_preferred
Date: Mon, 26 Oct 2026 09:57:27 +0000	[thread overview]
Message-ID: <179300864774.19661.11942156119304654192@gmail.com> (raw)
In-Reply-To: <20261019015139.806-1-hdanton@sina.com>

Hi Hillf,

I tested your asynchronous CMA ID destruction patch from the #syz test
reply on the current upstream checkout at 21a7f44fd076 (Linux 7.3.0).

The kernel was built with KASAN, lockdep, RDMA_RXE and RDS enabled. I ran
the syzbot C reproducer in QEMU with four vCPUs. On the unpatched kernel it
reproduced the reported circular locking dependency between rds_trans_sem
and the RDMA CMA handler_mutex. With your patch applied, the same
reproducer completed successfully, established both active and passive RDS
connections, and produced no possible circular locking, possible recursive
locking, WARNING, Oops, or BUG output.

The build completed successfully and checkpatch.pl --strict reported no
errors or warnings. The complete test logs and the applied diff are
available on request.

Tested-by: Eduard Zateev <hackerowskiy@gmail.com>

  parent reply	other threads:[~2026-10-26  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 19:14 syzbot
2026-10-19  1:51 ` Hillf Danton
2026-10-19  1:51   ` syzbot
2026-10-26  9:57   ` Eduard Zateev [this message]
2026-10-19  8:04 ` Hillf Danton
2026-10-19  8:24   ` syzbot

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=179300864774.19661.11942156119304654192@gmail.com \
    --to=hackerowskiy@gmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rds-devel@oss.oracle.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
all inboxes | Powered by JetHome®