linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nathan Lynch <nathanl@linux.ibm.com>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org
Cc: ajd@linux.ibm.com, nayna@linux.ibm.com, jmorris@namei.org,
	paul@paul-moore.com, gcwilson@linux.ibm.com, serge@hallyn.com
Subject: Re: [PATCH v2 0/2] powerpc/pseries: restrict error injection and DT changes when locked down
Date: Wed, 05 Oct 2022 00:25:51 +1100	[thread overview]
Message-ID: <166488995179.779920.16022330580724234832.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220926131643.146502-1-nathanl@linux.ibm.com>

On Mon, 26 Sep 2022 08:16:41 -0500, Nathan Lynch wrote:
> Add two new lockdown reasons for use in powerpc's pseries platform
> code.
> 
> The pseries platform allows hardware-level error injection via certain
> calls to the RTAS (Run Time Abstraction Services) firmware. ACPI-based
> error injection is already restricted in lockdown; this facility
> should be restricted for the same reasons.
> 
> [...]

Applied to powerpc/next.

[1/2] powerpc/pseries: block untrusted device tree changes when locked down
      https://git.kernel.org/powerpc/c/99df7a2810b6d24651d4887ab61a142e042fb235
[2/2] powerpc/rtas: block error injection when locked down
      https://git.kernel.org/powerpc/c/b8f3e48834fe8c86b4f21739c6effd160e2c2c19

cheers

      parent reply	other threads:[~2022-10-04 13:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 13:16 [PATCH v2 0/2] powerpc/pseries: restrict error injection and DT changes when locked down Nathan Lynch
2022-09-26 13:16 ` [PATCH v2 1/2] powerpc/pseries: block untrusted device tree " Nathan Lynch
2022-09-26 22:39   ` Paul Moore
2022-09-28  9:51   ` Andrew Donnellan
2022-09-26 13:16 ` [PATCH v2 2/2] powerpc/rtas: block error injection " Nathan Lynch
2022-09-26 22:41   ` Paul Moore
2022-09-28 10:02   ` Andrew Donnellan
2022-09-28 16:23     ` Nathan Lynch
2022-10-04 13:25 ` Michael Ellerman [this message]

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=166488995179.779920.16022330580724234832.b4-ty@ellerman.id.au \
    --to=patch-notifications@ellerman.id.au \
    --cc=ajd@linux.ibm.com \
    --cc=gcwilson@linux.ibm.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nathanl@linux.ibm.com \
    --cc=nayna@linux.ibm.com \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.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).