mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Tycho Andersen <tycho@tycho.ws>, Joe Perches <joe@perches.com>
Cc: "Tobin C. Harding" <me@tobin.cc>,
	Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	kernel-hardening@lists.openwall.com,
	linux-kernel@vger.kernel.org,
	driverdev-devel@linuxdriverproject.org,
	Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH 4/4] video: Remove stack VLA usage
Date: Fri, 9 Mar 2018 00:16:21 -0600	[thread overview]
Message-ID: <d99bbd46-8fed-b86f-c043-272ebc96e023@embeddedor.com> (raw)
In-Reply-To: <20180309061152.r3yumh6agasyhtvo@cisco>


I sent a patch for this six hours ago:

https://patchwork.kernel.org/patch/10268591/

--
Gustavo

On 03/09/2018 12:11 AM, Tycho Andersen wrote:
> On Thu, Mar 08, 2018 at 10:01:07PM -0800, Joe Perches wrote:
>> On Fri, 2018-03-09 at 16:50 +1100, Tobin C. Harding wrote:
>>> The kernel would like to have all stack VLA usage removed[1].  The
>>> arrays are fixed here (declared with a const variable) but they appear
>>> like VLAs to the compiler.  We can use a pre-processor define to fix the
>>> warning.
>> []
>>> diff --git a/drivers/video/fbdev/via/via_aux_sii164.c b/drivers/video/fbdev/via/via_aux_sii164.c
>> []
>>> @@ -27,6 +27,9 @@
>>>   
>>>   static const char *name = "SiI 164 PanelLink Transmitter";
>>>   
>>> +/* check vendor id and device id */
>>> +const u8 id[] = {0x01, 0x00, 0x06, 0x00};
>>
>> It seems id is now global in multiple places.
>> Perhaps these should be static.
> 
> Does it even need to be global? Why not just get rid of the indirection and use
> ARRAY_SIZE where we mean it? This seems to work for me,
> 
> diff --git a/drivers/video/fbdev/via/via_aux_sii164.c b/drivers/video/fbdev/via/via_aux_sii164.c
> index ca1b35f033b1..87db6c98d680 100644
> --- a/drivers/video/fbdev/via/via_aux_sii164.c
> +++ b/drivers/video/fbdev/via/via_aux_sii164.c
> @@ -35,10 +35,10 @@ static void probe(struct via_aux_bus *bus, u8 addr)
>                  .addr   =       addr,
>                  .name   =       name};
>          /* check vendor id and device id */
> -       const u8 id[] = {0x01, 0x00, 0x06, 0x00}, len = ARRAY_SIZE(id);
> -       u8 tmp[len];
> +       const u8 id[] = {0x01, 0x00, 0x06, 0x00};
> +       u8 tmp[ARRAY_SIZE(id)];
>   
> -       if (!via_aux_read(&drv, 0x00, tmp, len) || memcmp(id, tmp, len))
> +       if (!via_aux_read(&drv, 0x00, tmp, sizeof(tmp)) || memcmp(id, tmp, sizeof(tmp)))
>                  return;
>   
>          printk(KERN_INFO "viafb: Found %s at address 0x%x\n", name, addr);
> 
> Cheers,
> 
> Tycho
> 

  reply	other threads:[~2018-03-09  6:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  5:50 Tobin C. Harding
2018-03-09  6:01 ` Joe Perches
2018-03-09  6:04   ` Tobin C. Harding
2018-03-09  6:11   ` Tycho Andersen
2018-03-09  6:16     ` Gustavo A. R. Silva [this message]
2018-03-09  6:28       ` Tobin C. Harding

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=d99bbd46-8fed-b86f-c043-272ebc96e023@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=FlorianSchandinat@gmx.de \
    --cc=b.zolnierkie@samsung.com \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@tobin.cc \
    --cc=tycho@tycho.ws \
    /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

Powered by JetHome