Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Niklas Cassel <cassel@kernel.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: Tue, 12 May 2026 13:00:58 -0700	[thread overview]
Message-ID: <8a831bdf-6d32-45c4-bddc-9b14d6367407@acm.org> (raw)
In-Reply-To: <agIJdj0vUGLAWsg1@ryzen>

On 5/11/26 9:53 AM, Niklas Cassel wrote:
> 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 ?

This is something I can't do myself. This is something that should be 
done by an ATA expert. I'm not an ATA expert.

> 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?

Just like for (1), since there are inconsistencies between the
"LOCKING:" documentation and the implementation, this is best done by
an ATA expert.

The goal of the annotations in this patch is to make sure that the build
doesn't break with CONTEXT_ANALYSIS := y. Any additional annotations can
be implemented as follow-up patches.

Thanks,

Bart.

      reply	other threads:[~2026-05-12 20:01 UTC|newest]

Thread overview: 3+ 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
2026-05-12 20:00   ` 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=8a831bdf-6d32-45c4-bddc-9b14d6367407@acm.org \
    --to=bvanassche@acm.org \
    --cc=cassel@kernel.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