All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/mmuext: Unify okay/rc error handling in do_mmuext_op()
Date: Tue, 22 Dec 2015 09:09:33 +0000	[thread overview]
Message-ID: <5679134D.6070404@citrix.com> (raw)
In-Reply-To: <56791E8502000078000C2243@prv-mh.provo.novell.com>

On 22/12/2015 08:57, Jan Beulich wrote:
>>>> On 21.12.15 at 18:16, <andrew.cooper3@citrix.com> wrote:
>> c/s 506db90 "x86/HVM: merge HVM and PVH hypercall tables" introduced a path
>> whereby 'okay' was used uninitialised, with broke compilation on CentOS 7.
> It appeared to be used uninitialized, but wasn't in fact (i.e. the
> outcome - the value rc gets set to - didn't depend on the value
> due to
>
>         if ( unlikely(!okay) && !rc )
>             rc = -EINVAL;
>
> being equivalent to
>
>         if ( !rc && unlikely(!okay) )
>             rc = -EINVAL;
>
> (no side effects for the expressions on either side of the &&).
> I'll re-word accordingly upon committing, to not give the false
> impression of there having been other than a cosmetic problem.

There is a real problem.  Because the compiler is able to prove that
okay is genuinely read uninitialised in one case, the rules concerning
undefined behaviour permit it to do anything it wishes, including
omitting this if statement.

As far as practical problems go however, it is the build breakage which
is relevant, and it breaks because of a -Werror=maybe-uninitialised.

~Andrew

      reply	other threads:[~2015-12-22  9:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 17:16 [PATCH] x86/mmuext: Unify okay/rc error handling in do_mmuext_op() Andrew Cooper
2015-12-21 17:50 ` Boris Ostrovsky
2015-12-22  9:56   ` Andrew Cooper
2015-12-22  8:57 ` Jan Beulich
2015-12-22  9:09   ` Andrew Cooper [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=5679134D.6070404@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.