From: Jiri Slaby <jirislaby@kernel.org>
To: Dexuan Cui <decui@microsoft.com>, Borislav Petkov <bp@alien8.de>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
"open list:X86 TRUST DOMAIN EXTENSIONS (TDX)"
<linux-coco@lists.linux.dev>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>,
Michael Kelley <mikelley@microsoft.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Kai Huang <kai.huang@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] x86/tdx: Support vmalloc() for tdx_enc_status_changed()
Date: Tue, 9 Jul 2024 07:45:55 +0200 [thread overview]
Message-ID: <cabc0b75-6536-4aee-9d6b-57712bb2e1a8@kernel.org> (raw)
In-Reply-To: <SA1PR21MB1317816DFCE6EF38A92CF254BFDA2@SA1PR21MB1317.namprd21.prod.outlook.com>
On 08. 07. 24, 23:45, Dexuan Cui wrote:
>> From: Borislav Petkov <bp@alien8.de>
>>> Cc: stable@vger.kernel.org
>>
>> Why?
>>
>> Fixes: what?
>
> Please refer to my reply above.
>
> This is not to fix a buggy commit. The described scenario never worked before,
> so I suppose a "Fixes:" tag is not needed.
If you cc stable, fixes *is* actually needed. So again, why to cc stable
when this is a feature? I suppose you will receive a Greg-bot reply
anyway ;).
>> From reading this, it seems to me you need to brush up on
>> https://kernel.org/doc/html/latest/process/submitting-patches.html
> Thanks for the link! I read it and did learn something.
>
>> while waiting.
...> I hope I have provided a satisfactory reply above.
>
> How do you like the v12 below? It's also attached.
> If this looks good to you, I can post it today or tomorrow.
Then you need to enumerate what changed in v1..v12. In every single
revision. Do it under the "---" line below. And add v12 to the subject
as you did below (but not above).
> From 132f656fdbf3b4f00752140aac10f3674b598b5a Mon Sep 17 00:00:00 2001
> From: Dexuan Cui <decui@microsoft.com>
> Date: Mon, 20 May 2024 19:12:38 -0700
> Subject: [PATCH v12] x86/tdx: Fix set_memory_decrypted() for vmalloc() buffers
>
...
>
> hv_netvsc is the first user of vmalloc() + set_memory_decrypted(), which
> is why nobody noticed this until now.
>
> Co-developed-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Signed-off-by: Dexuan Cui <decui@microsoft.com>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> Reviewed-by: Michael Kelley <mikelley@microsoft.com>
> Reviewed-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
> Reviewed-by: Rick Edgecombe <rick.p.edgecombe@intel.com>
> Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com>
> Acked-by: Kai Huang <kai.huang@intel.com>
> Cc: stable@vger.kernel.org # 6.6+
> ---
The revision log belongs here. I believe you had to meet that
requirement in the submittingpatches document.
And to avoid future confusion, I would list the links to received
"Signed-off-by"/"Reviewed-by"s here too. The links you listed earlier.
> arch/x86/coco/tdx/tdx.c | 43 ++++++++++++++++++++++++++++++++++-------
> 1 file changed, 36 insertions(+), 7 deletions(-)
regards,
--
js
suse labs
next prev parent reply other threads:[~2024-07-09 5:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 18:39 [PATCH] x86/tdx: Support vmalloc() for tdx_enc_status_changed() Dexuan Cui
2024-07-08 19:17 ` Borislav Petkov
2024-07-08 21:45 ` Dexuan Cui
2024-07-09 5:45 ` Jiri Slaby [this message]
2024-07-09 7:13 ` Dexuan Cui
2024-07-09 11:06 ` Borislav Petkov
2024-07-10 7:48 ` Dexuan Cui
2024-07-10 7:53 ` Dexuan Cui
2024-07-10 8:15 ` Borislav Petkov
2024-07-10 9:20 ` Dexuan Cui
2024-07-10 9:29 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2024-05-21 2:12 Dexuan Cui
2024-06-19 1:02 ` Dexuan Cui
2024-06-28 10:04 ` Kirill A. Shutemov
2024-06-28 19:24 ` Dexuan Cui
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=cabc0b75-6536-4aee-9d6b-57712bb2e1a8@kernel.org \
--to=jirislaby@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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