From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: eric.snowberg@oracle.com, john.haxby@oracle.com,
todd.vierling@oracle.com
Cc: David Howells <dhowells@redhat.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
acpi4asus-user@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
Matthew Garrett <mjg59@srcf.ucam.org>,
Thomas Gleixner <tglx@linutronix.de>, Greg KH <greg@kroah.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Matthew Garrett <matthewgarrett@google.com>,
James Morris <jmorris@namei.org>
Subject: Re: [PATCH RFC UEK5 5/7] debugfs: Restrict debugfs when the kernel is locked down
Date: Tue, 20 Oct 2020 17:08:08 -0400 [thread overview]
Message-ID: <20201020210808.GB21080@char.us.oracle.com> (raw)
In-Reply-To: <20201020210004.18977-6-konrad.wilk@oracle.com>
On Tue, Oct 20, 2020 at 05:00:02PM -0400, Konrad Rzeszutek Wilk wrote:
> Disallow opening of debugfs files that might be used to muck around when
..snip..
> [Backport:
> Since UEK5 by default is confidentiality we have to outright
> disallow debugfs if the default mode is selected. Hence the
> call to __kernel_is_confidentiality_mode to help us.
>
> If we are in integrity lockdown mode, we can enable debugfs
> IF they match with the above 1-3 criteria]
<sigh>
And that is what I get for _not_ doing --suppress-cc=all
My apologies for spamming you all!
<goes to hide in the corner of shame>
next prev parent reply other threads:[~2020-10-20 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201020210004.18977-1-konrad.wilk@oracle.com>
2020-10-20 20:59 ` [PATCH RFC UEK5 2/7] bpf: Restrict bpf when kernel lockdown is in confidentiality mode Konrad Rzeszutek Wilk
2020-10-20 21:06 ` Konrad Rzeszutek Wilk
2020-10-20 21:00 ` [PATCH RFC UEK5 5/7] debugfs: Restrict debugfs when the kernel is locked down Konrad Rzeszutek Wilk
2020-10-20 21:08 ` Konrad Rzeszutek Wilk [this message]
2020-10-28 11:37 ` Hans de Goede
2020-10-20 21:00 ` [PATCH RFC UEK5 6/7] debugfs: Return -EPERM when " Konrad Rzeszutek Wilk
2020-10-20 21:11 ` Konrad Rzeszutek Wilk
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=20201020210808.GB21080@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=andy.shevchenko@gmail.com \
--cc=dhowells@redhat.com \
--cc=eric.snowberg@oracle.com \
--cc=greg@kroah.com \
--cc=jmorris@namei.org \
--cc=john.haxby@oracle.com \
--cc=matthewgarrett@google.com \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=todd.vierling@oracle.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.