From: Gleb Natapov <gleb@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org
Subject: Re: [PATCHv2] Fix EDD3.0 data verification.
Date: Wed, 16 Feb 2011 17:09:33 +0200 [thread overview]
Message-ID: <20110216150933.GE14984@redhat.com> (raw)
In-Reply-To: <20110208145301.GO14984@redhat.com>
On Tue, Feb 08, 2011 at 04:53:01PM +0200, Gleb Natapov wrote:
> Peter, ping.
>
> Is this version acceptable?
>
Ping?
> On Thu, Feb 03, 2011 at 02:29:48PM +0200, Gleb Natapov wrote:
> > Check for nonzero path in edd_has_edd30() has no sense. First, it looks
> > at the wrong memory. Device path starts at offset 30 of the info->params
> > structure which is at offset 8 from the beginning of info structure, but
> > code looks at info + 4 instead. This was correct when code was introduced,
> > but around v2.6.4 three more fields were added to edd_info structure
> > (commit 66b61a5c in history.git). Second, even if it will check correct
> > memory it will always succeed since at offset 30 (params->key) there will
> > be non-zero values otherwise previous check would fail.
> >
> > The patch replaces this bogus check with one that verifies checksum.
> >
> > Signed-off-by: Gleb Natapov <gleb@redhat.com>
> > ---
> > v1->v2
> > use device path info length to calculate csum.
> >
> > diff --git a/drivers/firmware/edd.c b/drivers/firmware/edd.c
> > index 96c25d9..f1b7f65 100644
> > --- a/drivers/firmware/edd.c
> > +++ b/drivers/firmware/edd.c
> > @@ -531,8 +531,8 @@ static int
> > edd_has_edd30(struct edd_device *edev)
> > {
> > struct edd_info *info;
> > - int i, nonzero_path = 0;
> > - char c;
> > + int i;
> > + u8 csum = 0;
> >
> > if (!edev)
> > return 0;
> > @@ -544,16 +544,16 @@ edd_has_edd30(struct edd_device *edev)
> > return 0;
> > }
> >
> > - for (i = 30; i <= 73; i++) {
> > - c = *(((uint8_t *) info) + i + 4);
> > - if (c) {
> > - nonzero_path++;
> > - break;
> > - }
> > - }
> > - if (!nonzero_path) {
> > +
> > + /* We support only T13 spec */
> > + if (info->params.device_path_info_length != 44)
> > + return 0;
> > +
> > + for (i = 30; i < info->params.device_path_info_length + 30; i++)
> > + csum += *(((u8 *)&info->params) + i);
> > +
> > + if (csum)
> > return 0;
> > - }
> >
> > return 1;
> > }
> > --
> > Gleb.
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> Gleb.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Gleb.
next prev parent reply other threads:[~2011-02-16 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 12:29 [PATCHv2] Fix EDD3.0 data verification Gleb Natapov
2011-02-08 14:53 ` Gleb Natapov
2011-02-16 15:09 ` Gleb Natapov [this message]
2011-02-16 18:57 ` H. Peter Anvin
2011-03-16 8:57 ` Gleb Natapov
2011-04-05 15:41 ` Gleb Natapov
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=20110216150933.GE14984@redhat.com \
--to=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).