From: Tzung-Bi Shih <tzungbi@kernel.org>
To: bleung@chromium.org
Cc: tzungbi@kernel.org, dawidn@google.com, chrome-platform@lists.linux.dev
Subject: [PATCH 0/2] platform/chrome: cros_ec_chardev: To be ec_dev registered-aware
Date: Mon, 21 Jul 2025 04:50:07 +0000 [thread overview]
Message-ID: <20250721045009.2737376-1-tzungbi@kernel.org> (raw)
Userland programs may wait forever for MKBP events after the underlying
struct cros_ec_device has been unregistered. The series tries to return
appropriate errors when detecting such possibilities.
The 1st patch is a clean-up.
The 2nd patch fixes the issue via checking the ec_dev's availability in fops.
The series applies after
"[v3,0/8] platform/chrome: cros_ec_chardev: Fix a possible UAF"
(https://patchwork.kernel.org/project/chrome-platform/cover/20250721044456.2736300-1-tzungbi@kernel.org/).
Tzung-Bi Shih (2):
platform/chrome: cros_ec_chardev: Don't use wait queue's lock
platform/chrome: cros_ec_chardev: Check ec_dev's availability in fops
drivers/platform/chrome/cros_ec_chardev.c | 49 +++++++++++++----------
1 file changed, 28 insertions(+), 21 deletions(-)
--
2.50.0.727.gbf7dc18ff4-goog
next reply other threads:[~2025-07-21 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 4:50 Tzung-Bi Shih [this message]
2025-07-21 4:50 ` [PATCH 1/2] platform/chrome: cros_ec_chardev: Don't use wait queue's lock Tzung-Bi Shih
2025-07-21 4:50 ` [PATCH 2/2] platform/chrome: cros_ec_chardev: Check ec_dev's availability in fops 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=20250721045009.2737376-1-tzungbi@kernel.org \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dawidn@google.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