From: Viresh Kumar <viresh.kumar@linaro.org>
To: Mehmet Koseoglu <mehmet.mkoseoglu@gmail.com>
Cc: rafael@kernel.org, ojeda@kernel.org, boqun@kernel.org,
gary@garyguo.net, bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, daniel.almeida@collabora.com, tamird@kernel.org,
acourbot@nvidia.com, work@onurozkan.dev,
linux-pm@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org, xuyiwen14@gmail.com,
miguel.ojeda.sandonis@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH v4] rust: cpufreq: reject NULL from cpufreq_cpu_get()
Date: Mon, 5 Oct 2026 09:26:15 +0530 [thread overview]
Message-ID: <asMf3xK5XiWdEiDA@vireshk-B250M-D3H> (raw)
In-Reply-To: <20261001102213.45437-1-mehmet.mkoseoglu@gmail.com>
On 01-10-26, 13:19, Mehmet Koseoglu wrote:
> cpufreq_cpu_get() returns either a referenced policy or NULL.
> PolicyCpu::from_cpu() passed its return value to from_err_ptr(), which
> rejects ERR_PTR values but accepts NULL.
>
> If the lookup fails, Policy::from_raw_mut() therefore constructs a mutable
> reference from NULL. Dropping the resulting PolicyCpu then passes the
> invalid pointer to cpufreq_cpu_put(), causing an oops in kobject_put().
>
> Reject NULL with NonNull before constructing the Policy reference. Return
> ENODEV instead.
>
> A KUnit negative-control run reproduced the oops with the original
> conversion. The same test passed with this change. The reproducer is
> available on request.
>
> Fixes: 6ebdd7c93177 ("rust: cpufreq: Extend abstractions for policy and driver ops")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Mehmet Koseoglu <mehmet.mkoseoglu@gmail.com>
> Reviewed-by: Onur Özkan <work@onurozkan.dev>
> Reviewed-by: spidermana <xuyiwen14@gmail.com>
Applied. Thanks.
--
viresh
prev parent reply other threads:[~2026-10-05 3:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 16:10 [PATCH v3] rust: cpufreq: reject NULL from cpufreq_cpu_get() Mehmet Koseoglu
2026-08-29 19:52 ` Onur Özkan
2026-09-28 16:22 ` spidermana
2026-09-28 17:17 ` Miguel Ojeda
2026-09-29 9:55 ` spidermana
2026-10-01 6:25 ` Viresh Kumar
2026-10-01 9:49 ` Mehmet Koseoglu
2026-10-01 9:58 ` Viresh Kumar
2026-10-01 10:19 ` [PATCH v4] " Mehmet Koseoglu
2026-10-05 3:56 ` Viresh Kumar [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=asMf3xK5XiWdEiDA@vireshk-B250M-D3H \
--to=viresh.kumar@linaro.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mehmet.mkoseoglu@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
--cc=xuyiwen14@gmail.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