From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/2] Linux/x86: Update cancel_jmp_buf to match __jmp_buf_tag [BZ #22563]
Date: Mon, 18 Dec 2017 11:49:00 -0000 [thread overview]
Message-ID: <4e80a87a-c90a-85a6-daf1-cbbf71d0bf58@redhat.com> (raw)
In-Reply-To: <CAMe9rOqiSm6GfuXCAwL3zuuRO5mzdMtx3MkrxBpdgSC0nNCghw@mail.gmail.com>
On 12/18/2017 12:42 PM, H.J. Lu wrote:
> We need to restore shadow stack pointer here so that we can jump back
> to the function where __sigsetjmp is called.
But neither __sigsetjmp (when called the second time) nor the function
that calls it return normally during cancellation, so it is still
completely unclear to me what issue you are observing.
Could you post a backtrace from the CET verification failure, please?
Thanks,
Florian
next prev parent reply other threads:[~2017-12-18 11:49 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 17:41 H.J. Lu
2017-12-07 17:58 ` Joseph Myers
2017-12-07 18:37 ` Florian Weimer
2017-12-07 18:59 ` H.J. Lu
2017-12-07 19:09 ` Florian Weimer
2017-12-07 19:12 ` H.J. Lu
2017-12-07 19:14 ` Florian Weimer
2017-12-07 19:19 ` H.J. Lu
2017-12-07 19:25 ` Florian Weimer
2017-12-07 19:35 ` H.J. Lu
2017-12-08 2:25 ` H.J. Lu
2017-12-14 13:06 ` H.J. Lu
2017-12-15 17:43 ` H.J. Lu
2017-12-18 10:25 ` Florian Weimer
2017-12-18 11:42 ` H.J. Lu
2017-12-18 11:49 ` Florian Weimer [this message]
2017-12-18 12:25 ` H.J. Lu
2017-12-18 12:52 ` Florian Weimer
2017-12-18 13:19 ` H.J. Lu
2017-12-18 14:13 ` H.J. Lu
2017-12-18 14:45 ` Andreas Schwab
2017-12-18 14:48 ` H.J. Lu
2017-12-18 16:29 ` H.J. Lu
2018-01-09 10:47 ` Florian Weimer
2018-01-09 12:17 ` H.J. Lu
2018-01-09 16:20 ` Senkevich, Andrew
2018-01-21 16:16 ` Aurelien Jarno
2018-01-21 16:27 ` H.J. Lu
2018-01-21 16:50 ` Carlos O'Donell
2018-01-22 14:44 ` Senkevich, Andrew
2018-01-23 19:35 ` Carlos O'Donell
2018-01-23 21:13 ` Senkevich, Andrew
2018-01-24 18:08 ` H.J. Lu
2018-01-24 18:23 ` Florian Weimer
2018-01-25 0:32 ` Carlos O'Donell
2018-01-25 0:56 ` Joseph Myers
2018-01-25 1:09 ` H.J. Lu
2018-01-25 1:44 ` Carlos O'Donell
2018-01-25 1:48 ` Dmitry V. Levin
2018-01-25 4:53 ` [PATCH] Revert Intel CET changes to __jmp_buf_tag (Bug 22743) Carlos O'Donell
2018-01-25 5:33 ` H.J. Lu
2018-01-25 9:47 ` Florian Weimer
2018-01-25 12:38 ` H.J. Lu
2018-01-25 12:50 ` Florian Weimer
2018-01-25 13:00 ` H.J. Lu
2018-01-25 14:56 ` Zack Weinberg
2018-01-25 15:33 ` H.J. Lu
2018-01-25 16:22 ` Zack Weinberg
2018-01-25 16:28 ` H.J. Lu
2018-01-25 16:36 ` Carlos O'Donell
2018-01-25 16:40 ` H.J. Lu
2018-01-25 16:46 ` Carlos O'Donell
2018-01-25 17:01 ` H.J. Lu
2018-01-26 7:46 ` Carlos O'Donell
2018-01-28 18:40 ` H.J. Lu
2018-01-25 16:47 ` Florian Weimer
2018-01-25 16:55 ` H.J. Lu
2018-01-25 18:26 ` Joseph Myers
2018-01-25 19:21 ` H.J. Lu
2018-01-25 16:37 ` Carlos O'Donell
2018-01-25 16:38 ` Florian Weimer
2017-12-18 17:37 ` [PATCH 1/2] Linux/x86: Update cancel_jmp_buf to match __jmp_buf_tag [BZ #22563] Joseph Myers
2017-12-18 21:19 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e80a87a-c90a-85a6-daf1-cbbf71d0bf58@redhat.com \
--to=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).