qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] eepro100: Don't allow guests to fail assertions
Date: Thu, 24 Sep 2009 09:25:53 +0200	[thread overview]
Message-ID: <4ABB1F01.3030507@redhat.com> (raw)
In-Reply-To: <4ABA62D3.6030900@mail.berlios.de>

Am 23.09.2009 20:02, schrieb Stefan Weil:
> Kevin Wolf schrieb:
>> The idea of using assert() for input validation is rather questionable.
>> Let's remove it from eepro100, so that guests need to find more
>> interesting
>> ways if they want to crash qemu.
>>
>> This patch replaces asserts that are directly dependent on
>> guest-accessible
>> data by other means of error handling.
>>
>> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
>> ---
>> hw/eepro100.c | 46 +++++++++++++++++++++++++++++++++++-----------
>> 1 files changed, 35 insertions(+), 11 deletions(-)
>>
> There are about 10 pending patches for eepro100.c, so the code at
> savannah is
> not a good base for new patches of eepro100.c. And there are even more
> patches
> in my queue to be sent as soon as the first 10 are integrated.
> 
> git://repo.or.cz/qemu/ar7.git has my latest version of eepro100.c.
> Could you please send a patch based on that version (or just wait
> until the savannah version is up-to-date)?

Seems this is just what must happen when patches accumulate on the list
without being committed. I'll try to rebase on top of your patches.
Thanks for the git URL, saves me some work of applying everything manually.

Apart from that, have you had a look at the actual changes? In some
places I'm not completely sure what's the right thing to do. I just know
that assert is the wrong one.

Kevin

  reply	other threads:[~2009-09-24  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 15:42 [Qemu-devel] [PATCH] eepro100: Don't allow guests to fail assertions Kevin Wolf
2009-09-23 18:02 ` Stefan Weil
2009-09-24  7:25   ` Kevin Wolf [this message]
2009-09-25 10:14   ` Kevin Wolf
2009-09-25 15:28     ` Stefan Weil

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=4ABB1F01.3030507@redhat.com \
    --to=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.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).