mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Matt Fleming <matt.fleming@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
Subject: Re: [PATCH] firmware: dmi_scan: Prevent dmi_num integer overflow
Date: Fri, 27 Mar 2015 14:22:15 +0100	[thread overview]
Message-ID: <1427462535.26270.4.camel@chaos.site> (raw)
In-Reply-To: <20150327121243.GA5801@codeblueprint.co.uk>

Hi Matt,

Le Friday 27 March 2015 à 12:12 +0000, Matt Fleming a écrit :
> On Thu, 26 Mar, at 04:21:53PM, Jean Delvare wrote:
> > Le Thursday 26 March 2015 à 14:47 +0000, Matt Fleming a écrit :
> > > On Thu, 26 Mar, at 02:15:05PM, Jean Delvare wrote:
> > > > 
> > > > I don't actually have a tree, so feel free to pick it.
> > > 
> > > OK will do, but this is a regression fix for a potential bug introduced
> > > in commit 6d9ff4733172 ("firmware: dmi_scan: Fix dmi_len type"), right?
> > 
> > Not really. I'd rather say it complements commit 6d9ff4733172. The
> > actual bugs were introduced in commit fc43026278b2. But you can't really
> > call it a regression as SMBIOS 3.0 entry points were not supported at
> > all before that commit.
>  
> OK, thanks for clarifying.
> 
> > Still a reference to commit fc43026278b2 would certainly be appropriate,
> > as anyone backporting that commit will also want to pick the two
> > aforementioned fix-ups (plus ce204e9a4bd8 for that matter.)
> 
> commit ce204e9a4bd8 and 6d9ff4733172 are already tagged for stable, so
> we should be good there.
> 
> This is what I've got queued up to send to tip today. Feel free to send
> me another version today if you want to word things differently.

Looks good, thanks for taking care of it.

-- 
Jean Delvare
SUSE L3 Support


      reply	other threads:[~2015-03-27 13:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20  8:59 Jean Delvare
2015-03-20  9:21 ` Ard Biesheuvel
2015-03-26 13:06 ` Matt Fleming
2015-03-26 13:15   ` Jean Delvare
2015-03-26 14:47     ` Matt Fleming
2015-03-26 15:21       ` Jean Delvare
2015-03-27 12:12         ` Matt Fleming
2015-03-27 13:22           ` Jean Delvare [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=1427462535.26270.4.camel@chaos.site \
    --to=jdelvare@suse.de \
    --cc=ard.biesheuvel@linaro.org \
    --cc=ivan.khoronzhuk@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=matt@codeblueprint.co.uk \
    /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®