qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jack Schwartz <jack.schwartz@oracle.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, anatol.pomozov@gmail.com, ppandit@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/5] multiboot: Fix buffer overflow on invalid kernels
Date: Wed, 14 Mar 2018 22:19:25 -0700	[thread overview]
Message-ID: <75f404ed-70f5-dba5-17bb-e7302caa05af@oracle.com> (raw)
In-Reply-To: <20180314173213.18563-1-kwolf@redhat.com>

Hi Kevin.

I see an issue with the commit message of patch 1; please see my reply 
to that patch for details.  I fully understand patches 1,2,3, patch 4 
except for some of the Makefile black magic, and patch 5 looks 
reasonable to me.

So, for patches 2,3,4,5:
     Reviewed-by: Jack Schwartz <jack.schwartz@oracle.com>

     Thanks,
     Jack

On 2018-03-14 10:32, Kevin Wolf wrote:
> Patch 1 fixes another Multiboot kernel validation bug that could cause
> QEMU to load the kernel image file into a too small buffer. Patch 2 adds
> another check to harden the code. The rest of the series adds Multiboot
> test cases for kernels using the a.out kludge, which is where the recent
> bugs were found.
>
> Kevin Wolf (5):
>    multiboot: Reject kernels exceeding the address space
>    multiboot: Check validity of mh_header_addr
>    tests/multiboot: Test exit code for every qemu run
>    tests/multiboot: Add tests for the a.out kludge
>    tests/multiboot: Add .gitignore
>
>   hw/i386/multiboot.c             |   8 +++
>   tests/multiboot/.gitignore      |   3 +
>   tests/multiboot/Makefile        |  22 +++++--
>   tests/multiboot/aout_kludge.S   | 138 ++++++++++++++++++++++++++++++++++++++++
>   tests/multiboot/aout_kludge.out |  42 ++++++++++++
>   tests/multiboot/run_test.sh     |  34 ++++++----
>   6 files changed, 227 insertions(+), 20 deletions(-)
>   create mode 100644 tests/multiboot/.gitignore
>   create mode 100644 tests/multiboot/aout_kludge.S
>   create mode 100644 tests/multiboot/aout_kludge.out
>

      parent reply	other threads:[~2018-03-15  5:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 17:32 [Qemu-devel] [PATCH 0/5] multiboot: Fix buffer overflow on invalid kernels Kevin Wolf
2018-03-14 17:32 ` [Qemu-devel] [PATCH 1/5] multiboot: Reject kernels exceeding the address space Kevin Wolf
2018-03-15  5:19   ` Jack Schwartz
2018-03-15 15:54     ` Kevin Wolf
2018-03-15 16:55       ` Jack Schwartz
2018-03-15 17:18         ` Kevin Wolf
2018-03-15 19:50           ` Jack Schwartz
2018-03-14 17:32 ` [Qemu-devel] [PATCH 2/5] multiboot: Check validity of mh_header_addr Kevin Wolf
2018-03-14 17:32 ` [Qemu-devel] [PATCH 3/5] tests/multiboot: Test exit code for every qemu run Kevin Wolf
2018-03-14 17:32 ` [Qemu-devel] [PATCH 4/5] tests/multiboot: Add tests for the a.out kludge Kevin Wolf
2018-03-14 17:32 ` [Qemu-devel] [PATCH 5/5] tests/multiboot: Add .gitignore Kevin Wolf
2018-03-14 17:43   ` Eric Blake
2018-03-14 17:50     ` Eric Blake
2018-03-15  5:19 ` Jack Schwartz [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=75f404ed-70f5-dba5-17bb-e7302caa05af@oracle.com \
    --to=jack.schwartz@oracle.com \
    --cc=anatol.pomozov@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=ppandit@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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 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).