All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	'Keir Fraser' <keir.fraser@eu.citrix.com>,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: paging_domctl() missing break statements?
Date: Wed, 23 Jun 2010 14:27:31 +0200	[thread overview]
Message-ID: <4C21FDB3.8000402@redhat.com> (raw)
In-Reply-To: <20100217095806.GK368@whitby.uk.xensource.com>

On 02/17/2010 10:58 AM, Tim Deegan wrote:
> At 09:48 +0000 on 17 Feb (1266400095), Jan Beulich wrote:
>> The main switch statement in that function looks suspicious, and with no
>> explicit comment saying that fall-through is intended it would seem like
>> one or two break statements are actually missing. Comments?
>
> Yep, looks like that was just working by blind luck.
>
> Tim.
>
> diff -r 560277d2fd20 xen/arch/x86/mm/paging.c
> --- a/xen/arch/x86/mm/paging.c	Mon Feb 15 08:19:07 2010 +0000
> +++ b/xen/arch/x86/mm/paging.c	Wed Feb 17 09:56:43 2010 +0000
> @@ -717,11 +717,13 @@
>                   hap_logdirty_init(d);
>               return paging_log_dirty_enable(d);
>           }
> +        break;
>
>       case XEN_DOMCTL_SHADOW_OP_OFF:
>           if ( paging_mode_log_dirty(d) )
>               if ( (rc = paging_log_dirty_disable(d)) != 0 )
>                   return rc;
> +        break;
>
>       case XEN_DOMCTL_SHADOW_OP_CLEAN:
>       case XEN_DOMCTL_SHADOW_OP_PEEK:

This was never applied.

Paolo

  parent reply	other threads:[~2010-06-23 12:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  9:48 paging_domctl() missing break statements? Jan Beulich
2010-02-17  9:58 ` Tim Deegan
2010-02-17 15:20   ` Dan Magenheimer
2010-02-17 17:36     ` Tim Deegan
2010-06-23 12:27   ` Paolo Bonzini [this message]
2010-06-23 12:51     ` Keir Fraser
2010-06-23 12:51     ` Tim Deegan
2010-06-23 16:27       ` Patrick Colp
2010-06-24  7:10         ` Jan Beulich
2010-06-25 13:50         ` [PATCH] " Tim Deegan

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=4C21FDB3.8000402@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=JBeulich@novell.com \
    --cc=Tim.Deegan@citrix.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.