From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix locking bugs in error paths
Date: Tue, 18 Feb 2025 21:36:23 -0500 [thread overview]
Message-ID: <yq1seoamzj7.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250210203936.2946494-1-bvanassche@acm.org> (Bart Van Assche's message of "Mon, 10 Feb 2025 12:39:34 -0800")
Bart,
> Annotating struct mutex and the mutex_*() functions with Clang
> thread-safety attributes led to the discovery of two locking bugs in
> error paths of SCSI drivers. This patch series fixes these locking
> bugs. Please consider this patch series for the next merge window.
Applied to 6.15/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2025-02-19 2:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 20:39 [PATCH 0/2] Fix locking bugs in error paths Bart Van Assche
2025-02-10 20:39 ` [PATCH 1/2] scsi: mpi3mr: Fix locking in an error path Bart Van Assche
2025-02-10 20:39 ` [PATCH 2/2] scsi: mpt3sas: Fix a locking bug " Bart Van Assche
2025-02-19 2:36 ` Martin K. Petersen [this message]
2025-02-25 0:32 ` [PATCH 0/2] Fix locking bugs in error paths Martin K. Petersen
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=yq1seoamzj7.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@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