From: Jes.Sorensen@redhat.com
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org, dledford@redhat.com
Subject: [PATCH 0/2] Misc fixes
Date: Fri, 28 Oct 2011 21:50:49 +0200 [thread overview]
Message-ID: <1319831451-26704-1-git-send-email-Jes.Sorensen@redhat.com> (raw)
From: Jes Sorensen <Jes.Sorensen@redhat.com>
Hi,
Two fixes:
The first is to avoid a use-after-free case. I looked at this one for
a while, and I believe this is the intention of the code. Ie. once we
find the first entry, bail out to the end rather than going back
re-iterating over the list that we just freed.
The second to avoid the case where a GPT partition table entry is
larger than 128 bytes, in which case we would read it and corrupt the
stack.
Jes Sorensen (2):
Avoid use after free
Avoid stack overflow if GPT partition entries on disk are > 128 bytes
util.c | 15 ++++++++++-----
1 files changed, 10 insertions(+), 5 deletions(-)
--
1.7.6.4
next reply other threads:[~2011-10-28 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 19:50 Jes.Sorensen [this message]
2011-10-28 19:50 ` [PATCH 1/2] Avoid use after free Jes.Sorensen
2011-10-30 23:43 ` NeilBrown
2011-10-31 7:41 ` Jes Sorensen
2011-10-28 19:50 ` [PATCH 2/2] Avoid stack overflow if GPT partition entries on disk are > 128 bytes Jes.Sorensen
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=1319831451-26704-1-git-send-email-Jes.Sorensen@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).