public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <andriy.shevchenko@linux.intel.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <Ludovic.Desroches@microchip.com>, <linus.walleij@linaro.org>,
	<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH v2 1/5] pinctrl: at91: use devm_kasprintf() to avoid potential leaks (part 2)
Date: Tue, 14 Feb 2023 11:05:05 +0000	[thread overview]
Message-ID: <b64bd722-5ce7-9cca-9547-be84d0ef381a@microchip.com> (raw)
In-Reply-To: <20230213154532.32992-2-andriy.shevchenko@linux.intel.com>

On 13.02.2023 17:45, Andy Shevchenko wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> Use devm_kasprintf() instead of kasprintf() to avoid any potential
> leaks. At the moment drivers have no remove functionality hence
> there is no need for fixes tag.
> 
> While at it, switch to use devm_kasprintf_strarray().
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
Tested-by: Claudiu Beznea <claudiu.beznea@microchip.com>


> ---
>  drivers/pinctrl/pinctrl-at91.c | 23 +++++++++++++++++------
>  1 file changed, 17 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/pinctrl/pinctrl-at91.c b/drivers/pinctrl/pinctrl-at91.c
> index 2e7debb905d5..5c01765c7a2a 100644
> --- a/drivers/pinctrl/pinctrl-at91.c
> +++ b/drivers/pinctrl/pinctrl-at91.c
> @@ -18,6 +18,7 @@
>  #include <linux/pm.h>
>  #include <linux/seq_file.h>
>  #include <linux/slab.h>
> +#include <linux/string_helpers.h>
> 
>  /* Since we request GPIOs from ourself */
>  #include <linux/pinctrl/consumer.h>
> @@ -1371,6 +1372,7 @@ static int at91_pinctrl_probe_dt(struct platform_device *pdev,
> 
>  static int at91_pinctrl_probe(struct platform_device *pdev)
>  {
> +       struct device *dev = &pdev->dev;
>         struct at91_pinctrl *info;
>         struct pinctrl_pin_desc *pdesc;
>         int ret, i, j, k;
> @@ -1394,9 +1396,19 @@ static int at91_pinctrl_probe(struct platform_device *pdev)
>                 return -ENOMEM;
> 
>         for (i = 0, k = 0; i < gpio_banks; i++) {
> +               char **names;
> +
> +               names = devm_kasprintf_strarray(dev, "pio", MAX_NB_GPIO_PER_BANK);
> +               if (!names)
> +                       return -ENOMEM;
> +
>                 for (j = 0; j < MAX_NB_GPIO_PER_BANK; j++, k++) {
> +                       char *name = names[j];
> +
> +                       strreplace(name, '-', i + 'A');
> +
>                         pdesc->number = k;
> -                       pdesc->name = kasprintf(GFP_KERNEL, "pio%c%d", i + 'A', j);
> +                       pdesc->name = name;
>                         pdesc++;
>                 }
>         }
> @@ -1797,7 +1809,8 @@ static const struct of_device_id at91_gpio_of_match[] = {
> 
>  static int at91_gpio_probe(struct platform_device *pdev)
>  {
> -       struct device_node *np = pdev->dev.of_node;
> +       struct device *dev = &pdev->dev;
> +       struct device_node *np = dev->of_node;
>         struct at91_gpio_chip *at91_chip = NULL;
>         struct gpio_chip *chip;
>         struct pinctrl_gpio_range *range;
> @@ -1866,16 +1879,14 @@ static int at91_gpio_probe(struct platform_device *pdev)
>                         chip->ngpio = ngpio;
>         }
> 
> -       names = devm_kcalloc(&pdev->dev, chip->ngpio, sizeof(char *),
> -                            GFP_KERNEL);
> -
> +       names = devm_kasprintf_strarray(dev, "pio", chip->ngpio);
>         if (!names) {
>                 ret = -ENOMEM;
>                 goto clk_enable_err;
>         }
> 
>         for (i = 0; i < chip->ngpio; i++)
> -               names[i] = devm_kasprintf(&pdev->dev, GFP_KERNEL, "pio%c%d", alias_idx + 'A', i);
> +               strreplace(names[i], '-', alias_idx + 'A');
> 
>         chip->names = (const char *const *)names;
> 
> --
> 2.39.1
> 


  reply	other threads:[~2023-02-14 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 15:45 [PATCH v2 0/5] pinctrl: at91: Cleanups Andy Shevchenko
2023-02-13 15:45 ` [PATCH v2 1/5] pinctrl: at91: use devm_kasprintf() to avoid potential leaks (part 2) Andy Shevchenko
2023-02-14 11:05   ` Claudiu.Beznea [this message]
2023-02-13 15:45 ` [PATCH v2 2/5] pinctrl: at91: Don't mix non-devm calls with devm ones Andy Shevchenko
2023-02-14 11:05   ` Claudiu.Beznea
2023-02-13 15:45 ` [PATCH v2 3/5] pinctrl: at91: Use of_device_get_match_data() Andy Shevchenko
2023-02-14 11:05   ` Claudiu.Beznea
2023-02-13 15:45 ` [PATCH v2 4/5] pinctrl: at91: Use dev_err_probe() instead of custom messaging Andy Shevchenko
2023-02-14 11:07   ` Claudiu.Beznea
2023-02-13 15:45 ` [PATCH v2 5/5] pinctrl: at91: Utilise temporary variable for struct device Andy Shevchenko
2023-02-14 11:11   ` Claudiu.Beznea
2023-02-15 13:38     ` Andy Shevchenko

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=b64bd722-5ce7-9cca-9547-be84d0ef381a@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@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