From: Thomas Huth <thuth@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Bandan Das <bsd@redhat.com>,
f4bug@amsat.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] fuzz: do not use POSIX shm for coverage bitmap
Date: Wed, 24 Jun 2020 09:51:41 +0200 [thread overview]
Message-ID: <192d94b9-b1f6-e744-8135-26aa26b88015@redhat.com> (raw)
In-Reply-To: <20200622165040.15121-1-alxndr@bu.edu>
On 22/06/2020 18.50, Alexander Bulekov wrote:
> We used shm_open with mmap to share libfuzzer's coverage bitmap with
> child (runner) processes. The same functionality can be achieved with
> MAP_SHARED | MAP_ANONYMOUS, since we do not care about naming or
> permissioning the shared memory object.
>
> Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
Thanks, queued to qtest-next now:
https://gitlab.com/huth/qemu/-/commits/qtest-next/
Thomas
prev parent reply other threads:[~2020-06-24 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 16:50 [PATCH] fuzz: do not use POSIX shm for coverage bitmap Alexander Bulekov
2020-06-23 8:03 ` Darren Kenny
2020-06-23 8:44 ` Stefan Hajnoczi
2020-06-24 7:51 ` Thomas Huth [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=192d94b9-b1f6-e744-8135-26aa26b88015@redhat.com \
--to=thuth@redhat.com \
--cc=alxndr@bu.edu \
--cc=bsd@redhat.com \
--cc=f4bug@amsat.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).