From: Nicholas Mc Guire <der.herr@hofr.at>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: linux-gpio <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
sergio.paracuellos@gmail.com, linux-mediatek@lists.infradead.org,
hofrat@osadl.org, matthias.bgg@gmail.com,
arm-soc <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] gpio: mt7621: handle failure of devm_kasprintf()
Date: Wed, 21 Nov 2018 18:01:16 +0100 [thread overview]
Message-ID: <20181121170116.GA10656@osadl.at> (raw)
In-Reply-To: <CAMpxmJUNYWqk4PEKcZ5o5PMR3RhMhudK+Pf+Pfo64mvJ8ND2wQ@mail.gmail.com>
On Wed, Nov 21, 2018 at 05:43:43PM +0100, Bartosz Golaszewski wrote:
> ??r., 21 lis 2018 o 17:39 Nicholas Mc Guire <hofrat@osadl.org> napisa??(a):
> >
> > kasprintf() may return NULL on failure of internal allocation thus the
> > assigned label is not safe if not explicitly checked. On error
> > mediatek_gpio_bank_probe() returns negative values so -ENOMEM in the
> > (unlikely) failure case should be fine here.
> >
> > Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org>
> > Fixes: 4ba9c3afda41 ("gpio: mt7621: Add a driver for MT7621")
> > ---
> >
> > Problem located with experimental coccinelle script
> >
> > Patch was compile tested with: omega2p_defconfig, SOC_MT7621=y,
> > GPIOLIB=y, GPIO_MT7621=y
> >
> > Patch is against 4.20-rc3 (localversion-next is next-20181121)
> >
> > drivers/gpio/gpio-mt7621.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/gpio/gpio-mt7621.c b/drivers/gpio/gpio-mt7621.c
> > index d72af6f..42f0c67 100644
> > --- a/drivers/gpio/gpio-mt7621.c
> > +++ b/drivers/gpio/gpio-mt7621.c
> > @@ -244,6 +244,10 @@ mediatek_gpio_bank_probe(struct device *dev,
> > rg->chip.of_xlate = mediatek_gpio_xlate;
> > rg->chip.label = devm_kasprintf(dev, GFP_KERNEL, "%s-bank%d",
> > dev_name(dev), bank);
> > + if (!rg->chip.label) {
> > + dev_err(dev, "Could not allocate label\n");
>
> No need for an error message here, an -ENOMEM says enough.
>
I just thought its more consistent with the rest of
the code - and as it is a highly unlikely event it would
probably be hard to pinpoint as some of the other functions
can return -ENOMEM (but with a message).
....and the call site of mediatek_gpio_bank_probe() actually
currently ignores the return value so the -ENOMEM would go
unnoticed which is a bug as well - patch for that a bit later.
anyway fine with me - I´ll send a V2 and drop the dev_err() here.
thx!
hofrat
> Bart
>
> > + return -ENOMEM;
> > + }
> >
> > ret = devm_gpiochip_add_data(dev, &rg->chip, mtk);
> > if (ret < 0) {
> > --
> > 2.1.4
> >
prev parent reply other threads:[~2018-11-21 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 16:35 [PATCH] gpio: mt7621: handle failure of devm_kasprintf() Nicholas Mc Guire
2018-11-21 16:43 ` Bartosz Golaszewski
2018-11-21 17:01 ` Nicholas Mc Guire [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=20181121170116.GA10656@osadl.at \
--to=der.herr@hofr.at \
--cc=bgolaszewski@baylibre.com \
--cc=hofrat@osadl.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=sergio.paracuellos@gmail.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;
as well as URLs for NNTP newsgroup(s).