From: Dave Hansen <dave.hansen@intel.com>
To: Li RongQing <lirongqing@baidu.com>,
kirill.shutemov@linux.intel.com, dave.hansen@linux.intel.com,
x86@kernel.org, linux-coco@lists.linux.dev, "Edgecombe,
Rick P" <rick.p.edgecombe@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] virt: tdx-guest: Fix the decrypted failure memory free
Date: Thu, 13 Jun 2024 09:07:39 -0700 [thread overview]
Message-ID: <32eddae1-14bf-42dd-afdd-7dca8bc8a131@intel.com> (raw)
In-Reply-To: <20240613111931.43123-1-lirongqing@baidu.com>
On 6/13/24 04:19, Li RongQing wrote:
> When set_memory_decrypted() fails, the memory should be encrypted
> via set_memory_encrypted(); if encrypting the memory fails, leak it
Please, always cc LKML on this stuff.
Second, Rick was looking in this area, but I'm not sure we ever applied
his patches. The idea was to never leak memory silently in these
failures. Doesn't this silently leak memory?
next parent reply other threads:[~2024-06-13 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240613111931.43123-1-lirongqing@baidu.com>
2024-06-13 16:07 ` Dave Hansen [this message]
2024-06-13 16:13 ` [PATCH] virt: tdx-guest: Fix the decrypted failure memory free Edgecombe, Rick P
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=32eddae1-14bf-42dd-afdd-7dca8bc8a131@intel.com \
--to=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--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