From: Daniele Buono <dbuono@linux.vnet.ibm.com>
To: Alexander Bulekov <alxndr@bu.edu>, Paolo Bonzini <pbonzini@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] configure: add support for Control-Flow Integrity
Date: Thu, 13 Aug 2020 10:00:36 -0400 [thread overview]
Message-ID: <8da7805e-7728-5109-564d-d26389efee68@linux.vnet.ibm.com> (raw)
In-Reply-To: <20200810211958.vyhkl3d4cxpu75ni@mozz.bu.edu>
Yes, Something like that, probably with a small python script.
On 8/10/2020 5:33 PM, Alexander Bulekov wrote:
> On 200810 2139, Paolo Bonzini wrote:
>> On 10/08/20 21:01, Daniele Buono wrote:
>>> So I'm thinking of adding a check in configure. If gold is the linker,
>>> automatically create (somehow, still working on it) the full link script
>>> by obtaining the default bfd script and add the required parts. Would
>>> that work for you?
>>
>> Maybe even do it unconditionally?
>
> I agree.
>
> I can try a respin of my compiler-rt/libFuzzer patches to add a built-in
> fork-server to libFuzzer, so we can avoid the linker-script madness
> altogether. Don't know how soon I can get to this, but I do think it is
> worth another try.
>
> TIL about these differences between ld.bfd and ld.gold.
> So the idea is to use something like:
> "ld --verbose | grep -n ".*:" | grep -A1 "\s.data\s" | tail -n1"
> and insert the existing linker-script before that line?
> Thanks
> -Alex
>
>> Paolo
>>
>
next prev parent reply other threads:[~2020-08-13 14:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 5:49 [PATCH 0/2] Add support for Control-Flow Integrity Daniele Buono
2020-07-02 5:49 ` [PATCH 1/2] check-block: enable iotests with cfi-icall Daniele Buono
2020-07-02 5:49 ` [PATCH 2/2] configure: add support for Control-Flow Integrity Daniele Buono
2020-07-02 9:45 ` Paolo Bonzini
2020-07-02 12:19 ` Daniele Buono
2020-07-02 9:52 ` Daniel P. Berrangé
2020-07-02 12:50 ` Daniele Buono
2020-07-02 12:59 ` Paolo Bonzini
2020-07-02 13:38 ` Alexander Bulekov
2020-07-02 15:43 ` Daniele Buono
2020-08-10 19:01 ` Daniele Buono
2020-08-10 19:39 ` Paolo Bonzini
2020-08-10 21:33 ` Alexander Bulekov
2020-08-13 14:00 ` Daniele Buono [this message]
2020-07-02 13:12 ` Daniel P. Berrangé
2020-07-02 15:02 ` Daniele Buono
2020-07-16 21:57 ` Daniele Buono
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=8da7805e-7728-5109-564d-d26389efee68@linux.vnet.ibm.com \
--to=dbuono@linux.vnet.ibm.com \
--cc=alxndr@bu.edu \
--cc=berrange@redhat.com \
--cc=pbonzini@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 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.