From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Benoit Parrot <bparrot@ti.com>, Hans Verkuil <hverkuil@xs4all.nl>
Cc: <linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [Patch] media: ti-vpe: cal: fix a kernel oops when unloading module
Date: Wed, 4 Mar 2020 10:41:16 +0200 [thread overview]
Message-ID: <f7f6dd87-147f-b9e9-aaa7-c063a8f3c11e@ti.com> (raw)
In-Reply-To: <4010c13f-6a32-f3c3-5b6d-62a4e3782c64@ti.com>
On 04/03/2020 10:40, Tomi Valkeinen wrote:
> On 03/03/2020 19:26, Benoit Parrot wrote:
>> After the switch to use v4l2_async_notifier_add_subdev() and
>> v4l2_async_notifier_cleanup(), unloading the ti_cal module would casue a
>> kernel oops.
>>
>> This was root cause to the fact that v4l2_async_notifier_cleanup() tries
>> to kfree the asd pointer passed into v4l2_async_notifier_add_subdev().
>>
>> In our case the asd reference was from a statically allocated struct.
>> So in effect v4l2_async_notifier_cleanup() was trying to free a pointer
>> that was not kalloc.
>>
>> So here we switch to using a kzalloc struct instead of a static one.
>>
>> Fixes: d079f94c9046 ("media: platform: Switch to v4l2_async_notifier_add_subdev")
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Benoit Parrot <bparrot@ti.com>
>> ---
>> drivers/media/platform/ti-vpe/cal.c | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/media/platform/ti-vpe/cal.c b/drivers/media/platform/ti-vpe/cal.c
>> index 6d4cbb8782ed..18fe2cb9dd17 100644
>> --- a/drivers/media/platform/ti-vpe/cal.c
>> +++ b/drivers/media/platform/ti-vpe/cal.c
>> @@ -372,8 +372,6 @@ struct cal_ctx {
>> struct v4l2_subdev *sensor;
>> struct v4l2_fwnode_endpoint endpoint;
>> - struct v4l2_async_subdev asd;
>> -
>> struct v4l2_fh fh;
>> struct cal_dev *dev;
>> struct cc_data *cc;
>> @@ -2032,7 +2030,6 @@ static int of_cal_create_instance(struct cal_ctx *ctx, int inst)
>> parent = pdev->dev.of_node;
>> - asd = &ctx->asd;
>> endpoint = &ctx->endpoint;
>> ep_node = NULL;
>> @@ -2040,6 +2037,10 @@ static int of_cal_create_instance(struct cal_ctx *ctx, int inst)
>> sensor_node = NULL;
>> ret = -EINVAL;
>> + asd = kzalloc(sizeof(*asd), GFP_KERNEL);
>> + if (!asd)
>> + goto cleanup_exit;
>> +
>> ctx_dbg(3, ctx, "Scanning Port node for csi2 port: %d\n", inst);
>> for (index = 0; index < CAL_NUM_CSI2_PORTS; index++) {
>> port = of_get_next_port(parent, port);
>>
>
> Thanks, this fixes the crash for me.
>
> It does look a bit odd that something is allocated with kzalloc, and then it's freed somewhere
> inside v4l2_async_notifier_cleanup, though. But if that's how it supposed to be used, looks fine to me.
Well, sent that a few seconds too early... With this patch, I see kmemleaks.
Tomi
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2020-03-04 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 17:26 [Patch] media: ti-vpe: cal: fix a kernel oops when unloading module Benoit Parrot
2020-03-04 8:40 ` Tomi Valkeinen
2020-03-04 8:41 ` Tomi Valkeinen [this message]
2020-03-04 9:22 ` Tomi Valkeinen
2020-03-04 13:10 ` Benoit Parrot
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=f7f6dd87-147f-b9e9-aaa7-c063a8f3c11e@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--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