From: "Loïc Minier" <lool@dooz.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fat_chksum(): fix access above array bounds
Date: Mon, 23 Aug 2010 16:56:13 +0200 [thread overview]
Message-ID: <20100823145613.GD15935@bee.dooz.org> (raw)
In-Reply-To: <4C7288BC.9000804@redhat.com>
On Mon, Aug 23, 2010, Kevin Wolf wrote:
> How did you find this one? From a quick look it seems that the pattern
> that name is intentionally overflowed to access extension is still there
> in some places. So if this caused some real bug, I think we'll have to
> fix the other ones, too.
Compiler found that one
http://launchpadlibrarian.net/54142111/buildlog_ubuntu-maverick-armel.qemu-maemo_0.0~20100806%2Bd7a5eb1-0ubuntu1~linaro2_FAILEDTOBUILD.txt.gz
but I didn't quote it because I'm at a loss as to why it detected it
now and on armel only. I think I just got one accidental build on a
modern gcc-4.4 tree because of the timing of my copy of the packages.
I guess I should build them more regularly under a recent gcc.
--
Loïc Minier
prev parent reply other threads:[~2010-08-23 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 22:47 [Qemu-devel] [PATCH] fat_chksum(): fix access above array bounds Loïc Minier
2010-08-23 14:42 ` Kevin Wolf
2010-08-23 14:56 ` Loïc Minier [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=20100823145613.GD15935@bee.dooz.org \
--to=lool@dooz.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.