All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Will Deacon <will@kernel.org>, Boyan Karatotev <boyan.karatotev@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	amit.kachhap@arm.com, boian4o1@gmail.com,
	Shuah Khan <shuah@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH v2 0/4] kselftests/arm64: add PAuth tests
Date: Mon, 14 Sep 2020 13:24:05 +0100	[thread overview]
Message-ID: <626cb564-22e1-4f2d-47c7-f38439c5fb29@arm.com> (raw)
In-Reply-To: <20200911181558.GA21319@willie-the-truck>

Hi Will,

On 9/11/20 7:15 PM, Will Deacon wrote:
> On Mon, Aug 31, 2020 at 12:04:46PM +0100, Boyan Karatotev wrote:
>> Pointer Authentication (PAuth) is a security feature introduced in ARMv8.3.
>> It introduces instructions to sign addresses and later check for potential
>> corruption using a second modifier value and one of a set of keys. The
>> signature, in the form of the Pointer Authentication Code (PAC), is stored
>> in some of the top unused bits of the virtual address (e.g. [54: 49] if
>> TBID0 is enabled and TnSZ is set to use a 48 bit VA space). A set of
>> controls are present to enable/disable groups of instructions (which use
>> certain keys) for compatibility with libraries that do not utilize the
>> feature. PAuth is used to verify the integrity of return addresses on the
>> stack with less memory than the stack canary.
> 
> Any chance of a v3 addressing the couple of small comments from Dave on
> the third patch, please? Then I can pick up the whole lot for 5.10.
> 

Boyan is on it. Thank you.

> Cheers,
> 
> Will
> 

-- 
Regards,
Vincenzo

WARNING: multiple messages have this Message-ID (diff)
From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Will Deacon <will@kernel.org>, Boyan Karatotev <boyan.karatotev@arm.com>
Cc: boian4o1@gmail.com, Catalin Marinas <catalin.marinas@arm.com>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	amit.kachhap@arm.com, Shuah Khan <shuah@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] kselftests/arm64: add PAuth tests
Date: Mon, 14 Sep 2020 13:24:05 +0100	[thread overview]
Message-ID: <626cb564-22e1-4f2d-47c7-f38439c5fb29@arm.com> (raw)
In-Reply-To: <20200911181558.GA21319@willie-the-truck>

Hi Will,

On 9/11/20 7:15 PM, Will Deacon wrote:
> On Mon, Aug 31, 2020 at 12:04:46PM +0100, Boyan Karatotev wrote:
>> Pointer Authentication (PAuth) is a security feature introduced in ARMv8.3.
>> It introduces instructions to sign addresses and later check for potential
>> corruption using a second modifier value and one of a set of keys. The
>> signature, in the form of the Pointer Authentication Code (PAC), is stored
>> in some of the top unused bits of the virtual address (e.g. [54: 49] if
>> TBID0 is enabled and TnSZ is set to use a 48 bit VA space). A set of
>> controls are present to enable/disable groups of instructions (which use
>> certain keys) for compatibility with libraries that do not utilize the
>> feature. PAuth is used to verify the integrity of return addresses on the
>> stack with less memory than the stack canary.
> 
> Any chance of a v3 addressing the couple of small comments from Dave on
> the third patch, please? Then I can pick up the whole lot for 5.10.
> 

Boyan is on it. Thank you.

> Cheers,
> 
> Will
> 

-- 
Regards,
Vincenzo

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-09-14 12:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 11:04 [PATCH v2 0/4] kselftests/arm64: add PAuth tests Boyan Karatotev
2020-08-31 11:04 ` Boyan Karatotev
2020-08-31 11:04 ` [PATCH v2 1/4] kselftests/arm64: add a basic Pointer Authentication test Boyan Karatotev
2020-08-31 11:04   ` Boyan Karatotev
2020-09-16 12:11   ` Amit Kachhap
2020-09-16 12:11     ` Amit Kachhap
2020-09-17 13:38     ` Boyan Karatotev
2020-09-17 13:38       ` Boyan Karatotev
2020-08-31 11:04 ` [PATCH v2 2/4] kselftests/arm64: add nop checks for PAuth tests Boyan Karatotev
2020-08-31 11:04   ` Boyan Karatotev
2020-08-31 11:04 ` [PATCH v2 3/4] kselftests/arm64: add PAuth test for whether exec() changes keys Boyan Karatotev
2020-08-31 11:04   ` Boyan Karatotev
2020-09-02 17:08   ` Dave Martin
2020-09-02 17:08     ` Dave Martin
2020-09-03 10:48     ` Boyan Karatotev
2020-09-03 10:48       ` Boyan Karatotev
2020-09-07 10:35       ` Dave Martin
2020-09-07 10:35         ` Dave Martin
2020-08-31 11:04 ` [PATCH v2 4/4] kselftests/arm64: add PAuth tests for single threaded consistency and key uniqueness Boyan Karatotev
2020-08-31 11:04   ` Boyan Karatotev
2020-08-31 21:04 ` [PATCH v2 0/4] kselftests/arm64: add PAuth tests Shuah Khan
2020-08-31 21:04   ` Shuah Khan
2020-09-11 18:15 ` Will Deacon
2020-09-11 18:15   ` Will Deacon
2020-09-14 12:24   ` Vincenzo Frascino [this message]
2020-09-14 12:24     ` Vincenzo Frascino

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=626cb564-22e1-4f2d-47c7-f38439c5fb29@arm.com \
    --to=vincenzo.frascino@arm.com \
    --cc=amit.kachhap@arm.com \
    --cc=boian4o1@gmail.com \
    --cc=boyan.karatotev@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=will@kernel.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 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.