From: Pavel Machek <pavel@ucw.cz>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
jarkko.sakkinen@linux.intel.com
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 4.19.157 -- fixing SGX problem?
Date: Thu, 12 Nov 2020 20:24:32 +0100 [thread overview]
Message-ID: <20201112192432.GA10247@amd> (raw)
In-Reply-To: <160504197091230@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
Hi!
> I'm announcing the release of the 4.19.157 kernel.
>
> Please see the 5.9.8 announcement if you are curious if you should
> upgrade or not:
> https://lore.kernel.org/lkml/1605041246232108@kroah.com/
Quoting:
# Hint, if you are using SGX, then upgrade. And then possibly
# reconsider
# the decisions you have recently made that caused you to write special
# code to use that crazy thing. Personally, it still feels like a
# solution in search of a problem.
I agree with you that SGX is "crazy", but this makes no sense.
SGX is expected to protect enclave even from root. How does making
interface root-only solve that?
Plus, SGX is not in 4.19. I don't believe it is in mainline, either,
as the patches are still reposted. We are at v40 now...
Date: Wed, 4 Nov 2020 16:54:06 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Subject: [PATCH v40 00/24] Intel SGX foundations
ls arch/x86/kernel/cpu/sgx shows nothing in mainline. It shows nothing
in -next, either.
Confused,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2020-11-12 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 20:59 Linux 4.19.157 Greg Kroah-Hartman
2020-11-10 20:59 ` Greg Kroah-Hartman
2020-11-12 19:24 ` Pavel Machek [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=20201112192432.GA10247@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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.