mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Xiaoke Wang <xkernel.wang@foxmail.com>
Cc: lars@metafoo.de, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: dummy: iio_simple_dummy: check the return value of kstrdup()
Date: Thu, 16 Dec 2021 16:30:37 +0000	[thread overview]
Message-ID: <20211216163019.570d6aed@jic23-huawei> (raw)
In-Reply-To: <tencent_4014A4E1394AA4FF7620EBCC47B9701C9D08@qq.com>

On Mon, 13 Dec 2021 17:18:21 +0800
Xiaoke Wang <xkernel.wang@foxmail.com> wrote:

> kstrdup() is also a memory allocation-related function, it return NULL
> when some memory errors happen. So it is better to check the return
> value of it so to catch the memory error in time.
> 
> Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
Hi.

Good spot, but there is more to do to fix this.  The error path doesn't
clear up the allocation if we get a failure later in this function.

So should have a kfree() error case.

Also, a side note is the error labels in that function are terrible!
(given I probably wrote them I can be rude about them:) 

So cleaning that up as well might be a good thing to do whilst here.
Make them reflect what they are cleaning up rather that the crazy
naming there currently.  When error_ret label goes to a place where
it does more than just return it's not good.

Also drop the first error_kzalloc label and goto in favour of direct return.

Great if you can tidy this up, if not I'll do it at somepoint.

Jonathan

> ---
>  drivers/iio/dummy/iio_simple_dummy.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/iio/dummy/iio_simple_dummy.c b/drivers/iio/dummy/iio_simple_dummy.c
> index c0b7ef9..a5e8071 100644
> --- a/drivers/iio/dummy/iio_simple_dummy.c
> +++ b/drivers/iio/dummy/iio_simple_dummy.c
> @@ -616,6 +616,10 @@ static struct iio_sw_device *iio_dummy_probe(const char *name)
>  	 *    indio_dev->name = spi_get_device_id(spi)->name;
>  	 */
>  	indio_dev->name = kstrdup(name, GFP_KERNEL);
> +	if (!indio_dev->name) {
> +		ret = -ENOMEM;
> +		goto error_free_device;
> +	}
>  
>  	/* Provide description of available channels */
>  	indio_dev->channels = iio_dummy_channels;


      reply	other threads:[~2021-12-16 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  9:18 Xiaoke Wang
2021-12-16 16:30 ` Jonathan Cameron [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=20211216163019.570d6aed@jic23-huawei \
    --to=jic23@jic23.retrosnub.co.uk \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xkernel.wang@foxmail.com \
    /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®