From: "Caccavale, Samuel" <samcacc@amazon.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Sam Caccavale <samcacc@amazon.de>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Pohlack, Martin" <mpohlack@amazon.de>,
"Wieczorkiewicz, Pawel" <wipawel@amazon.de>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
Jan Beulich <jbeulich@suse.com>,
Martin Mazein <amazein@amazon.de>,
"Doebel, Bjoern" <doebel@amazon.de>,
"Manthey, Norbert" <nmanthey@amazon.de>
Subject: Re: [PATCH fuzzer v1] Added the --ignore-sigill option for AFL fuzzing
Date: Tue, 23 Apr 2019 10:12:31 +0000 [thread overview]
Message-ID: <1556014350963.34293@amazon.com> (raw)
In-Reply-To: <75edc89a-cda7-81ec-afca-1d31f08d6897@citrix.com>
Yes. Current staging resolves all of the SIG-ILL related crashes.
Tangentially I have ~1000 crashes which fail the `ctxt->regs->r(ip) == orig_ip'
assert at x86_emulate/x86_emulate.c:9862 when compiling afl-harness statically
with afl-clang-fast. They do not reproduce when compiled dynamically or
compiled in any way with afl-gcc.
I will look into these and open a new email chain if this is a problem with Xen,
though it looks like an afl or llvm issue. If you have any insight then please
let me know.
Best,
Sam Caccavale
________________________________________
From: Andrew Cooper <andrew.cooper3@citrix.com>
Sent: Tuesday, April 23, 2019 12:02 PM
To: Caccavale, Samuel; Sam Caccavale; xen-devel@lists.xenproject.org
Cc: Jan Beulich; Doebel, Bjoern; Woodhouse, David; Martin Mazein; Pohlack, Martin; Wieczorkiewicz, Pawel; Manthey, Norbert
Subject: Re: [PATCH fuzzer v1] Added the --ignore-sigill option for AFL fuzzing
On 23/04/2019 10:10, Caccavale, Samuel wrote:
> My mistake, I'm currently unable to reproduce the ~100 crashes
> AFL found while fuzzing the master branch, on the current staging
> branch. It seems some staged patch has since addressed this.
>
> If it is of any interest, most of the crashes came from AVX512
> instructions.
>
> Sorry and thanks,
Not a problem in the slightest.
Are you saying that current staging resolves all the crashed you'd
found? If not, please do report them.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Caccavale, Samuel" <samcacc@amazon.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Sam Caccavale <samcacc@amazon.de>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Pohlack, Martin" <mpohlack@amazon.de>,
"Wieczorkiewicz, Pawel" <wipawel@amazon.de>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
Jan Beulich <jbeulich@suse.com>,
Martin Mazein <amazein@amazon.de>,
"Doebel, Bjoern" <doebel@amazon.de>,
"Manthey, Norbert" <nmanthey@amazon.de>
Subject: Re: [Xen-devel] [PATCH fuzzer v1] Added the --ignore-sigill option for AFL fuzzing
Date: Tue, 23 Apr 2019 10:12:31 +0000 [thread overview]
Message-ID: <1556014350963.34293@amazon.com> (raw)
Message-ID: <20190423101231.wHgSWGUmUTWPoAeaghvo9d8y_oabIga4Jo2N4S0_GrY@z> (raw)
In-Reply-To: <75edc89a-cda7-81ec-afca-1d31f08d6897@citrix.com>
Yes. Current staging resolves all of the SIG-ILL related crashes.
Tangentially I have ~1000 crashes which fail the `ctxt->regs->r(ip) == orig_ip'
assert at x86_emulate/x86_emulate.c:9862 when compiling afl-harness statically
with afl-clang-fast. They do not reproduce when compiled dynamically or
compiled in any way with afl-gcc.
I will look into these and open a new email chain if this is a problem with Xen,
though it looks like an afl or llvm issue. If you have any insight then please
let me know.
Best,
Sam Caccavale
________________________________________
From: Andrew Cooper <andrew.cooper3@citrix.com>
Sent: Tuesday, April 23, 2019 12:02 PM
To: Caccavale, Samuel; Sam Caccavale; xen-devel@lists.xenproject.org
Cc: Jan Beulich; Doebel, Bjoern; Woodhouse, David; Martin Mazein; Pohlack, Martin; Wieczorkiewicz, Pawel; Manthey, Norbert
Subject: Re: [PATCH fuzzer v1] Added the --ignore-sigill option for AFL fuzzing
On 23/04/2019 10:10, Caccavale, Samuel wrote:
> My mistake, I'm currently unable to reproduce the ~100 crashes
> AFL found while fuzzing the master branch, on the current staging
> branch. It seems some staged patch has since addressed this.
>
> If it is of any interest, most of the crashes came from AVX512
> instructions.
>
> Sorry and thanks,
Not a problem in the slightest.
Are you saying that current staging resolves all the crashed you'd
found? If not, please do report them.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-04-23 10:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 15:02 [PATCH fuzzer v1] Added the --ignore-sigill option for AFL fuzzing Sam Caccavale
2019-04-18 15:02 ` [Xen-devel] " Sam Caccavale
2019-04-18 16:18 ` Andrew Cooper
2019-04-18 16:18 ` [Xen-devel] " Andrew Cooper
2019-04-23 9:10 ` Caccavale, Samuel
2019-04-23 9:10 ` [Xen-devel] " Caccavale, Samuel
2019-04-23 10:02 ` Andrew Cooper
2019-04-23 10:02 ` [Xen-devel] " Andrew Cooper
2019-04-23 10:12 ` Caccavale, Samuel [this message]
2019-04-23 10:12 ` Caccavale, Samuel
2019-04-23 10:25 ` Andrew Cooper
2019-04-23 10:25 ` [Xen-devel] " Andrew Cooper
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=1556014350963.34293@amazon.com \
--to=samcacc@amazon.com \
--cc=amazein@amazon.de \
--cc=andrew.cooper3@citrix.com \
--cc=doebel@amazon.de \
--cc=dwmw@amazon.co.uk \
--cc=jbeulich@suse.com \
--cc=mpohlack@amazon.de \
--cc=nmanthey@amazon.de \
--cc=samcacc@amazon.de \
--cc=wipawel@amazon.de \
--cc=xen-devel@lists.xenproject.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.