From: Niklas Cassel <cassel@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
Marco Elver <elver@google.com>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: libata-core: Enable context analysis
Date: Mon, 11 May 2026 18:53:10 +0200 [thread overview]
Message-ID: <agIJdj0vUGLAWsg1@ryzen> (raw)
In-Reply-To: <20260505042227.909666-1-bvanassche@acm.org>
On Tue, May 05, 2026 at 06:22:27AM +0200, Bart Van Assche wrote:
> Enable Clang's context analysis. This will cause the build to fail if
> e.g. a locking bug would be introduced in an error path. This patch
> should not affect the generated assembler code.
>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
> drivers/ata/Makefile | 2 ++
> drivers/ata/libata-core.c | 28 ++++++++++++++++++++++++++++
> drivers/ata/libata-eh.c | 6 ++++++
> drivers/ata/libata.h | 6 ++++--
> 4 files changed, 40 insertions(+), 2 deletions(-)
Hello Bart,
Thank you for doing this work!
It looks nice to me.
I did notice two things:
1) It seems that you are only checking for the EH mutex.
$ git grep -A 1 "LOCKING" drivers/ata/
Does have many functions with:
LOCKING:
spin_lock_irqsave(host lock)
Would it be possible to add __must_hold() annotations for these functions
too, but for ap->lock instead of EH mutex ?
2) There seems to be some files that did not get any annotations, e.g.
drivers/ata/libata-scsi.c, drivers/ata/libata-sata.c,
drivers/ata/libata-acpi.c, drivers/ata/libata-pmp.c.
Would it be possible to add annotations for these files too?
Kind regards,
Niklas
prev parent reply other threads:[~2026-05-11 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 4:22 [PATCH] ata: libata-core: Enable context analysis Bart Van Assche
2026-05-11 16:53 ` Niklas Cassel [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=agIJdj0vUGLAWsg1@ryzen \
--to=cassel@kernel.org \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=elver@google.com \
--cc=linux-ide@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