From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Zhang Rui <rui.zhang@intel.com>, rafael.j.wysocki@intel.com
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
lukasz.luba@arm.com, srinivas.pandruvada@intel.com
Subject: Re: [PATCH] thermal/netlink: Prevent Userspace Segmentation Fault by Adjusting UAPI Header
Date: Tue, 11 Feb 2025 09:01:53 +0100 [thread overview]
Message-ID: <15de0ea2-eae6-4f23-9ca1-15836ec95cca@linaro.org> (raw)
In-Reply-To: <20250208074907.5679-1-rui.zhang@intel.com>
On 08/02/2025 08:49, Zhang Rui wrote:
> The intel-lpmd tool [1], which uses the THERMAL_GENL_ATTR_CPU_CAPABILITY
> attribute to receive HFI events from kernel space, encounters a
> segmentation fault after commit 1773572863c4 ("thermal: netlink: Add the
> commands and the events for the thresholds").
>
> The issue arises because the THERMAL_GENL_ATTR_CPU_CAPABILITY raw value
> was changed while intel_lpmd still uses the old value.
>
> Although intel_lpmd can be updated to check the THERMAL_GENL_VERSION and
> use the appropriate THERMAL_GENL_ATTR_CPU_CAPABILITY value, the commit
> itself is questionable. The commit introduced a new element in the
> middle of enum thermal_genl_attr, which affects many existing attributes
> and introduces potential risks and unnecessary maintenance burdens for
> userspace thermal netlink event users.
>
> Solve the issue by moving the newly introduced
> THERMAL_GENL_ATTR_TZ_PREV_TEMP attribute to the end of the
> enum thermal_genl_attr. This ensures that all existing thermal generic
> netlink attributes remain unaffected.
>
> Link: https://github.com/intel/intel-lpmd [1]
> Fixes: 1773572863c4 ("thermal: netlink: Add the commands and the events for the thresholds")
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>
> ---
Right, thanks for the fix
Reviewed-by: Daniel Lezcano <daniel.lezcano@linaro.org>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2025-02-11 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 7:49 Zhang Rui
2025-02-11 8:01 ` Daniel Lezcano [this message]
2025-02-11 19:56 ` Rafael J. Wysocki
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=15de0ea2-eae6-4f23-9ca1-15836ec95cca@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@intel.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
all inboxes | Powered by JetHome®