All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Wang" <00107082@163.com>
To: "Linus Walleij" <linus.walleij@linaro.org>
Cc: "Kees Cook" <kees@kernel.org>,
	brgl@bgdev.pl, tglx@linutronix.de,  linux-kernel@vger.kernel.org,
	linux-gpio@vger.kernel.org,  geert@linux-m68k.org
Subject: Re: [PATCH] Fix a potential abuse of seq_printf() format string in drivers
Date: Wed, 20 Nov 2024 17:00:41 +0800 (CST)	[thread overview]
Message-ID: <65fc7014.91c4.19348cd68a0.Coremail.00107082@163.com> (raw)
In-Reply-To: <CACRpkdZ0zwn0908LDqrfQJtF7M-WRcKA4qdJdwSXZNzm0L47CA@mail.gmail.com>


At 2024-11-20 15:35:38, "Linus Walleij" <linus.walleij@linaro.org> wrote:
>On Wed, Nov 20, 2024 at 6:31 AM David Wang <00107082@163.com> wrote:
>
>> Using device name as format string of seq_printf() is proned to
>> "Format string attack", opens possibility for exploitation.
>> Seq_puts() is safer and more efficient.
>>
>> Signed-off-by: David Wang <00107082@163.com>
>
>Okay better get Kees' eye on this, he looks after string vulnerabilities.
>(But I think you're right.)
>
>>  drivers/gpio/gpio-aspeed-sgpio.c            | 2 +-
>>  drivers/gpio/gpio-aspeed.c                  | 2 +-
>>  drivers/gpio/gpio-ep93xx.c                  | 2 +-
>>  drivers/gpio/gpio-hlwd.c                    | 2 +-
>>  drivers/gpio/gpio-mlxbf2.c                  | 2 +-
>>  drivers/gpio/gpio-omap.c                    | 2 +-
>>  drivers/gpio/gpio-pca953x.c                 | 2 +-
>>  drivers/gpio/gpio-pl061.c                   | 2 +-
>>  drivers/gpio/gpio-tegra.c                   | 2 +-
>>  drivers/gpio/gpio-tegra186.c                | 2 +-
>>  drivers/gpio/gpio-tqmx86.c                  | 2 +-
>>  drivers/gpio/gpio-visconti.c                | 2 +-
>>  drivers/gpio/gpio-xgs-iproc.c               | 2 +-
>>  drivers/irqchip/irq-gic.c                   | 2 +-
>>  drivers/irqchip/irq-mvebu-pic.c             | 2 +-
>>  drivers/irqchip/irq-versatile-fpga.c        | 2 +-
>>  drivers/pinctrl/bcm/pinctrl-iproc-gpio.c    | 2 +-
>>  drivers/pinctrl/mvebu/pinctrl-armada-37xx.c | 2 +-
>>  drivers/pinctrl/pinctrl-mcp23s08.c          | 2 +-
>>  drivers/pinctrl/pinctrl-stmfx.c             | 2 +-
>>  drivers/pinctrl/pinctrl-sx150x.c            | 2 +-
>>  drivers/pinctrl/renesas/pinctrl-rzg2l.c     | 2 +-
>
>Can you split this in three patches per-subsystem?
>One for gpio, one for irqchip and one for pinctrl?
>
>Then send to each subsystem maintainer and CC kees on
>each.
>
>I'm just the pinctrl maintainer. The rest can be found with
>scripts/get_maintainer.pl.

Thanks for the review, I will send a patchset later.


>
>Yours,
>Linus Walleij


Thanks
David

  reply	other threads:[~2024-11-20  9:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20  5:30 [PATCH] Fix a potential abuse of seq_printf() format string in drivers David Wang
2024-11-20  7:35 ` Linus Walleij
2024-11-20  9:00   ` David Wang [this message]
2024-11-20 18:12   ` Kees Cook
2024-11-20 19:28     ` Greg Kroah-Hartman
2024-11-22  4:38       ` Kees Cook
2024-11-22 14:35         ` Greg Kroah-Hartman
2024-11-22 19:54 ` Thomas Gleixner

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=65fc7014.91c4.19348cd68a0.Coremail.00107082@163.com \
    --to=00107082@163.com \
    --cc=brgl@bgdev.pl \
    --cc=geert@linux-m68k.org \
    --cc=kees@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.