linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Derrick McKee <derrick.mckee@gmail.com>
To: Yianni Giannaris <yiannig@mit.edu>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	 mark.rutland@arm.com, suzuki.poulose@arm.com,
	 Catalin Marinas <catalin.marinas@arm.com>,
	james.morse@arm.com, amit.kachhap@arm.com, will@kernel.org
Subject: PAC key changes when kernel code is preempted
Date: Fri, 30 Apr 2021 10:40:04 -0400	[thread overview]
Message-ID: <CAJoBWHxHqUY427-62=YtGDtnGrcSyOXiKTF=A+Vswbt0K_7c+w@mail.gmail.com> (raw)

Hi,

I am noticing that when kernel code is preempted, PAC keys seem to
change when resuming execution.  For instance, when I read
APDAKeyHi_EL1 and APDAKeyLo_EL1, sleep, and read them again, the
values are different.  Is this the intended behavior?  If so, how can
I ensure that the keys do not change?  The different keys are causing
PAC authentication to fail on pointers signed using the stale key.
Thanks.

--
Derrick McKee
Email: derrick.mckee@gmail.com

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

             reply	other threads:[~2021-04-30 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 14:40 Derrick McKee [this message]
2021-04-30 15:04 ` PAC key changes when kernel code is preempted Mark Rutland
2021-05-07 20:24   ` Derrick McKee
2021-05-20 15:18   ` [PATCH] Ensure kernel AI key is not changed on fork Derrick McKee
2021-05-20 16:00     ` Mark Rutland
2021-05-20 18:24       ` Derrick McKee

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='CAJoBWHxHqUY427-62=YtGDtnGrcSyOXiKTF=A+Vswbt0K_7c+w@mail.gmail.com' \
    --to=derrick.mckee@gmail.com \
    --cc=amit.kachhap@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=will@kernel.org \
    --cc=yiannig@mit.edu \
    /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).