The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Rob Herring <robh@kernel.org>,
	linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH] uio: uio_dmem_genirq: check the return value of devm_kasprintf()
Date: Fri, 10 Jan 2025 09:52:04 +0100	[thread overview]
Message-ID: <2025011054-promptly-earful-3631@gregkh> (raw)
In-Reply-To: <CAMRc=MfMehi+kU=xopv6Ued2mYyZk5wrv1i_OBYMC0XW8aPdMQ@mail.gmail.com>

On Fri, Jan 10, 2025 at 09:41:16AM +0100, Bartosz Golaszewski wrote:
> On Mon, Dec 2, 2024 at 7:17 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> >
> > From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> >
> > devm_kasprintf() can fail so check its return value and bail-out on no
> > memory.
> >
> > Fixes: 52e2dc2ce2d8 ("uio: Convert a few more users to using %pOFn instead of device_node.name")
> > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> > ---
> >  drivers/uio/uio_dmem_genirq.c | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/uio/uio_dmem_genirq.c b/drivers/uio/uio_dmem_genirq.c
> > index c70dd81bfc61f..31aa75110ba59 100644
> > --- a/drivers/uio/uio_dmem_genirq.c
> > +++ b/drivers/uio/uio_dmem_genirq.c
> > @@ -167,6 +167,8 @@ static int uio_dmem_genirq_probe(struct platform_device *pdev)
> >                 }
> >                 uioinfo->name = devm_kasprintf(&pdev->dev, GFP_KERNEL, "%pOFn",
> >                                                pdev->dev.of_node);
> > +               if (!uioinfo->name)
> > +                       return -ENOMEM;
> >                 uioinfo->version = "devicetree";
> >         }
> >
> > --
> > 2.45.2
> >
> 
> Gentle ping?

It's in my queue.  The "fix up an error path" patches are on the bottom
of all my reviews as generally they are a pain to review as it takes a
lot of out-of-band code reading.  And they have a bad history of being
wrong.  And they are really low on the priority as they really can't be
triggered :)

So I'll get to them, but realize that they are a pain to deal with...

thanks,

greg k-h

      reply	other threads:[~2025-01-10  8:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 18:17 [PATCH] uio: uio_dmem_genirq: check the return value of devm_kasprintf() Bartosz Golaszewski
2025-01-10  8:41 ` Bartosz Golaszewski
2025-01-10  8:52   ` Greg Kroah-Hartman [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=2025011054-promptly-earful-3631@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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