Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: Hangyu Hua <hbh25y@gmail.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: bjorn.andersson@linaro.org, arnaud.pouliquen@foss.st.com,
	linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rpmsg: virtio: fix possible double free in rpmsg_probe()
Date: Tue, 26 Apr 2022 09:40:33 +0800	[thread overview]
Message-ID: <60d80bae-d229-0aa2-8c63-025754ab3438@gmail.com> (raw)
In-Reply-To: <20220425165552.GB1917807@p14s>

On 2022/4/26 00:55, Mathieu Poirier wrote:
> On Mon, Apr 18, 2022 at 05:31:44PM +0800, Hangyu Hua wrote:
>> vch will be free in virtio_rpmsg_release_device() when
>> rpmsg_ns_register_device() fails. There is no need to call kfree() again.
>>
>> Fix this by changing error path from free_vch to free_ctrldev.
>>
>> Fixes: c486682ae1e2 ("rpmsg: virtio: Register the rpmsg_char device")
>> Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
>> ---
>>   drivers/rpmsg/virtio_rpmsg_bus.c | 4 +---
>>   1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
>> index 3ede25b1f2e4..603233f0686e 100644
>> --- a/drivers/rpmsg/virtio_rpmsg_bus.c
>> +++ b/drivers/rpmsg/virtio_rpmsg_bus.c
>> @@ -973,7 +973,7 @@ static int rpmsg_probe(struct virtio_device *vdev)
>>   
>>   		err = rpmsg_ns_register_device(rpdev_ns);
>>   		if (err)
>> -			goto free_vch;
> 
> Please add a comment that highlights where 'vch' will be free'd to avoid
> receiving patches that will introduce another kfree().  Same for your other
> patch.
> 
> In the next revision please use a cover letter and add Arnaud's patches to it.
> 
> Thanks,
> Mathieu
> 

Thanks! I will send a v2 later.

>> +			goto free_ctrldev;
>>   	}
>>   
>>   	/*
>> @@ -997,8 +997,6 @@ static int rpmsg_probe(struct virtio_device *vdev)
>>   
>>   	return 0;
>>   
>> -free_vch:
>> -	kfree(vch);
>>   free_ctrldev:
>>   	rpmsg_virtio_del_ctrl_dev(rpdev_ctrl);
>>   free_coherent:
>> -- 
>> 2.25.1
>>

      reply	other threads:[~2022-04-26  1:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18  9:31 [PATCH] rpmsg: virtio: fix possible double free in rpmsg_probe() Hangyu Hua
2022-04-22 15:29 ` Arnaud POULIQUEN
2022-04-25 16:55 ` Mathieu Poirier
2022-04-26  1:40   ` Hangyu Hua [this message]

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=60d80bae-d229-0aa2-8c63-025754ab3438@gmail.com \
    --to=hbh25y@gmail.com \
    --cc=arnaud.pouliquen@foss.st.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@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