[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d394fb33-2fe4-4a5a-b6fa-7f5598aede9b@linaro.org>
Date: Fri, 11 Oct 2024 10:41:30 +0100
From: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
To: Johan Hovold <johan@...nel.org>, Robert Foss <rfoss@...nel.org>,
Todor Tomov <todor.too@...il.com>
Cc: Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org>,
linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: camss NULL-deref on power on with 6.12-rc2
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
Powered by blists - more mailing lists