[PATCH v6 0/2] platform/chrome: Fix an UAF via revocable primitive APIs

[Tzung-Bi Shih <tzungbi@kernel.org>]

The series is separated from [1] to show the independency and compare
potential use cases easier.  This use case uses the primitive revocable
APIs directly.  It relies on the revocable core part [2].

It tries to fix an UAF in the fops of cros_ec_chardev after the
underlying protocol device has gone by using revocable.

The file operations make sure the resources are available when using them.

Even though it has the finest grain for accessing the resources, it makes
the user code verbose.  Per feedback from the community, I'm looking for
some subsystem level helpers so that user code can be simlper.

The 1st patch converts existing protocol devices to resource providers
of cros_ec_device.

The 2nd patch converts cros_ec_chardev to a resource consumer of
cros_ec_device to fix the UAF.

[1] https://lore.kernel.org/chrome-platform/20251016054204.1523139-1-tzungbi@kernel.org
[2] https://lore.kernel.org/chrome-platform/20251106152330.11733-1-tzungbi@kernel.org/

v6:
- New, separated from an existing series.

Tzung-Bi Shih (2):
  platform/chrome: Protect cros_ec_device lifecycle with revocable
  platform/chrome: cros_ec_chardev: Consume cros_ec_device via revocable

 drivers/platform/chrome/cros_ec.c           |  5 ++
 drivers/platform/chrome/cros_ec_chardev.c   | 71 ++++++++++++++++-----
 include/linux/platform_data/cros_ec_proto.h |  4 ++
 3 files changed, 65 insertions(+), 15 deletions(-)

-- 
2.48.1