From: "Nuno Sá" <nuno.sa@analog.com>
To: <linux-clk@vger.kernel.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Subject: [PATCH 0/2] clk: fix possible use after free
Date: Wed, 12 Jun 2024 11:34:24 +0200 [thread overview]
Message-ID: <20240612-dev-clk-misc-v1-0-7ad8b58f2ea2@analog.com> (raw)
The first patch is fixing a possible use after free in case a clk
provider is removed before it's consumer (more details on the commit
message.
The second patch is a straightforward replacement of the open coded
hlist_del(&clk->clks_node) -> clk_core_unlink_consumer(clk)
---
Nuno Sá (2):
clk: fix clk not being unlinked from consumers list
clk: use clk_core_unlink_consumer() helper
drivers/clk/clk.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
---
base-commit: 5029c56be4bab3bce7db6d9595b0bbd171a5b154
change-id: 20240611-dev-clk-misc-a9e401b25032
--
Thanks!
- Nuno Sá
next reply other threads:[~2024-06-12 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 9:34 Nuno Sá [this message]
2024-06-12 9:34 ` [PATCH 1/2] clk: fix clk not being unlinked from consumers list Nuno Sá
2024-06-12 9:34 ` [PATCH 2/2] clk: use clk_core_unlink_consumer() helper Nuno Sá
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=20240612-dev-clk-misc-v1-0-7ad8b58f2ea2@analog.com \
--to=nuno.sa@analog.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
/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