All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Tzung-Bi Shih <tzungbi@kernel.org>,
	Benson Leung <bleung@chromium.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	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,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH v3 0/5] platform/chrome: Fix a possible UAF via revocable
Date: Fri, 12 Sep 2025 12:20:00 +0300	[thread overview]
Message-ID: <20250912092000.GA31682@pendragon.ideasonboard.com> (raw)
In-Reply-To: <2025091224-blaming-untapped-6883@gregkh>

On Fri, Sep 12, 2025 at 10:30:45AM +0200, Greg KH wrote:
> On Fri, Sep 12, 2025 at 08:17:12AM +0000, Tzung-Bi Shih wrote:
> > This is a follow-up series of [1].  It tries to fix a possible UAF in the
> > fops of cros_ec_chardev after the underlying protocol device has gone by
> > using revocable.
> > 
> > The 1st patch introduces the revocable which is an implementation of ideas
> > from the talk [2].
> > 
> > The 2nd and 3rd patches add test cases for revocable in Kunit and selftest.
> > 
> > The 4th patch converts existing protocol devices to resource providers
> > of cros_ec_device.
> > 
> > The 5th patch converts cros_ec_chardev to a resource consumer of
> > cros_ec_device to fix the UAF.
> > 
> > [1] https://lore.kernel.org/chrome-platform/20250721044456.2736300-6-tzungbi@kernel.org/
> > [2] https://lpc.events/event/17/contributions/1627/
> > 
> > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> > Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
> 
> This is, frankly, wonderful work.  Thanks so much for doing this, it's
> what many of us have been wanting to see for a very long time but none
> of us got around to actually doing it.
> 
> And it has tests!  And documentation!  Couldn't ask for more.
> 
> We can bikeshed about the REVOCABLE() macro name, but frankly, you wrote
> it, you get to pick it :)
> 
> Laurent, Bartosz, Wolfram, any objection to this series?  I think this
> addresses the issues that all of you have been raising for years with
> our access of pointers that have different lifecycles from other
> structures (i.e. struct cdev from struct device).

I'll check this either later today or over the weekend.

> Also, Danilo, if you get the chance, can you give this a review as well?
> At first glance it looks good to me, but as you wrote the Rust
> implementation of this feature, a second pair of eyes would be great to
> have if you have the time.

-- 
Regards,

Laurent Pinchart

  parent reply	other threads:[~2025-09-12  9:20 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
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 [this message]
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=20250912092000.GA31682@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=bartosz.golaszewski@linaro.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 \
    --cc=tzungbi@kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.