public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Zack Weinberg <zackw@panix.com>
Cc: Jeff Law <law@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>,
	Joseph Myers <joseph@codesourcery.com>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Subject: Re: [PATCH] explicit_bzero final
Date: Wed, 14 Dec 2016 13:15:00 -0000	[thread overview]
Message-ID: <3ea46d8d-4ace-719d-a47e-917c000a0d26@redhat.com> (raw)
In-Reply-To: <CAKCAbMgxfviybrcRtSO-=eEc0YQc-TfwP+fvtKqQsodBTr_isg@mail.gmail.com>

On 12/14/2016 02:04 AM, Zack Weinberg wrote:
> We also have a nasty interaction between internal PLT bypass and
> ifuncs which means that a hypothetical __explicit_bzero_chk is
> ridiculously difficult to implement.  I tried that once already and it
> did not go well.

I'm looking into this aspect right now.

Florian

  parent reply	other threads:[~2016-12-14 13:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 23:06 Zack Weinberg
2016-12-13  1:58 ` Paul Eggert
2016-12-13  7:02 ` Florian Weimer
2016-12-13 15:53   ` Zack Weinberg
2016-12-13 22:47     ` Jeff Law
2016-12-14  1:04       ` Zack Weinberg
2016-12-14  1:05         ` Zack Weinberg
2016-12-14 13:15         ` Florian Weimer [this message]
2016-12-14 17:06           ` Florian Weimer
2016-12-14 22:28             ` Zack Weinberg
2016-12-14 22:37               ` Joseph Myers
2016-12-15  9:08               ` Florian Weimer
2016-12-15 10:20                 ` Florian Weimer
2016-12-15 23:31                 ` Zack Weinberg
2016-12-16  7:50                   ` Florian Weimer
2016-12-14 16:58         ` Jeff Law
2016-12-14 23:11           ` Zack Weinberg
2016-12-15  5:25             ` Jeff Law
2016-12-15 23:21               ` Zack Weinberg
2016-12-16 18:26                 ` Jeff Law
2016-12-16 21:35                   ` Zack Weinberg

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=3ea46d8d-4ace-719d-a47e-917c000a0d26@redhat.com \
    --to=fweimer@redhat.com \
    --cc=Wilco.Dijkstra@arm.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=joseph@codesourcery.com \
    --cc=law@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=zackw@panix.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 read-only IMAP folder(s) and NNTP newsgroup(s).