From: Sudeep Holla <sudeep.holla@kernel.org>
To: Christian Loehle <christian.loehle@arm.com>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
breno Leitao <leitao@debian.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 2/2] mailbox: pcc: Serialize channel updates with shared memory teardown
Date: Thu, 3 Sep 2026 13:40:52 +0100 [thread overview]
Message-ID: <20260903-solid-unbiased-hog-26c0ef@sudeepholla> (raw)
In-Reply-To: <20260903111328.805352-3-christian.loehle@arm.com>
On Thu, Sep 03, 2026 at 12:13:28PM +0100, Christian Loehle wrote:
> mbox_free_channel() makes a PCC channel available before the subsequent
> shared-memory unmap. Without serialization, a concurrent request can bind a
> new client and replace the mapping, which the old release then unmaps.
>
> Serialize PCC channel acquisition and release. Keep the channel unavailable
> until the old shared-memory mapping has been removed.
>
> Suggested-by: Sudeep Holla <sudeep.holla@kernel.org>
Reviewed-by: Sudeep Holla <sudeep.holla@kernel.org>
--
Regards,
Sudeep
next prev parent reply other threads:[~2026-09-03 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 11:13 [PATCH 0/2] mailbox: pcc: Fix shared-memory teardown race Christian Loehle
2026-09-03 11:13 ` [PATCH 1/2] mailbox: pcc: Free the channel before unmapping the shared memory Christian Loehle
2026-09-03 11:13 ` [PATCH 2/2] mailbox: pcc: Serialize channel updates with shared memory teardown Christian Loehle
2026-09-03 12:40 ` Sudeep Holla [this message]
2026-09-03 12:42 ` [PATCH 0/2] mailbox: pcc: Fix shared-memory teardown race Sudeep Holla
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=20260903-solid-unbiased-hog-26c0ef@sudeepholla \
--to=sudeep.holla@kernel.org \
--cc=christian.loehle@arm.com \
--cc=jassisinghbrar@gmail.com \
--cc=leitao@debian.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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