From: Kai Huang <kai.huang@intel.com>
To: linux-sgx@vger.kernel.org, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, bp@alien8.de, seanjc@google.com,
jarkko@kernel.org, dave.hansen@intel.com, tglx@linutronix.de,
mingo@redhat.com, Yang Zhong <yang.zhong@intel.com>,
Kai Huang <kai.huang@intel.com>
Subject: [PATCH] x86/sgx: Add missing xa_destroy() when virtual EPC is destroyed
Date: Tue, 15 Jun 2021 22:16:39 +1200 [thread overview]
Message-ID: <20210615101639.291929-1-kai.huang@intel.com> (raw)
xa_destroy() needs to be called to destroy virtual EPC's page arra
before calling kfree() to free the virtual EPC. Currently it is not
calaled. Add the missing xa_destroy() to fix.
Fixes: 540745ddbc70 ("x86/sgx: Introduce virtual EPC for use by KVM guests")
Tested-by: Yang Zhong <yang.zhong@intel.com>
Signed-off-by: Kai Huang <kai.huang@intel.com>
---
arch/x86/kernel/cpu/sgx/virt.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/kernel/cpu/sgx/virt.c b/arch/x86/kernel/cpu/sgx/virt.c
index 6ad165a5c0cc..64511c4a5200 100644
--- a/arch/x86/kernel/cpu/sgx/virt.c
+++ b/arch/x86/kernel/cpu/sgx/virt.c
@@ -212,6 +212,7 @@ static int sgx_vepc_release(struct inode *inode, struct file *file)
list_splice_tail(&secs_pages, &zombie_secs_pages);
mutex_unlock(&zombie_secs_pages_lock);
+ xa_destroy(&vepc->page_array);
kfree(vepc);
return 0;
--
2.31.1
next reply other threads:[~2021-06-15 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 10:16 Kai Huang [this message]
2021-06-15 13:20 ` [PATCH] x86/sgx: Add missing xa_destroy() when virtual EPC is destroyed Jarkko Sakkinen
2021-06-16 0:30 ` Kai Huang
2021-06-17 14:34 ` Borislav Petkov
2021-06-18 0:04 ` Kai Huang
2021-06-18 5:15 ` Borislav Petkov
2021-06-15 15:39 ` Dave Hansen
2021-06-16 0:28 ` Kai Huang
2021-06-15 16:16 ` [tip: x86/urgent] " tip-bot2 for Kai Huang
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=20210615101639.291929-1-kai.huang@intel.com \
--to=kai.huang@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yang.zhong@intel.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;
as well as URLs for NNTP newsgroup(s).