From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Cc: Will Deacon <will@kernel.org>,
Tamas Zsoldos <tamas.zsoldos@arm.com>,
Mark Brown <broonie@kernel.org>,
kernel-team@android.com, Dave Martin <dave.martin@arm.com>,
Daniel Kiss <daniel.kiss@arm.com>
Subject: [PATCH 0/3] arm64 sigreturn unwinding fixes
Date: Tue, 19 May 2020 13:18:15 +0100 [thread overview]
Message-ID: <20200519121818.14511-1-will@kernel.org> (raw)
Hi folks,
Here are a handful of sigreturn unwinding fixes, based on top of for-next/bti.
Note that I haven't confirmed the GDB breakage, I only spotted it by reading
the code.
Daniel, Tamas: please can you confirm that these fix your unwinding issues with
LLVM?
Given that this has always been broken and there's a risk of introducing
a new regression, I plan to queue these for 5.8 so that we can revert
bits if necessary.
Thanks,
Will
Cc: Dave Martin <dave.martin@arm.com>
Cc: Tamas Zsoldos <tamas.zsoldos@arm.com>
Cc: Daniel Kiss <daniel.kiss@arm.com>
Cc: Mark Brown <broonie@kernel.org>
Cc: <kernel-team@android.com>
--->8
Will Deacon (3):
arm64: vdso: Don't prefix sigreturn trampoline with a BTI C
instruction
arm64: vdso: Add a comment to justify the mysterious NOP in sigreturn
arm64: vdso: Fix CFI directives in sigreturn trampoline
arch/arm64/kernel/vdso/sigreturn.S | 20 +++++++++++++++-----
1 file changed, 15 insertions(+), 5 deletions(-)
--
2.26.2.761.g0e0b3e54be-goog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-05-19 12:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 12:18 Will Deacon [this message]
2020-05-19 12:18 ` [PATCH 1/3] arm64: vdso: Don't prefix sigreturn trampoline with a BTI C instruction Will Deacon
2020-05-19 12:38 ` Mark Brown
2020-05-19 13:25 ` Dave Martin
2020-05-19 14:35 ` Mark Brown
2020-05-19 14:55 ` Dave Martin
2020-05-19 15:42 ` Mark Brown
2020-05-20 9:48 ` Dave Martin
2020-05-20 10:46 ` Mark Brown
2020-05-20 11:08 ` Dave Martin
2020-05-19 15:26 ` Will Deacon
2020-05-19 13:21 ` Dave Martin
2020-05-19 13:29 ` Will Deacon
2020-05-19 12:18 ` [PATCH 2/3] arm64: vdso: Add a comment to justify the mysterious NOP in sigreturn Will Deacon
2020-05-19 13:26 ` Dave Martin
2020-05-19 12:18 ` [PATCH 3/3] arm64: vdso: Fix CFI directives in sigreturn trampoline Will Deacon
2020-05-19 13:09 ` Dave P Martin
2020-05-19 13:39 ` Will Deacon
2020-05-19 13:55 ` Dave Martin
2020-05-19 15:24 ` Will Deacon
2020-05-19 15:30 ` Daniel Kiss
2020-05-19 15:55 ` Will Deacon
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=20200519121818.14511-1-will@kernel.org \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=daniel.kiss@arm.com \
--cc=dave.martin@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=tamas.zsoldos@arm.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 NNTP newsgroup(s).