From: "Li,Rongqing" <lirongqing@baidu.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: RE: [外部邮件] Re: [PATCH] virt: tdx-guest: Fix the decrypted failure memory free
Date: Fri, 14 Jun 2024 04:48:18 +0000 [thread overview]
Message-ID: <f6813dfbfc7c41d580656826724f5f9e@baidu.com> (raw)
In-Reply-To: <0f6752d0ff95ba9d4fdafdfba1b37c9a140c773d.camel@intel.com>
> In the other cases the general consensus was to not optimize for this failure.
> As in, don't try to re-encrypt the pages first, just give up and leak them on the
> first failure. So the fix could just be to remove the free_pages_exact() call. I
> think we should stick with that pattern.
>
I see, I will send v2
Thanks
-Li
prev parent reply other threads:[~2024-06-14 5:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 11:19 [PATCH] virt: tdx-guest: Fix the decrypted failure memory free Li RongQing
2024-06-13 16:07 ` Dave Hansen
2024-06-13 16:13 ` Edgecombe, Rick P
2024-06-13 16:10 ` Edgecombe, Rick P
2024-06-14 4:48 ` Li,Rongqing [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=f6813dfbfc7c41d580656826724f5f9e@baidu.com \
--to=lirongqing@baidu.com \
--cc=dave.hansen@linux.intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=rick.p.edgecombe@intel.com \
--cc=x86@kernel.org \
/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).