From: Jarkko Sakkinen <jarkko@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Sean Christopherson <seanjc@google.com>,
ira.weiny@intel.com, linux-kernel@vger.kernel.org,
linux-sgx@vger.kernel.org
Subject: Re: [PATCH] x86: Remove unnecessary kmap() from sgx_ioc_enclave_init()
Date: Tue, 2 Feb 2021 19:37:08 +0200 [thread overview]
Message-ID: <YBmNxAW8jYTqg/IF@kernel.org> (raw)
In-Reply-To: <20210201084812.GA3229269@infradead.org>
On Mon, Feb 01, 2021 at 08:48:12AM +0000, Christoph Hellwig wrote:
> On Fri, Jan 29, 2021 at 09:37:30AM -0800, Sean Christopherson wrote:
> > On Thu, Jan 28, 2021, ira.weiny@intel.com wrote:
> > > From: Ira Weiny <ira.weiny@intel.com>
> > >
> > > There is no reason to alloc a page and kmap it to store this temporary
> > > data from the user.
> >
> > Actually, there is, it's just poorly documented. The sigstruct needs to be
> > page aligned, and the token needs to be 512-byte aligned. kmcalloc doesn't
> > guarantee alignment. IIRC things will work until slub_debug is enabled, at
> > which point the natural alignment behavior goes out the window.
>
> Well, there still is absolutely no need for the kmap as you can use
> page_address for a GFP_KERNEL allocation.
Yeah, we do that in sgx_ioc_enclave_create already based on feedback:
secs = kmalloc(PAGE_SIZE, GFP_KERNEL);
if (!secs)
return -ENOMEM;
The kmap() in sgx_ioc_enclave_init() is an unfortunate miss. Let's just
follow the pre-existing pattern.
/Jarkko
next prev parent reply other threads:[~2021-02-02 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 0:14 [PATCH] x86: Remove unnecessary kmap() from sgx_ioc_enclave_init() ira.weiny
2021-01-29 17:37 ` Sean Christopherson
2021-02-01 8:48 ` Christoph Hellwig
2021-02-02 17:37 ` Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-02 1:37 ira.weiny
2021-02-02 18:55 ` Dave Hansen
2021-02-02 22:43 ` 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=YBmNxAW8jYTqg/IF@kernel.org \
--to=jarkko@kernel.org \
--cc=hch@infradead.org \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=seanjc@google.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.