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>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
chrome-platform@lists.linux.dev, linux-kselftest@vger.kernel.org,
tzungbi@kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Simona Vetter <simona.vetter@ffwll.ch>,
Dan Williams <dan.j.williams@intel.com>,
Jason Gunthorpe <jgg@nvidia.com>
Subject: [PATCH v6 2/3] char: misc: Leverage revocable fops replacement
Date: Thu, 6 Nov 2025 23:27:11 +0800 [thread overview]
Message-ID: <20251106152712.11850-3-tzungbi@kernel.org> (raw)
In-Reply-To: <20251106152712.11850-1-tzungbi@kernel.org>
Leverage revocable fops replacement if the driver requests.
The "resource" in the context means presence of the miscdevice. It
prevents file operations (except .release()) in drivers to be called if
the miscdevice no longer exists.
Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org>
---
v6:
- Call fs_revocable_replace() after f_op->open() and modify the API
usage accordingly.
- Use presence of miscdevice as a virtual resource.
v5: https://lore.kernel.org/chrome-platform/20251016054204.1523139-7-tzungbi@kernel.org
- No primary changes but modify the API usage accordingly to support
multiple revocable providers.
v4: https://lore.kernel.org/chrome-platform/20250923075302.591026-7-tzungbi@kernel.org
- New in the series.
drivers/char/misc.c | 18 ++++++++++++++++--
include/linux/miscdevice.h | 2 ++
2 files changed, 18 insertions(+), 2 deletions(-)
diff --git a/drivers/char/misc.c b/drivers/char/misc.c
index 726516fb0a3b..e0106270c188 100644
--- a/drivers/char/misc.c
+++ b/drivers/char/misc.c
@@ -50,6 +50,8 @@
#include <linux/tty.h>
#include <linux/kmod.h>
#include <linux/gfp.h>
+#include <linux/fs_revocable.h>
+#include <linux/revocable.h>
/*
* Head entry for the doubly linked miscdevice list
@@ -157,10 +159,16 @@ static int misc_open(struct inode *inode, struct file *file)
*/
file->private_data = c;
- err = 0;
replace_fops(file, new_fops);
- if (file->f_op->open)
+
+ if (file->f_op->open) {
err = file->f_op->open(inode, file);
+ if (err)
+ goto fail;
+ }
+
+ if (c->revocable)
+ err = fs_revocable_replace(c->rp, file);
fail:
mutex_unlock(&misc_mtx);
return err;
@@ -218,6 +226,10 @@ int misc_register(struct miscdevice *misc)
return -EINVAL;
}
+ misc->rp = revocable_provider_alloc(misc);
+ if (!misc->rp)
+ return -ENOMEM;
+
INIT_LIST_HEAD(&misc->list);
mutex_lock(&misc_mtx);
@@ -290,6 +302,8 @@ void misc_deregister(struct miscdevice *misc)
if (misc->minor > MISC_DYNAMIC_MINOR)
misc->minor = MISC_DYNAMIC_MINOR;
mutex_unlock(&misc_mtx);
+
+ revocable_provider_revoke(misc->rp);
}
EXPORT_SYMBOL(misc_deregister);
diff --git a/include/linux/miscdevice.h b/include/linux/miscdevice.h
index 7d0aa718499c..85fac108e485 100644
--- a/include/linux/miscdevice.h
+++ b/include/linux/miscdevice.h
@@ -92,6 +92,8 @@ struct miscdevice {
const struct attribute_group **groups;
const char *nodename;
umode_t mode;
+ bool revocable;
+ struct revocable_provider *rp;
};
extern int misc_register(struct miscdevice *misc);
--
2.48.1
next prev parent reply other threads:[~2025-11-06 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 15:27 [PATCH v6 0/3] platform/chrome: Fix an UAF via replacing fops Tzung-Bi Shih
2025-11-06 15:27 ` [PATCH v6 1/3] revocable: Add fops replacement Tzung-Bi Shih
2025-11-06 15:47 ` Jason Gunthorpe
2025-11-07 5:07 ` Tzung-Bi Shih
2025-11-07 14:15 ` Jason Gunthorpe
2025-11-10 6:28 ` Tzung-Bi Shih
2025-11-17 15:33 ` Jason Gunthorpe
2025-11-06 17:11 ` kernel test robot
2025-11-07 3:39 ` kernel test robot
2025-11-06 15:27 ` Tzung-Bi Shih [this message]
2025-11-06 15:27 ` [PATCH v6 3/3] platform/chrome: cros_ec_chardev: Secure cros_ec_device via revocable Tzung-Bi Shih
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=20251106152712.11850-3-tzungbi@kernel.org \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=brgl@bgdev.pl \
--cc=chrome-platform@lists.linux.dev \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@nvidia.com \
--cc=laurent.pinchart@ideasonboard.com \
--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=simona.vetter@ffwll.ch \
--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 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).