From: Reinette Chatre <reinette.chatre@intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, tim.gardner@canonical.com,
jarkko@kernel.org, shuah@kernel.org, linux-sgx@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/sgx: remove checks for file execute permissions
Date: Mon, 21 Jun 2021 14:08:10 -0700 [thread overview]
Message-ID: <121f7215-f11d-2533-b736-9f18516c3220@intel.com> (raw)
In-Reply-To: <20210621190556.4B5DCBB1@viggo.jf.intel.com>
Hi Dave,
On 6/21/2021 12:05 PM, Dave Hansen wrote:
>
> The SGX selftests can fail for a bunch of non-obvious reasons
> like 'noexec' permissions on /dev (which is the default *EVERYWHERE*
> it seems).
>
> A new test mistakenly also looked for +x permission on the
> /dev/sgx_enclave. File execute permissions really only apply to
> the ability of execve() to work on a file, *NOT* on the ability
> for an application to map the file with PROT_EXEC. SGX needs to
> mmap(PROT_EXEC), but doesn't need to execve() the device file.
>
> Remove the check.
>
> Fixes: 4284f7acb78b ("selftests/sgx: Improve error detection and messages")
> Reported-by: Tim Gardner <tim.gardner@canonical.com>
> Cc: Jarkko Sakkinen <jarkko@kernel.org>
> Cc: Reinette Chatre <reinette.chatre@intel.com>
> Cc: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: Shuah Khan <shuah@kernel.org>
> Cc: linux-sgx@vger.kernel.org
> Cc: linux-kselftest@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
>
Thank you very much for fixing this. With this applied the SGX tests are
able to run again on my system.
Tested-by: Reinette Chatre <reinette.chatre@intel.com>
I think it is missing a "Signed-off-by".
Reinette
next prev parent reply other threads:[~2021-06-21 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 19:05 [PATCH] selftests/sgx: remove checks for file execute permissions Dave Hansen
2021-06-21 21:08 ` Reinette Chatre [this message]
2021-06-21 21:18 ` Dave Hansen
2021-06-24 0:40 ` Shuah Khan
2021-06-23 13:41 ` Jarkko Sakkinen
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=121f7215-f11d-2533-b736-9f18516c3220@intel.com \
--to=reinette.chatre@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-sgx@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=tim.gardner@canonical.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