The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86/xen: fix xen_hypercall_hvm() to not clobber %rbx
Date: Wed, 5 Feb 2025 11:04:34 +0100	[thread overview]
Message-ID: <a2b93e7c-be69-4cfd-8b34-de22dda4cb6f@suse.com> (raw)
In-Reply-To: <b70e246a-5e5e-431c-9b85-dc4644df7bd9@citrix.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1850 bytes --]

On 05.02.25 10:38, Andrew Cooper wrote:
> On 05/02/2025 9:17 am, Jürgen Groß wrote:
>> On 05.02.25 10:16, Andrew Cooper wrote:
>>> On 05/02/2025 9:10 am, Juergen Gross wrote:
>>>> xen_hypercall_hvm(), which is used when running as a Xen PVH guest at
>>>> most only once during early boot, is clobbering %rbx. Depending on
>>>> whether the caller relies on %rbx to be preserved across the call or
>>>> not, this clobbering might result in an early crash of the system.
>>>>
>>>> This can be avoided by not modifying %rbx in xen_hypercall_hvm().
>>>>
>>>> Fixes: b4845bb63838 ("x86/xen: add central hypercall functions")
>>>> Signed-off-by: Juergen Gross <jgross@suse.com>
>>>> ---
>>>>    arch/x86/xen/xen-head.S | 3 +--
>>>>    1 file changed, 1 insertion(+), 2 deletions(-)
>>>>
>>>> diff --git a/arch/x86/xen/xen-head.S b/arch/x86/xen/xen-head.S
>>>> index 9252652afe59..4378b817ed32 100644
>>>> --- a/arch/x86/xen/xen-head.S
>>>> +++ b/arch/x86/xen/xen-head.S
>>>> @@ -117,8 +117,7 @@ SYM_FUNC_START(xen_hypercall_hvm)
>>>
>>> The 32bit case, out of context up here, also clobbers %ebx.
>>>
>>> ~Andrew
>>>
>>>>        pop %ebx
>>
>> It does not, as this part of the context is showing.
> 
> Hmm, so it is, and worse, it can't be changed to match the 64bit side.
> That's nasty.
> 
> But while I'm here looking at the code, what's up with
> 
> #ifdef CONFIG_FRAME_POINTER
>          pushq $0        /* Dummy push for stack alignment. */
> #endif
> 
> ?
> 
> That's covered by FRAME_{START,END} normally, and Linux's preferred
> stack alignment is 8 not 16.

I've added this due to a review comment by Jan. As he is more into ABI
matters, I believed him.

Google is telling me you are right, so I'll remove those extra hunks in
V2 of the patch adding FRAME_END.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2025-02-05 10:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05  9:10 [PATCH] x86/xen: fix xen_hypercall_hvm() to not clobber %rbx Juergen Gross
2025-02-05  9:16 ` Andrew Cooper
2025-02-05  9:17   ` Jürgen Groß
2025-02-05  9:38     ` Andrew Cooper
2025-02-05 10:04       ` Jürgen Groß [this message]
2025-02-05 10:30         ` Jan Beulich
2025-02-05  9:54 ` Jan Beulich
2025-02-05 10:07   ` Jürgen Groß

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=a2b93e7c-be69-4cfd-8b34-de22dda4cb6f@suse.com \
    --to=jgross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.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