From: Yao Qi <yao.qi@arm.com>
To: Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: arnd@arndb.de, catalin.marinas@arm.com,
christoffer.dall@linaro.org, Dave.Martin@arm.com,
jiong.wang@arm.com, kvmarm@lists.cs.columbia.edu,
linux-arch@vger.kernel.org, marc.zyngier@arm.com,
suzuki.poulose@arm.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH 00/11] ARMv8.3 pointer authentication userspace support
Date: Tue, 25 Jul 2017 12:32:10 +0100 [thread overview]
Message-ID: <bb507ee1-c7ba-4c73-0d0f-058c4821793c@arm.com> (raw)
In-Reply-To: <1500480092-28480-1-git-send-email-mark.rutland@arm.com>
On 19/07/17 17:01, Mark Rutland wrote:
> If authentication fails, bits are set in the pointer such that it is guaranteed
> to cause a fault if used.
How does user space know the fault is caused by authentication fail?
When GDB is debugging a program, and it failed in pointer
authentication, I assume GDB only knows that the program receives signal
SIGSEGV, but how does GDB or user know why does the program get SIGSEGV?
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
WARNING: multiple messages have this Message-ID (diff)
From: yao.qi@arm.com (Yao Qi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/11] ARMv8.3 pointer authentication userspace support
Date: Tue, 25 Jul 2017 12:32:10 +0100 [thread overview]
Message-ID: <bb507ee1-c7ba-4c73-0d0f-058c4821793c@arm.com> (raw)
In-Reply-To: <1500480092-28480-1-git-send-email-mark.rutland@arm.com>
On 19/07/17 17:01, Mark Rutland wrote:
> If authentication fails, bits are set in the pointer such that it is guaranteed
> to cause a fault if used.
How does user space know the fault is caused by authentication fail?
When GDB is debugging a program, and it failed in pointer
authentication, I assume GDB only knows that the program receives signal
SIGSEGV, but how does GDB or user know why does the program get SIGSEGV?
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
WARNING: multiple messages have this Message-ID (diff)
From: Yao Qi <yao.qi@arm.com>
To: Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: arnd@arndb.de, catalin.marinas@arm.com,
christoffer.dall@linaro.org, Dave.Martin@arm.com,
jiong.wang@arm.com, kvmarm@lists.cs.columbia.edu,
linux-arch@vger.kernel.org, marc.zyngier@arm.com,
suzuki.poulose@arm.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: [PATCH 00/11] ARMv8.3 pointer authentication userspace support
Date: Tue, 25 Jul 2017 12:32:10 +0100 [thread overview]
Message-ID: <bb507ee1-c7ba-4c73-0d0f-058c4821793c@arm.com> (raw)
In-Reply-To: <1500480092-28480-1-git-send-email-mark.rutland@arm.com>
On 19/07/17 17:01, Mark Rutland wrote:
> If authentication fails, bits are set in the pointer such that it is guaranteed
> to cause a fault if used.
How does user space know the fault is caused by authentication fail?
When GDB is debugging a program, and it failed in pointer
authentication, I assume GDB only knows that the program receives signal
SIGSEGV, but how does GDB or user know why does the program get SIGSEGV?
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2017-07-25 11:32 UTC|newest]
Thread overview: 124+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 16:01 [PATCH 00/11] ARMv8.3 pointer authentication userspace support Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` [PATCH 01/11] arm64: docs: describe ELF hwcaps Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-21 17:05 ` Dave Martin
2017-07-21 17:05 ` [kernel-hardening] " Dave Martin
2017-07-21 17:05 ` Dave Martin
2017-07-21 17:05 ` Dave Martin
2017-07-24 10:47 ` Suzuki K Poulose
2017-07-24 10:47 ` [kernel-hardening] " Suzuki K Poulose
2017-07-24 10:47 ` Suzuki K Poulose
2017-08-03 14:49 ` Catalin Marinas
2017-08-03 14:49 ` [kernel-hardening] " Catalin Marinas
2017-08-03 14:49 ` Catalin Marinas
2017-08-03 17:57 ` Kees Cook
2017-08-03 17:57 ` [kernel-hardening] " Kees Cook
2017-08-03 17:57 ` Kees Cook
2017-08-03 17:57 ` Kees Cook
2017-07-19 16:01 ` [PATCH 02/11] asm-generic: mm_hooks: allow hooks to be overridden individually Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` [PATCH 03/11] arm64: add pointer authentication register bits Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` [PATCH 04/11] arm64/cpufeature: add ARMv8.3 id_aa64isar1 bits Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-24 10:54 ` Suzuki K Poulose
2017-07-24 10:54 ` [kernel-hardening] " Suzuki K Poulose
2017-07-24 10:54 ` Suzuki K Poulose
2017-07-19 16:01 ` [PATCH 05/11] arm64/cpufeature: detect pointer authentication Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` [PATCH 06/11] arm64: Don't trap host pointer auth use to EL2 Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-24 10:37 ` Dave Martin
2017-07-24 10:37 ` [kernel-hardening] " Dave Martin
2017-07-24 10:37 ` Dave Martin
2017-07-19 16:01 ` [PATCH 07/11] arm64: add basic pointer authentication support Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-25 15:26 ` Dave Martin
2017-07-25 15:26 ` [kernel-hardening] " Dave Martin
2017-07-25 15:26 ` Dave Martin
2017-07-25 15:26 ` Dave Martin
2017-08-11 7:46 ` Yao Qi
2017-08-11 7:46 ` [kernel-hardening] " Yao Qi
2017-08-11 7:46 ` Yao Qi
2017-08-11 8:45 ` Dave Martin
2017-08-11 8:45 ` [kernel-hardening] " Dave Martin
2017-08-11 8:45 ` Dave Martin
2017-08-11 8:45 ` Dave Martin
2017-07-19 16:01 ` [PATCH 08/11] arm64: expose user PAC bit positions via ptrace Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` [PATCH 09/11] arm64/kvm: preserve host HCR_EL2 value Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-08-01 11:00 ` Christoffer Dall
2017-08-01 11:00 ` [kernel-hardening] " Christoffer Dall
2017-08-01 11:00 ` Christoffer Dall
2017-08-01 11:00 ` Christoffer Dall
2017-07-19 16:01 ` [PATCH 10/11] arm64/kvm: context-switch ptrauth registers Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-08-01 11:00 ` Christoffer Dall
2017-08-01 11:00 ` [kernel-hardening] " Christoffer Dall
2017-08-01 11:00 ` Christoffer Dall
2017-08-01 11:00 ` Christoffer Dall
2017-08-01 14:26 ` Mark Rutland
2017-08-01 14:26 ` [kernel-hardening] " Mark Rutland
2017-08-01 14:26 ` Mark Rutland
2017-08-01 14:32 ` Will Deacon
2017-08-01 14:32 ` [kernel-hardening] " Will Deacon
2017-08-01 14:32 ` Will Deacon
2017-08-01 17:02 ` Christoffer Dall
2017-08-01 17:02 ` [kernel-hardening] " Christoffer Dall
2017-08-01 17:02 ` Christoffer Dall
2017-07-19 16:01 ` [PATCH 11/11] arm64: docs: document pointer authentication Mark Rutland
2017-07-19 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-19 16:01 ` Mark Rutland
2017-07-21 17:05 ` [PATCH 00/11] ARMv8.3 pointer authentication userspace support Dave Martin
2017-07-21 17:05 ` [kernel-hardening] " Dave Martin
2017-07-21 17:05 ` Dave Martin
2017-07-21 17:05 ` Dave Martin
2017-07-25 12:06 ` Mark Rutland
2017-07-25 12:06 ` [kernel-hardening] " Mark Rutland
2017-07-25 12:06 ` Mark Rutland
2017-07-25 14:00 ` Jiong Wang
2017-07-25 14:00 ` [kernel-hardening] " Jiong Wang
2017-07-25 14:00 ` Jiong Wang
2017-07-25 14:00 ` Jiong Wang
2017-08-11 11:29 ` Mark Rutland
2017-08-11 11:29 ` [kernel-hardening] " Mark Rutland
2017-08-11 11:29 ` Mark Rutland
2017-07-24 11:52 ` Yao Qi
2017-07-24 11:52 ` [kernel-hardening] " Yao Qi
2017-07-24 11:52 ` Yao Qi
2017-07-25 11:32 ` Yao Qi [this message]
2017-07-25 11:32 ` [kernel-hardening] " Yao Qi
2017-07-25 11:32 ` Yao Qi
2017-07-25 16:01 ` Mark Rutland
2017-07-25 16:01 ` [kernel-hardening] " Mark Rutland
2017-07-25 16:01 ` Mark Rutland
2017-07-25 14:12 ` [kernel-hardening] " Li Kun
2017-07-25 14:12 ` Li Kun
2017-07-25 14:12 ` Li Kun
2017-07-25 14:12 ` Li Kun
2017-07-25 15:12 ` Mark Rutland
2017-07-25 15:12 ` Mark Rutland
2017-07-25 15:12 ` Mark Rutland
2017-07-25 15:12 ` Mark Rutland
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=bb507ee1-c7ba-4c73-0d0f-058c4821793c@arm.com \
--to=yao.qi@arm.com \
--cc=Dave.Martin@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=jiong.wang@arm.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.