From: Subbaraman Narayanamurthy <quic_subbaram@quicinc.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
"Nick Desaulniers" <ndesaulniers@google.com>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Collins <quic_collinsd@quicinc.com>,
Manaf Meethalavalappu Pallikunhi <quic_manafm@quicinc.com>,
Stable <stable@vger.kernel.org>
Subject: Re: [RESEND PATCH v2] thermal: Fix a NULL pointer dereference
Date: Fri, 5 Nov 2021 13:08:22 -0700 [thread overview]
Message-ID: <6fd1b6ca-15fc-757b-8755-7f8ec4110bcc@quicinc.com> (raw)
In-Reply-To: <CAJZ5v0j1TDe0ZiBg_ju-JDuCsBDb_exueRDUwCcJ6VD_=fbzjg@mail.gmail.com>
On 11/5/21 9:37 AM, Rafael J. Wysocki wrote:
> On Fri, Nov 5, 2021 at 5:19 PM Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>> On 05/11/2021 16:14, Rafael J. Wysocki wrote:
>>> On Fri, Nov 5, 2021 at 12:57 AM Subbaraman Narayanamurthy
>>> <quic_subbaram@quicinc.com> wrote:
>>>> of_parse_thermal_zones() parses the thermal-zones node and registers a
>>>> thermal_zone device for each subnode. However, if a thermal zone is
>>>> consuming a thermal sensor and that thermal sensor device hasn't probed
>>>> yet, an attempt to set trip_point_*_temp for that thermal zone device
>>>> can cause a NULL pointer dereference. Fix it.
>>>>
>>>> console:/sys/class/thermal/thermal_zone87 # echo 120000 > trip_point_0_temp
>>>> ...
>>>> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020
>>>> ...
>>>> Call trace:
>>>> of_thermal_set_trip_temp+0x40/0xc4
>>>> trip_point_temp_store+0xc0/0x1dc
>>>> dev_attr_store+0x38/0x88
>>>> sysfs_kf_write+0x64/0xc0
>>>> kernfs_fop_write_iter+0x108/0x1d0
>>>> vfs_write+0x2f4/0x368
>>>> ksys_write+0x7c/0xec
>>>> __arm64_sys_write+0x20/0x30
>>>> el0_svc_common.llvm.7279915941325364641+0xbc/0x1bc
>>>> do_el0_svc+0x28/0xa0
>>>> el0_svc+0x14/0x24
>>>> el0_sync_handler+0x88/0xec
>>>> el0_sync+0x1c0/0x200
>>>>
>>>> While at it, fix the possible NULL pointer dereference in other
>>>> functions as well: of_thermal_get_temp(), of_thermal_set_emul_temp(),
>>>> of_thermal_get_trend().
>>> Can the subject be more specific, please?
>>>
>>> The issue appears to be limited to the of_thermal_ family of
>>> functions, but the subject doesn't reflect that at all.
>>>
>>>> Suggested-by: David Collins <quic_collinsd@quicinc.com>
>>>> Signed-off-by: Subbaraman Narayanamurthy <quic_subbaram@quicinc.com>
>>> Daniel, any concerns regarding the code changes below?
>> I've a concern about the root cause but I did not have time to
>> investigate how to fix it nicely.
>>
>> thermal_of is responsible of introducing itself between the thermal core
>> code and the backend. So it defines the ops which in turn call the
>> sensor ops leading us to this problem.
>>
>> So, without a better solution, this fix can be applied until we rethink
>> the thermal_of approach.
>>
>> Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Thanks!
>
> I've queued it up for 5.16-rc as "thermal: Fix NULL pointer
> dereferences in of_thermal_ functions".
Thanks, Daniel and Rafael. So, I guess I don't need to send v3 with fixing commit subject right?
-Subbaraman
next prev parent reply other threads:[~2021-11-05 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 23:57 Subbaraman Narayanamurthy
2021-11-05 6:50 ` Greg KH
2021-11-05 20:06 ` Subbaraman Narayanamurthy
2021-11-05 15:14 ` Rafael J. Wysocki
2021-11-05 16:19 ` Daniel Lezcano
2021-11-05 16:37 ` Rafael J. Wysocki
2021-11-05 20:08 ` Subbaraman Narayanamurthy [this message]
2021-11-05 20:19 ` 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=6fd1b6ca-15fc-757b-8755-7f8ec4110bcc@quicinc.com \
--to=quic_subbaram@quicinc.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=quic_collinsd@quicinc.com \
--cc=quic_manafm@quicinc.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=stable@vger.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
all inboxes | Powered by JetHome®