[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vf7R_GeFhA5c2PR42K=cp-UbK4u2o7B5N9Ceu_NdFXmzg@mail.gmail.com>
Date: Thu, 1 Jun 2017 16:16:05 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Jean Delvare <jdelvare@...e.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH] firmware: dmi: Check DMI structure length
On Thu, Jun 1, 2017 at 4:08 PM, Jean Delvare <jdelvare@...e.de> wrote:
> Before accessing DMI data to record it for later, we should ensure
> that the DMI structures are large enough to contain the data in
> question.
> - const u8 *d = (u8 *) dm + index;
> + const u8 *d;
> + d = (u8 *) dm + index;
I think you may leave this as is and make it compiler's burden to optimize.
> - const u8 *d = (u8 *) dm + index;
> + const u8 *d;
> + d = (u8 *) dm + index;
Ditto.
> - int i, count = *(u8 *)(dm + 1);
> + int i, count;
> + count = *(u8 *)(dm + 1);
Ditto.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists