From: Laura Abbott <labbott@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Alex Dubov <oakad@yahoo.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Hardening <kernel-hardening@lists.openwall.com>
Subject: Re: [PATCH] misc: tifm: Remove VLA
Date: Tue, 10 Apr 2018 11:49:02 -0700 [thread overview]
Message-ID: <799e8f9a-0aa1-6f5d-8421-7c768d70f562@redhat.com> (raw)
In-Reply-To: <CAK8P3a3Yo0riMroM3x4EVz8FkMakdPkkJ-mCTYW0qOji+MCCiQ@mail.gmail.com>
On 04/10/2018 12:57 AM, Arnd Bergmann wrote:
> On Mon, Apr 9, 2018 at 11:07 PM, Laura Abbott <labbott@redhat.com> wrote:
>> There's an ongoing effort to remove VLAs[1] from the kernel to eventually
>> turn on -Wvla. The single VLA can either take a value of 2 or 4 so switch
>> to the upper bound.
>>
>> [1] https://lkml.org/lkml/2018/3/7/621
>>
>> Signed-off-by: Laura Abbott <labbott@redhat.com>
>> ---
>> drivers/misc/tifm_7xx1.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/misc/tifm_7xx1.c b/drivers/misc/tifm_7xx1.c
>> index e5f108713dd8..690eaaea5ce4 100644
>> --- a/drivers/misc/tifm_7xx1.c
>> +++ b/drivers/misc/tifm_7xx1.c
>> @@ -239,7 +239,8 @@ static int tifm_7xx1_resume(struct pci_dev *dev)
>> unsigned long timeout;
>> unsigned int good_sockets = 0, bad_sockets = 0;
>> unsigned long flags;
>> - unsigned char new_ids[fm->num_sockets];
>> + /* Maximum number of entries is 4 */
>> + unsigned char new_ids[4];
>> DECLARE_COMPLETION_ONSTACK(finish_resume);
>>
>
> I like the idea of removing all the VLAs, but this one appears to make
> the code less robust rather than more: In case of an unexpected
> fm->num_sockets value, we now not only overflow the kernel stack
> area but also the local variable into the neighboring stack slots.
>
> Maybe add an extra overflow check?
>
Sure.
> Arnd
>
> diff --git a/drivers/misc/tifm_7xx1.c b/drivers/misc/tifm_7xx1.c
> index e5f108713dd8..c702cd92d396 100644
> --- a/drivers/misc/tifm_7xx1.c
> +++ b/drivers/misc/tifm_7xx1.c
> @@ -239,9 +239,12 @@ static int tifm_7xx1_resume(struct pci_dev *dev)
> unsigned long timeout;
> unsigned int good_sockets = 0, bad_sockets = 0;
> unsigned long flags;
> - unsigned char new_ids[fm->num_sockets];
> + /* Maximum number of entries is 4 */
> + unsigned char new_ids[4];
> DECLARE_COMPLETION_ONSTACK(finish_resume);
>
> + if (WARN_ON(fm->num_sockets > ARRAY_SIZE(new_ids)))
> + return -ENXIO;
> +
> pci_set_power_state(dev, PCI_D0);
> pci_restore_state(dev);
> rc = pci_enable_device(dev);
>
prev parent reply other threads:[~2018-04-10 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 21:07 Laura Abbott
2018-04-10 7:57 ` Arnd Bergmann
2018-04-10 18:49 ` Laura Abbott [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=799e8f9a-0aa1-6f5d-8421-7c768d70f562@redhat.com \
--to=labbott@redhat.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.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®