unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: PING^2: [PATCH 0/2] nptl: Update struct pthread_unwind_buf
Date: Fri, 23 Feb 2018 21:48:41 -0800	[thread overview]
Message-ID: <dca4154b-bc86-a914-8fee-b52f03c17bdf@redhat.com> (raw)
In-Reply-To: <CAMe9rOpoaaL=2B6cjLcGdPtwtWUFp5Sd+St4i1rA+eq5c30wnw@mail.gmail.com>

On 02/21/2018 07:33 AM, H.J. Lu wrote:
> On Thu, Feb 15, 2018 at 12:02 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>> On Fri, Feb 9, 2018 at 7:24 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>> On Fri, Feb 9, 2018 at 6:33 AM, Florian Weimer <fweimer@redhat.com> wrote:
>>>> On 02/09/2018 03:13 PM, H.J. Lu wrote:
>>>>>
>>>>> I built glibc master with gcc-8.0.1 -mcet -fcf-protection.  Some object
>>>>> files do get CET marker as expected.  But static executable isn't:
>>>>
>>>>
>>>> I said static libraries.  If I compile this code (based on the example from
>>>> the manual page) on Fedora rawhide:
>>>>
>>>
>>> Glibc never provides binary compatibility with static libraries.  My suggestions
>>> are
>>>
>>> 1. Recompile static libraries after CET is enabled in glibc.  Or
>>> 2. Don't compile static libraries with CET.
>>>
>>> BTW, we don't have space to save shadow stack register with existing
>>> cancel buf.
>>>
>>
>> PING:
>>
>> https://sourceware.org/ml/libc-alpha/2018-02/msg00290.html
>> https://sourceware.org/ml/libc-alpha/2018-02/msg00291.html
>>
> 
> PING.
 
These patches are pending the conclusion of the discussion that the
shadow stack pointer does not need to be restored in the unwinding
use case, and need only be placed in such a location that if it is
written it writes within the size of the existing truncated unwind
buffer.

Please see:
https://www.sourceware.org/ml/libc-alpha/2018-02/msg00679.html

-- 
Cheers,
Carlos.


  reply	other threads:[~2018-02-24  5:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 15:33 PING^2: [PATCH 0/2] nptl: Update struct pthread_unwind_buf H.J. Lu
2018-02-24  5:48 ` Carlos O'Donell [this message]
2018-02-24 15:20   ` H.J. Lu

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dca4154b-bc86-a914-8fee-b52f03c17bdf@redhat.com \
    --to=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.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 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).