From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Sergey Dyasli <sergey.dyasli@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>, WeiLiu <wl@xen.org>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH 0/2] libx86: Fuzzing harness
Date: Wed, 5 Jun 2019 10:58:40 +0100 [thread overview]
Message-ID: <4830243a-87f7-4e78-6c27-d67fe561e617@citrix.com> (raw)
In-Reply-To: <5CF79151020000780023569C@prv1-mh.provo.novell.com>
On 05/06/2019 10:54, Jan Beulich wrote:
>>>> On 04.06.19 at 21:51, <andrew.cooper3@citrix.com> wrote:
>> These are the final pieces to getting the fuzzing harness working correctly.
> I'm mildly confused by this statement, as it seems to imply there was
> something not working correctly, when in fact there was nothing at
> all - patch 2 only adds a new harness.
If you recall, the fuzzing harness was posted previously (during the
lead-up to L1TF) in the same patch as the unit tests, with a note saying
"sometimes AFL finds assertion failures".
In the end I dropped the fuzzing harness until I'd got it into a state
where it functioned correctly, and this is the final piece which isn't
yet committed upstream.
As to your question in patch 1 - all of the new library functionality is
strictly relevant to making DOMCTL_set_cpu_policy function correctly.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-06-05 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 19:51 [Xen-devel] [PATCH 0/2] libx86: Fuzzing harness Andrew Cooper
2019-06-04 19:51 ` [Xen-devel] [PATCH 1/2] libx86: Helper for clearing out-of-range CPUID leaves Andrew Cooper
2019-06-05 9:45 ` Jan Beulich
2019-06-05 11:26 ` Andrew Cooper
2019-06-05 13:01 ` Jan Beulich
2019-06-04 19:51 ` [Xen-devel] [PATCH 2/2] tools/fuzz: Add a cpu-policy fuzzing harness Andrew Cooper
2019-06-05 9:51 ` Jan Beulich
2019-06-05 11:31 ` Andrew Cooper
2019-06-05 13:02 ` Jan Beulich
2019-06-05 9:54 ` [Xen-devel] [PATCH 0/2] libx86: Fuzzing harness Jan Beulich
2019-06-05 9:58 ` Andrew Cooper [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=4830243a-87f7-4e78-6c27-d67fe561e617@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=sergey.dyasli@citrix.com \
--cc=wl@xen.org \
--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.