From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Benson Leung <bleung@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>, Shuah Khan <shuah@kernel.org>,
Dawid Niedzwiecki <dawidn@google.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
chrome-platform@lists.linux.dev, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 1/5] revocable: Revocable resource management
Date: Wed, 17 Sep 2025 05:24:37 +0000 [thread overview]
Message-ID: <aMpGFXII_WGviShc@google.com> (raw)
In-Reply-To: <20250912081718.3827390-2-tzungbi@kernel.org>
On Fri, Sep 12, 2025 at 08:17:13AM +0000, Tzung-Bi Shih wrote:
> +void *revocable_try_access(struct revocable *rev) __acquires(&rev->rp->srcu)
> +{
> + struct revocable_provider *rp = rev->rp;
> +
> + rev->idx = srcu_read_lock(&rp->srcu);
> + return rcu_dereference(rp->res);
Got a warning from lock debugging. This should be srcu_dereference(). Will
fix it in the next version.
next prev parent reply other threads:[~2025-09-17 5:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 8:17 [PATCH v3 0/5] platform/chrome: Fix a possible UAF via revocable Tzung-Bi Shih
2025-09-12 8:17 ` [PATCH v3 1/5] revocable: Revocable resource management Tzung-Bi Shih
2025-09-12 9:05 ` Danilo Krummrich
2025-09-13 15:56 ` Tzung-Bi Shih
2025-09-12 13:27 ` Jonathan Corbet
2025-09-13 15:56 ` Tzung-Bi Shih
2025-09-17 5:24 ` Tzung-Bi Shih [this message]
2025-09-22 18:35 ` Simona Vetter
2025-09-12 8:17 ` [PATCH v3 2/5] revocable: Add Kunit test cases Tzung-Bi Shih
2025-09-12 8:17 ` [PATCH v3 3/5] selftests: revocable: Add kselftest cases Tzung-Bi Shih
2025-09-12 8:17 ` [PATCH v3 4/5] platform/chrome: Protect cros_ec_device lifecycle with revocable Tzung-Bi Shih
2025-09-12 8:17 ` [PATCH v3 5/5] platform/chrome: cros_ec_chardev: Consume cros_ec_device via revocable Tzung-Bi Shih
2025-09-12 8:30 ` [PATCH v3 0/5] platform/chrome: Fix a possible UAF " Greg Kroah-Hartman
2025-09-12 8:34 ` Danilo Krummrich
2025-09-12 9:20 ` Laurent Pinchart
2025-09-12 9:09 ` Krzysztof Kozlowski
2025-09-12 9:24 ` Bartosz Golaszewski
2025-09-12 12:49 ` Tzung-Bi Shih
2025-09-12 13:26 ` Laurent Pinchart
2025-09-12 13:39 ` Greg Kroah-Hartman
2025-09-12 13:45 ` Laurent Pinchart
2025-09-12 13:46 ` Bartosz Golaszewski
2025-09-12 13:59 ` Laurent Pinchart
2025-09-12 14:19 ` Greg Kroah-Hartman
2025-09-12 14:26 ` Laurent Pinchart
2025-09-12 14:40 ` Greg Kroah-Hartman
2025-09-12 14:44 ` Bartosz Golaszewski
2025-09-12 14:54 ` Laurent Pinchart
2025-09-12 16:22 ` Danilo Krummrich
2025-09-13 16:17 ` Laurent Pinchart
2025-09-22 22:43 ` dan.j.williams
2025-09-13 15:55 ` Tzung-Bi Shih
2025-09-13 16:14 ` Laurent Pinchart
2025-09-23 8:20 ` Tzung-Bi Shih
2025-09-12 14:53 ` Laurent Pinchart
2025-09-22 15:10 ` Jason Gunthorpe
2025-09-22 15:55 ` Danilo Krummrich
2025-09-22 17:40 ` Jason Gunthorpe
2025-09-22 18:42 ` Greg Kroah-Hartman
2025-09-22 20:17 ` Jason Gunthorpe
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=aMpGFXII_WGviShc@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=dawidn@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).