From: Marc Zyngier <maz@kernel.org>
To: pnagar@codeaurora.org
Cc: Ard Biesheuvel <ardb@kernel.org>, Will Deacon <will@kernel.org>,
arnd@arndb.de, jmorris@namei.org, serge@hallyn.com,
paul@paul-moore.com, stephen.smalley.work@gmail.com,
eparis@parisplace.org, linux-security-module@vger.kernel.org,
selinux@vger.kernel.org, linux-arch@vger.kernel.org,
casey@schaufler-ca.com, ndesaulniers@google.com,
dhowells@redhat.com, ojeda@kernel.org, psodagud@codeaurora.org,
nmardana@codeaurora.org, johan@kernel.org, joe@perches.com,
jeyu@kernel.org, linux-kernel@vger.kernel.org,
Quentin Perret <qperret@google.com>
Subject: Re: [PATCH] RTIC: selinux: ARM64: Move selinux_state to a separate page
Date: Mon, 22 Feb 2021 10:56:57 +0000 [thread overview]
Message-ID: <87h7m41ibq.wl-maz@kernel.org> (raw)
In-Reply-To: <5f33e59bf9c01ed5c33a9c3cbe277615@codeaurora.org>
On Mon, 22 Feb 2021 04:58:41 +0000,
pnagar@codeaurora.org wrote:
>
> On 2021-02-17 15:45, Marc Zyngier wrote:
[...]
> > +1 on that. Even if, as I suspect, this is targeting some unspecified
> > hypervisor that is not KVM, the first course of action should be for
> > this to be implemented in the kernel's own hypervisor first so that
> > anyone can review understand what is at play.
> >
> > Thanks,
> >
> > M.
>
> Thank you for your comments. The key value add of the feature is a
> third party independent entity keeping a watch on crucial kernel
> assets, such that in case the kernel itself is compromised, still,
> the protection can remain intact. Can this be achieved if the
> implementation is done in KVM? I've limited knowledge of KVM
> currently, can surely look into more details for a better
> understanding.
[+Quentin]
KVM/arm64 doesn't currently support Stage-2 mappings on the host side,
but there are patches[1] on the list that implement this
functionality, and that I'm hoping to get in 5.13 (no pressure,
Quentin... ;-).
This could also be implemented with the current KVM code though, as a
PV service to guests, and I'd suggest looking into that as an initial
approach.
Thanks,
M.
[1] https://lore.kernel.org/r/20210108121524.656872-1-qperret@google.com
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-02-22 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 10:17 [PATCH] RTIC: selinux: ARM64: Move selinux_state to a separate page Preeti Nagar
2021-02-16 18:09 ` Nick Desaulniers
2021-02-22 6:54 ` pnagar
2021-02-16 20:32 ` Miguel Ojeda
2021-02-22 5:06 ` pnagar
2021-02-17 9:42 ` Will Deacon
2021-02-17 9:53 ` Ard Biesheuvel
2021-02-22 7:14 ` pnagar
2021-02-17 10:15 ` Marc Zyngier
2021-02-22 4:58 ` pnagar
2021-02-22 10:56 ` Marc Zyngier [this message]
2021-02-22 9:50 ` peter enderborg
2021-03-05 2:21 ` Paul Moore
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=87h7m41ibq.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=casey@schaufler-ca.com \
--cc=dhowells@redhat.com \
--cc=eparis@parisplace.org \
--cc=jeyu@kernel.org \
--cc=jmorris@namei.org \
--cc=joe@perches.com \
--cc=johan@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=nmardana@codeaurora.org \
--cc=ojeda@kernel.org \
--cc=paul@paul-moore.com \
--cc=pnagar@codeaurora.org \
--cc=psodagud@codeaurora.org \
--cc=qperret@google.com \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.com \
--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.