From: patchwork-bot+chrome-platform@kernel.org
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: bleung@chromium.org, groeck@chromium.org,
chrome-platform@lists.linux.dev
Subject: Re: [RESEND PATCH v2] platform/chrome: cros_ec_debugfs: detach log reader wq from devm
Date: Thu, 31 Mar 2022 16:50:11 +0000 [thread overview]
Message-ID: <164874541153.10400.1381918250182288340.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220209051130.386175-1-tzungbi@google.com>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Benson Leung <bleung@chromium.org>:
On Wed, 9 Feb 2022 13:11:30 +0800 you wrote:
> Debugfs console_log uses devm memory (e.g. debug_info in
> cros_ec_console_log_poll()). However, lifecycles of device and debugfs
> are independent. An use-after-free issue is observed if userland
> program operates the debugfs after the memory has been freed.
>
> The call trace:
> do_raw_spin_lock
> _raw_spin_lock_irqsave
> remove_wait_queue
> ep_unregister_pollwait
> ep_remove
> do_epoll_ctl
>
> [...]
Here is the summary with links:
- [RESEND,v2] platform/chrome: cros_ec_debugfs: detach log reader wq from devm
https://git.kernel.org/chrome-platform/c/a9e896f70fbe
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-03-31 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 5:11 [RESEND PATCH v2] platform/chrome: cros_ec_debugfs: detach log reader wq from devm Tzung-Bi Shih
2022-02-09 16:38 ` Guenter Roeck
2022-02-09 21:30 ` Prashant Malani
2022-02-10 3:11 ` Tzung-Bi Shih
2022-02-18 19:28 ` Benson Leung
2022-02-18 19:30 ` patchwork-bot+chrome-platform
2022-03-31 16:50 ` patchwork-bot+chrome-platform [this message]
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=164874541153.10400.1381918250182288340.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=tzungbi@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