From: Auger Eric <eric.auger@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, Peter Xu <peterx@redhat.com>
Cc: "Jason Wang" <jasowang@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 2/2] intel-iommu: start to use error_report_once
Date: Wed, 13 Jun 2018 11:36:05 +0200 [thread overview]
Message-ID: <dfb61dcd-c180-1307-bf9d-086aa15478ec@redhat.com> (raw)
In-Reply-To: <87r2lbkt5u.fsf@dusky.pond.sub.org>
Hi,
On 06/13/2018 10:05 AM, Markus Armbruster wrote:
> Peter Xu <peterx@redhat.com> writes:
>
>> Replace existing trace_vtd_err() with error_report_once() then stderr
>> will capture something if any of the error happens, meanwhile we don't
>> suffer from any DDOS. Then remove the trace point. Since at it,
>> provide more information where proper (now we can pass parameters into
>> the report function).
>>
>> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> Signed-off-by: Peter Xu <peterx@redhat.com>
>> ---
>> hw/i386/intel_iommu.c | 59 ++++++++++++++++++++++++-------------------
>> hw/i386/trace-events | 1 -
>> 2 files changed, 33 insertions(+), 27 deletions(-)
>
> Michael, would you give your Reviewed-by or Acked-by? I'd take the
> series through my tree then.
>
> [...]
>
Sorry to enter this thread at this late stage. Just one question: on the
smmuv3 emulation code, Peter (Maydell) urged me to use
qemu_log_mask(LOG_GUEST_ERROR, ...) whenever the error was triggered by
a guest bad behavior. So what is the final guidance to avoid the DOS you
mention?
Thanks
Eric
next prev parent reply other threads:[~2018-06-13 9:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 4:44 [Qemu-devel] [PATCH v4 0/2] error-report: introduce {error|warn}_report_once Peter Xu
2018-05-24 4:44 ` [Qemu-devel] [PATCH v4 1/2] qemu-error: " Peter Xu
2018-05-29 9:30 ` Cornelia Huck
2018-05-30 3:30 ` Peter Xu
2018-05-30 13:36 ` Cornelia Huck
2018-06-13 7:56 ` Markus Armbruster
2018-05-30 4:47 ` Michael S. Tsirkin
2018-05-30 6:39 ` Peter Xu
2018-05-30 13:53 ` Cornelia Huck
2018-06-13 7:59 ` Markus Armbruster
2018-05-30 15:15 ` Halil Pasic
2018-05-30 15:19 ` Michael S. Tsirkin
2018-05-30 15:30 ` Halil Pasic
2018-06-13 8:01 ` Markus Armbruster
2018-06-13 9:08 ` Peter Xu
2018-05-24 4:44 ` [Qemu-devel] [PATCH v4 2/2] intel-iommu: start to use error_report_once Peter Xu
2018-06-13 8:05 ` Markus Armbruster
2018-06-13 9:36 ` Auger Eric [this message]
2018-06-14 12:51 ` Markus Armbruster
2018-06-14 12:56 ` Peter Maydell
2018-08-15 5:58 ` [Qemu-devel] [PATCH v4 0/2] error-report: introduce {error|warn}_report_once Markus Armbruster
2018-08-15 6:10 ` Peter Xu
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=dfb61dcd-c180-1307-bf9d-086aa15478ec@redhat.com \
--to=eric.auger@redhat.com \
--cc=armbru@redhat.com \
--cc=f4bug@amsat.org \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@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 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).