From: Jarkko Sakkinen <jarkko@kernel.org>
To: Haitao Huang <haitao.huang@linux.intel.com>
Cc: "Sakkinen, Jarkko" <jarkko.sakkinen@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
Dave Hansen <dave.hansen@intel.com>,
"Accardi, Kristen C" <kristen.c.accardi@intel.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>
Subject: Re: Testing 5.17 bugfix material
Date: Mon, 24 Jan 2022 19:55:10 +0200 [thread overview]
Message-ID: <Ye7n/vk+MNF3Nc1D@iki.fi> (raw)
In-Reply-To: <Ye7k7b1x8OnQcJgL@iki.fi>
On Mon, Jan 24, 2022 at 07:42:08PM +0200, Jarkko Sakkinen wrote:
> On Sat, Jan 22, 2022 at 01:15:01PM -0600, Haitao Huang wrote:
> > Hi Dave,
> >
> > On Fri, 21 Jan 2022 13:57:50 -0600, Dave Hansen <dave.hansen@intel.com>
> > wrote:
> >
> > > Hi Everyone,
> > >
> > > There are a few SGX fixes that have showed up in the last week or so,
> > > mostly around RAS and fixing the backing storage issues. Could folks
> > > please give this branch a good thrashing?
> > >
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/daveh/devel.git/log/?h=x86/sgx
> > >
> > > I'm planning to send this bunch up to Linus after 5.17-rc1 comes out.
> > >
> > > Kristen, I really dug into the changelogs of your two patches to make it
> > > more clear that they are bugfix and stable@ material. I'd appreciate
> > > some additional eyeballs there.
> >
> > When testing this with a large enclave loaded by Intel runtime, we saw it
> > hang
> > on EADD ioctl and the ioctl never returns.
> >
> > Also noticed the selftest fails on oversub but the return errno is EINTR not
> > ENOMEM as expected.
> >
> > When user space register signal handler with SA_RESTART flag, EINTR would
> > be an auto restart of ioctl. So that might be what's going on with Intel
> > runtime test. And I suspect following code may cause infinite restart of the
> > ioctl:
> >
> > struct sgx_epc_page *sgx_alloc_epc_page(void *owner, bool reclaim)
> > {
> > struct sgx_epc_page *page;
> >
> > for ( ; ; ) {
> > page = __sgx_alloc_epc_page();
> > if (!IS_ERR(page)) {
> > page->owner = owner;
> > break;
> > }
> >
> > if (list_empty(&sgx_active_page_list))<-- should also check
> > sgx_nr_available_backing_pages?
> > return ERR_PTR(-ENOMEM);
I don't think so but why do you think it should?
> >
> > if (!reclaim) {
> > page = ERR_PTR(-EBUSY);
> > break;
> > }
> >
> > if (signal_pending(current)) {
> > page = ERR_PTR(-ERESTARTSYS);<---- this is the only exit of
> > the for loop when backing store limit reaches.
> > break;
> > }
> >
> > sgx_reclaim_pages(); <---- no checking for backing store fail due
> > to limit here.
Initially I'd think you're making here the right conclusion. Given the
limit sgx_reclaim_pages() should return e.g. boolean or int to tell that
we are out of backing storage.
Kristen?
> > cond_resched();
> > }
> >
> > Thanks
> > Haitao
The reason was that it was not x86/sgx branch of tip but this:
https://git.kernel.org/pub/scm/linux/kernel/git/daveh/devel.git/log/?h=x86/sgx
Sorry for initial reject.
BR, Jarkko
next prev parent reply other threads:[~2022-01-24 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 19:57 Testing 5.17 bugfix material Dave Hansen
2022-01-22 19:15 ` Haitao Huang
2022-01-24 17:42 ` Jarkko Sakkinen
2022-01-24 17:55 ` Jarkko Sakkinen [this message]
2022-01-25 4:27 ` Haitao Huang
2022-01-22 23:41 ` Jarkko Sakkinen
2022-01-24 17:44 ` Accardi, Kristen C
2022-01-24 17:56 ` Jarkko Sakkinen
2022-01-24 20:59 ` Accardi, Kristen C
2022-01-25 12:06 ` Jarkko Sakkinen
2022-01-24 17:58 ` 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=Ye7n/vk+MNF3Nc1D@iki.fi \
--to=jarkko@kernel.org \
--cc=dave.hansen@intel.com \
--cc=haitao.huang@linux.intel.com \
--cc=jarkko.sakkinen@intel.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=tony.luck@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