From: Phil Reid <preid@electromag.com.au>
To: Laura Abbott <labbott@redhat.com>,
Linus Walleij <linus.walleij@linaro.org>,
Kees Cook <keescook@chromium.org>,
Patrice Chotard <patrice.chotard@st.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH v3] gpio: Remove VLA from stmpe driver
Date: Thu, 29 Mar 2018 08:07:05 +0800 [thread overview]
Message-ID: <e676f8fc-e619-ac7e-a5e0-8682197c7b9b@electromag.com.au> (raw)
In-Reply-To: <20180328175957.23904-1-labbott@redhat.com>
On 29/03/2018 01:59, Laura Abbott wrote:
> The new challenge is to remove VLAs from the kernel
> (see https://lkml.org/lkml/2018/3/7/621)
>
> The number of GPIOs on the supported chips is fairly small
> so stack allocate to a known upper bound and spit out a warning
> if any new chips have more gpios.
>
> Signed-off-by: Laura Abbott <labbott@redhat.com>
> ---
> v3: Split this off from the rest of the series since some of the
> patches had been picked up. Switched to just hardcoding an upper
> bound for the stack array since it's only a few extra bytes
> of stack space.
> ---
> drivers/gpio/gpio-stmpe.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpio/gpio-stmpe.c b/drivers/gpio/gpio-stmpe.c
> index f8d7d1cd8488..8d6a5a7e612d 100644
> --- a/drivers/gpio/gpio-stmpe.c
> +++ b/drivers/gpio/gpio-stmpe.c
> @@ -363,13 +363,15 @@ static struct irq_chip stmpe_gpio_irq_chip = {
> .irq_set_type = stmpe_gpio_irq_set_type,
> };
>
> +#define MAX_GPIOS 24
> +
> static irqreturn_t stmpe_gpio_irq(int irq, void *dev)
> {
> struct stmpe_gpio *stmpe_gpio = dev;
> struct stmpe *stmpe = stmpe_gpio->stmpe;
> u8 statmsbreg;
> int num_banks = DIV_ROUND_UP(stmpe->num_gpios, 8);
> - u8 status[num_banks];
> + u8 status[DIV_ROUND_UP(MAX_GPIOS, 8)];
> int ret;
> int i;
>
> @@ -434,6 +436,11 @@ static int stmpe_gpio_probe(struct platform_device *pdev)
> struct stmpe_gpio *stmpe_gpio;
> int ret, irq;
>
> + if (stmpe->num_gpios > MAX_GPIOS) {
> + dev_err(&pdev->dev, "Need to increase maximum GPIO number\n");
> + return -EINVAL;
> + }
> +
> stmpe_gpio = kzalloc(sizeof(*stmpe_gpio), GFP_KERNEL);
> if (!stmpe_gpio)
> return -ENOMEM;
>
FWIW
Reviewed-by: Phil Reid <preid@electromag.com.au>
--
Regards
Phil Reid
next prev parent reply other threads:[~2018-03-29 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 17:59 Laura Abbott
2018-03-29 0:07 ` Phil Reid [this message]
2018-05-23 22:51 ` Kees Cook
2018-05-24 8:23 ` Linus Walleij
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=e676f8fc-e619-ac7e-a5e0-8682197c7b9b@electromag.com.au \
--to=preid@electromag.com.au \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.chotard@st.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®