From: Guilherme Giacomo Simoes <trintaeoitogc@gmail.com>
To: timo.joannin@gmail.com
Cc: axboe@kernel.dk, bvanassche@acm.org, josef@toxicpanda.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
nbd@other.debian.org,
syzbot+d7d72f3d467710442af0@syzkaller.appspotmail.com,
trintaeoitogc@gmail.com
Subject: Re: [PATCH] nbd: fix circular lock dependency
Date: Wed, 11 Nov 2026 09:25:45 -0300 [thread overview]
Message-ID: <20261111122545.225934-1-trintaeoitogc@gmail.com> (raw)
In-Reply-To: <20261111112921.306969-1-timo.joannin@gmail.com>
Timo Joannin <timo.joannin@gmail.com> wrote:
> > Moving nbd_get_socket() makes this patch much larger than necessary,
> > which makes reviewing and backporting it harder. Adding a single
> > nbd_reclassify_socket(sock) call in nbd_genl_reconnect_sock_cb() right
> > after the nbd_get_socket() call is sufficient.
>
> Hi Guilherme and Bart,
>
> Thanks for working on this! I'm currently fixing a possible deadlock
> in wg_ratelimiter_uninit
> (Reported-by: syzbot+72fceb8393e04ce876d9@syzkaller.appspotmail.com)
> involving cpu_hotplug_lock and slab_mutex.
>
> My one syzbot test failed because of this lockdep
> false positive that this patch addresses. I applied Bart's suggested 1-line
> fix locally, and will see if it resolves the false positive.
> I will be submitting my cpu_hotplug_lock fix separately.
> I am looking forward to see your v2!
>
Cool, thanks
next prev parent reply other threads:[~2026-11-11 12:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 21:57 [PATCH] nbd: fix circular lock dependency Guilherme Giacomo Simoes
2026-11-11 0:40 ` Bart Van Assche
2026-11-11 10:19 ` Guilherme Giacomo Simoes
2026-11-11 11:29 ` Timo Joannin
2026-11-11 12:25 ` Guilherme Giacomo Simoes [this message]
2026-11-11 11:38 ` Guilherme Giacomo Simoes
2026-11-11 17:13 ` Bart Van Assche
2026-11-12 0:13 ` Hillf Danton
2026-11-12 11:11 ` Guilherme Giacomo Simoes
2026-11-12 11:03 ` Guilherme Giacomo Simoes
2026-11-11 12:24 ` Guilherme Giacomo Simoes
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=20261111122545.225934-1-trintaeoitogc@gmail.com \
--to=trintaeoitogc@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=syzbot+d7d72f3d467710442af0@syzkaller.appspotmail.com \
--cc=timo.joannin@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 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.