All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Damien Le Moal <dlemoal@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v5 09/12] block/blk-mq-debugfs: Improve lock context annotations
Date: Mon, 1 Jun 2026 09:33:37 +0200	[thread overview]
Message-ID: <20260601073337.GE7799@lst.de> (raw)
In-Reply-To: <b49bc91945356894b8ab1dc2de1aabad6db3ce16.1779997063.git.bvanassche@acm.org>

On Thu, May 28, 2026 at 12:45:46PM -0700, Bart Van Assche wrote:
> Make the existing lock context annotations compatible with Clang. Add
> the lock context annotations that are missing.
> 
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
>  block/blk-mq-debugfs.c | 12 ++++++------
>  block/blk.h            |  4 ++++
>  2 files changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/block/blk-mq-debugfs.c b/block/blk-mq-debugfs.c
> index 047ec887456b..5c168e82273e 100644
> --- a/block/blk-mq-debugfs.c
> +++ b/block/blk-mq-debugfs.c
> @@ -20,7 +20,7 @@ static int queue_poll_stat_show(void *data, struct seq_file *m)
>  }
>  
>  static void *queue_requeue_list_start(struct seq_file *m, loff_t *pos)
> -	__acquires(&q->requeue_lock)
> +	__acquires(&((struct request_queue *)m->private)->requeue_lock)

I try to member where we got stuck on this, but isn't there a way
to at least have a macro for this dereference that can have a comment?

Also I guess most seq_file users will have a mess like this, but I
don't really know a good way around it.


  parent reply	other threads:[~2026-06-01  7:33 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 19:45 [PATCH v5 00/12] Enable lock context analysis Bart Van Assche
2026-05-28 19:45 ` [PATCH v5 01/12] block: Annotate the queue limits functions Bart Van Assche
2026-05-29  6:23   ` Hannes Reinecke
2026-05-28 19:45 ` [PATCH v5 02/12] block/bdev: Annotate the blk_holder_ops callback functions Bart Van Assche
2026-05-29  6:24   ` Hannes Reinecke
2026-06-01  7:28   ` Christoph Hellwig
2026-05-28 19:45 ` [PATCH v5 03/12] block/cgroup: Split blkg_conf_prep() Bart Van Assche
2026-05-29  6:26   ` Hannes Reinecke
2026-05-28 19:45 ` [PATCH v5 04/12] block/cgroup: Split blkg_conf_exit() Bart Van Assche
2026-05-29  6:27   ` Hannes Reinecke
2026-05-28 19:45 ` [PATCH v5 05/12] block/cgroup: Improve lock context annotations Bart Van Assche
2026-05-29  6:27   ` Hannes Reinecke
2026-06-01  7:28   ` Christoph Hellwig
2026-05-28 19:45 ` [PATCH v5 06/12] block/cgroup: Inline blkg_conf_{open,close}_bdev_frozen() Bart Van Assche
2026-05-29  6:29   ` Hannes Reinecke
2026-06-01  7:30   ` Christoph Hellwig
2026-05-28 19:45 ` [PATCH v5 07/12] block/crypto: Annotate the crypto functions Bart Van Assche
2026-05-29  6:30   ` Hannes Reinecke
2026-05-28 19:45 ` [PATCH v5 08/12] block/blk-iocost: Add lock context annotations Bart Van Assche
2026-05-29  6:31   ` Hannes Reinecke
2026-06-01  7:32   ` Christoph Hellwig
2026-06-01 19:46     ` Bart Van Assche
2026-05-28 19:45 ` [PATCH v5 09/12] block/blk-mq-debugfs: Improve " Bart Van Assche
2026-05-29  6:34   ` Hannes Reinecke
2026-06-01  7:33   ` Christoph Hellwig [this message]
2026-06-01 20:00     ` Bart Van Assche
2026-05-28 19:45 ` [PATCH v5 10/12] block/kyber: Make the lock context annotations compatible with Clang Bart Van Assche
2026-05-29  6:35   ` Hannes Reinecke
2026-06-01  7:34   ` Christoph Hellwig
2026-05-28 19:45 ` [PATCH v5 11/12] block/mq-deadline: " Bart Van Assche
2026-05-29  6:35   ` Hannes Reinecke
2026-06-01  7:34   ` Christoph Hellwig
2026-05-28 19:45 ` [PATCH v5 12/12] block: Enable lock context analysis Bart Van Assche
2026-05-29  6:36   ` Hannes Reinecke
2026-06-01  7:34   ` Christoph Hellwig

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=20260601073337.GE7799@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=nathan@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 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.