From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Johan Hovold <johan@kernel.org>, Robert Foss <rfoss@kernel.org>,
Todor Tomov <todor.too@gmail.com>
Cc: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: camss NULL-deref on power on with 6.12-rc2
Date: Fri, 11 Oct 2024 10:41:30 +0100 [thread overview]
Message-ID: <d394fb33-2fe4-4a5a-b6fa-7f5598aede9b@linaro.org> (raw)
In-Reply-To: <Zwjw6XfVWcufMlqM@hovoldconsulting.com>
On 11/10/2024 10:33, Johan Hovold wrote:
> Hi,
>
> This morning I hit the below NULL-deref in camss when booting a 6.12-rc2
> kernel on the Lenovo ThinkPad X13s.
>
> I booted the same kernel another 50 times without hitting it again it so
> it may not be a regression, but simply an older, hard to hit bug.
>
> Hopefully you can figure out what went wrong from just staring at the
> oops and code.
>
> Johan
>
>
> [ 5.657860] ov5675 24-0010: failed to get HW configuration: -517
So this caused it, I guess the sensor failed to power up.
You've booted 50 times in a row and hit a corner case where the sensor
didn't power up leading to a NULL deference.
So, two bugs I'd say.
- What is the cirumcstance where the sensor doesn't power up
- What's the NULL either entity * or entity->pad I'd say.
<snip>
> [ 6.594915] Call trace:
> [ 6.594915] camss_find_sensor+0x20/0x74 [qcom_camss]
Hmm, not sure looking at what we have.
pad = &entity->pads[0];
if (!(pad->flags & MEDIA_PAD_FL_SINK))
return NULL;
Is pad guaranteed after entity->pads[0] ?
We dereference it like its guaranteed.
Anyway thanks for the report, should be enough start digging.
---
bod
next prev parent reply other threads:[~2024-10-11 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 9:33 Johan Hovold
2024-10-11 9:41 ` Bryan O'Donoghue [this message]
2024-10-11 9:54 ` Johan Hovold
2025-04-07 9:12 ` Johan Hovold
2025-04-07 9:58 ` Bryan O'Donoghue
2025-04-07 10:38 ` Johan Hovold
2025-04-07 11:01 ` Johan Hovold
2025-04-07 13:49 ` Johan Hovold
2025-08-24 20:42 ` Vladimir Zapolskiy
2025-08-29 9:15 ` Johan Hovold
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=d394fb33-2fe4-4a5a-b6fa-7f5598aede9b@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=johan@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rfoss@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.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®