From: Bart Van Assche <bvanassche@acm.org>
To: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Marco Elver <elver@google.com>
Subject: Re: [PATCH 00/12] drbd: Enable lock context analysis
Date: Wed, 22 Jul 2026 11:18:54 -0700 [thread overview]
Message-ID: <0f813803-2334-4e9b-8744-4440d13089ef@acm.org> (raw)
In-Reply-To: <cover.1783632330.git.bvanassche@acm.org>
On 7/9/26 2:35 PM, Bart Van Assche wrote:
> This patch series enables compile-time lock context analysis for DRBD. The goal
> of this series is to allow the compiler to statically verify that locks are
> acquired and released correctly, helping to prevent deadlocks and race
> conditions. This version addresses feedback received on the v1 series, improves
> the annotations, and refactors some conditional locking paths to use the modern
> cleanup.h guard infrastructure.
Christoph Böhmwalder, are you the right person to help with reviewing
this patch series?
Thanks,
Bart.
prev parent reply other threads:[~2026-07-22 18:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 21:35 [PATCH 00/12] drbd: Enable lock context analysis Bart Van Assche
2026-07-09 21:35 ` [PATCH 01/12] drbd: Remove "extern" from function declarations Bart Van Assche
2026-07-09 21:35 ` [PATCH 02/12] drbd: Retain one _get_ldev_if_state() implementation Bart Van Assche
2026-07-09 21:35 ` [PATCH 03/12] drbd: Remove the get_ldev_if_state() macro Bart Van Assche
2026-07-09 21:35 ` [PATCH 04/12] drbd: Remove the 'local' lock context Bart Van Assche
2026-07-09 21:35 ` [PATCH 05/12] drbd: Simplify the bitmap locking functions Bart Van Assche
2026-07-09 21:35 ` [PATCH 06/12] drbd: Move two declarations Bart Van Assche
2026-07-09 21:35 ` [PATCH 07/12] drbd: Pass 'resource' directly to complete_conflicting_writes() Bart Van Assche
2026-07-09 21:35 ` [PATCH 08/12] drbd: Split drbd_nl_get_connections_dumpit() Bart Van Assche
2026-07-09 21:35 ` [PATCH 09/12] drbd: Make a mutex_unlock() call unconditional Bart Van Assche
2026-07-09 21:35 ` [PATCH 10/12] drbd: Rework locking in drbd_req_state() Bart Van Assche
2026-07-09 21:35 ` [PATCH 11/12] drbd: Annotate drbd_bm_{lock,unlock}() Bart Van Assche
2026-07-09 21:35 ` [PATCH 12/12] drbd: Enable lock context analysis Bart Van Assche
2026-07-22 18:18 ` Bart Van Assche [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=0f813803-2334-4e9b-8744-4440d13089ef@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=christoph.boehmwalder@linbit.com \
--cc=elver@google.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
/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).