From: Florian Weimer <fw@deneb.enyo.de>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 0/2] nptl: Update struct pthread_unwind_buf
Date: Sun, 25 Feb 2018 12:55:00 -0000 [thread overview]
Message-ID: <87fu5pb7ql.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CAMe9rOqCPk55Ke9T+0194myAiQHwKZVv=gzm3pHDtULTaT0S3A@mail.gmail.com> (H. J. Lu's message of "Sun, 25 Feb 2018 03:37:44 -0800")
* H. J. Lu:
> On Sun, Feb 25, 2018 at 1:26 AM, Florian Weimer <fw@deneb.enyo.de> wrote:
>> * H. J. Lu:
>>
>>> What have I done wrong?
>>
>> My understanding (shared by Carlos as far as I know) is that you do
>> not need to restore the shadow stack pointer when unwinding for
>> cancellation or thread exit.
>
> It may be true for thread exit. Are you saying that a function will never
> return after cancellation point?
That's certainly the intent. Cancellation is supposed to be
unstoppable.
next prev parent reply other threads:[~2018-02-25 12:21 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 20:58 H.J. Lu
2018-02-01 20:58 ` [PATCH 1/2] Revert "Revert Intel CET changes to __jmp_buf_tag (Bug 22743)" H.J. Lu
2018-02-01 20:58 ` [PATCH 2/2] nptl: Update struct pthread_unwind_buf [BZ #22743] H.J. Lu
2018-02-08 11:40 ` [PATCH 0/2] nptl: Update struct pthread_unwind_buf Carlos O'Donell
2018-02-08 13:27 ` Florian Weimer
2018-02-09 10:08 ` Carlos O'Donell
2018-02-09 11:13 ` Florian Weimer
2018-02-09 12:34 ` H.J. Lu
2018-02-09 12:42 ` Florian Weimer
2018-02-09 13:07 ` H.J. Lu
2018-02-09 14:33 ` H.J. Lu
2018-02-09 14:56 ` Florian Weimer
2018-02-09 16:39 ` H.J. Lu
2018-02-24 5:54 ` Carlos O'Donell
2018-02-24 15:46 ` H.J. Lu
2018-02-25 9:26 ` Florian Weimer
2018-02-25 11:37 ` H.J. Lu
2018-02-25 12:21 ` Florian Weimer
2018-02-25 12:53 ` H.J. Lu
2018-02-25 12:55 ` Florian Weimer [this message]
2018-02-25 12:58 ` H.J. Lu
2018-02-25 13:23 ` H.J. Lu
2018-02-25 13:31 ` Florian Weimer
2018-02-25 13:36 ` H.J. Lu
2018-02-25 13:49 ` Florian Weimer
2018-02-25 13:49 ` H.J. Lu
2018-02-25 14:00 ` H.J. Lu
2018-02-25 14:13 ` Florian Weimer
2018-02-25 15:15 ` H.J. Lu
2018-02-26 1:06 ` Florian Weimer
2018-02-26 12:28 ` H.J. Lu
[not found] ` <3764b0a1-9f26-6f5f-1bc5-d374f2672f3a@redhat.com>
2018-03-07 11:56 ` H.J. Lu
2018-03-07 17:34 ` Carlos O'Donell
2018-03-07 19:47 ` H.J. Lu
2018-03-07 20:14 ` H.J. Lu
2018-03-07 22:07 ` H.J. Lu
2018-03-08 12:24 ` Tsimbalist, Igor V
2018-03-08 12:48 ` H.J. Lu
2018-03-09 0:47 ` Carlos O'Donell
2018-03-09 5:24 ` H.J. Lu
2018-03-15 4:21 ` Carlos O'Donell
2018-02-24 15:20 ` Carlos O'Donell
2018-02-08 17:47 ` H.J. Lu
2018-02-09 10:49 ` Carlos O'Donell
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=87fu5pb7ql.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=carlos@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).