mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Beulich <jbeulich@suse.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH] x86: drop bogus "cc" clobber from __try_cmpxchg_user_asm()
Date: Tue, 7 Jun 2022 17:16:52 +0200	[thread overview]
Message-ID: <2a34e60a-6ac3-0f83-51d5-80a4c6403504@redhat.com> (raw)
In-Reply-To: <485c0c0b-a3a7-0b7c-5264-7d00c01de032@suse.com>

On 6/7/22 17:00, Jan Beulich wrote:
> As noted (and fixed) a couple of times in the past, "=@cc<cond>" outputs
> and clobbering of "cc" don't work well together. The compiler appears to
> mean to reject such, but doesn't - in its upstream form - quite manage
> to yet for "cc". Furthermore two similar macros don't clobber "cc", and
> clobbering "cc" is pointless in asm()-s for x86 anyway - the compiler
> always assumes status flags to be clobbered there.
> 
> Fixes: 989b5db215a2 ("x86/uaccess: Implement macros for CMPXCHG on user addresses")
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> The change I continue to carry locally actually allows specifying that
> "cc" is _not_ clobbered; it only happens to improve detection of bad
> situations like the one here.
> 
> --- a/arch/x86/include/asm/uaccess.h
> +++ b/arch/x86/include/asm/uaccess.h
> @@ -439,7 +439,7 @@ do {									\
>   		       [ptr] "+m" (*_ptr),				\
>   		       [old] "+a" (__old)				\
>   		     : [new] ltype (__new)				\
> -		     : "memory", "cc");					\
> +		     : "memory");					\
>   	if (unlikely(__err))						\
>   		goto label;						\
>   	if (unlikely(!success))						\
> 

Queued, thanks.

Paolo


      reply	other threads:[~2022-06-07 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 15:00 Jan Beulich
2022-06-07 15:16 ` Paolo Bonzini [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=2a34e60a-6ac3-0f83-51d5-80a4c6403504@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jbeulich@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=seanjc@google.com \
    --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

all inboxes | Powered by JetHome®