From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Aaron Lu" <aaron.lu@intel.com>
Cc: "Dave Hansen" <dave.hansen@linux.intel.com>, <x86@kernel.org>,
<linux-sgx@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Zhimin Luo" <zhimin.luo@intel.com>
Subject: Re: [PATCH] x86/sgx: Fix deadloop in __sgx_alloc_epc_page()
Date: Wed, 04 Sep 2024 17:17:24 +0300 [thread overview]
Message-ID: <D3XKBPX6DBX4.2BYXD4D5NZGWZ@kernel.org> (raw)
In-Reply-To: <Zte6ROmqrwdCSIn8@ziqianlu-kbl>
On Wed Sep 4, 2024 at 4:39 AM EEST, Aaron Lu wrote:
> On Tue, Sep 03, 2024 at 07:05:40PM +0300, Jarkko Sakkinen wrote:
> > On Fri Aug 30, 2024 at 9:14 AM EEST, Aaron Lu wrote:
> > > On Thu, Aug 29, 2024 at 07:44:13PM +0300, Jarkko Sakkinen wrote:
> > > > On Thu Aug 29, 2024 at 5:38 AM EEST, Aaron Lu wrote:
> > > > > When current node doesn't have a EPC section configured by firmware and
> > > > > all other EPC sections memory are used up, CPU can stuck inside the
> > > > > while loop in __sgx_alloc_epc_page() forever and soft lockup will happen.
> > > > > Note how nid_of_current will never equal to nid in that while loop because
> > > > ~~~~
> > > >
> > > > Oh *that* while loop ;-) Please be more specific.
> > >
> > > What about:
> > > Note how nid_of_current will never be equal to nid in the while loop that
> > > searches an available EPC page from remote nodes because nid_of_current is
> > > not set in sgx_numa_mask.
> >
> > That would work I think!
>
> While rewriting the changelog, I find it more natural to explain this
> "while loop" when I first mentioned it, i.e.
>
> When the current node doesn't have an EPC section configured by firmware
> and all other EPC sections are used up, CPU can get stuck inside the
> while loop that looks for an available EPC page from remote nodes
> indefinitely, leading to a soft lockup. Note how nid_of_current will
> never be equal to nid in that while loop because nid_of_current is not
> set in sgx_numa_mask.
>
> I hope this looks fine to you.
Yes, it is. I just want the storyline to the commit message as
a reminder why we did this, that's all. It helps a lot later on
when having to look into commit history.
BR, Jarkko
prev parent reply other threads:[~2024-09-04 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 2:38 [PATCH] x86/sgx: Fix deadloop in __sgx_alloc_epc_page() Aaron Lu
2024-08-29 7:47 ` Huang, Kai
2024-08-29 7:56 ` Huang, Kai
2024-08-29 13:22 ` Aaron Lu
2024-08-29 15:17 ` Dave Hansen
2024-08-30 6:02 ` Aaron Lu
2024-08-30 14:03 ` Dave Hansen
2024-09-02 7:57 ` Aaron Lu
2024-08-29 16:44 ` Jarkko Sakkinen
2024-08-30 6:14 ` Aaron Lu
2024-09-03 16:05 ` Jarkko Sakkinen
2024-09-04 1:39 ` Aaron Lu
2024-09-04 14:17 ` Jarkko Sakkinen [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=D3XKBPX6DBX4.2BYXD4D5NZGWZ@kernel.org \
--to=jarkko@kernel.org \
--cc=aaron.lu@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=x86@kernel.org \
--cc=zhimin.luo@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 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.