From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark D Rustad <mark.d.rustad@intel.com>, gleb@kernel.org
Cc: jeffrey.t.kirsher@intel.com, kvm@vger.kernel.org
Subject: Re: [PATCH V2 3/4] x86/kvm: Resolve shadow warnings in macro expansion
Date: Thu, 31 Jul 2014 13:50:42 +0200 [thread overview]
Message-ID: <53DA2D92.2010301@redhat.com> (raw)
In-Reply-To: <20140730211926.127150.102.stgit@mdrustad-wks.jf.intel.com>
Il 30/07/2014 23:19, Mark D Rustad ha scritto:
> Resolve shadow warnings that appear in W=2 builds. Instead of
> using ret to hold the return pointer, save the length in a new
> variable saved_len and compute the pointer on exit. This also
> resolves a very technical error, in that ret was declared as
> a const char *, when it really was a char * const, which
> theoretically could have allowed the compiler to do something
> wrong.
>
> Signed-off-by: Mark Rustad <mark.d.rustad@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>
> ---
> Changes in V2:
> - Instead of renaming all inner variables, just delete the
> ret variable in favor of the new saved_len variable.
> ---
> arch/x86/kvm/mmutrace.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/mmutrace.h b/arch/x86/kvm/mmutrace.h
> index 9d2e0ffcb190..5aaf35641768 100644
> --- a/arch/x86/kvm/mmutrace.h
> +++ b/arch/x86/kvm/mmutrace.h
> @@ -22,7 +22,7 @@
> __entry->unsync = sp->unsync;
>
> #define KVM_MMU_PAGE_PRINTK() ({ \
> - const char *ret = p->buffer + p->len; \
> + const u32 saved_len = p->len; \
> static const char *access_str[] = { \
> "---", "--x", "w--", "w-x", "-u-", "-ux", "wu-", "wux" \
> }; \
> @@ -41,7 +41,7 @@
> role.nxe ? "" : "!", \
> __entry->root_count, \
> __entry->unsync ? "unsync" : "sync", 0); \
> - ret; \
> + p->buffer + saved_len; \
> })
>
> #define kvm_mmu_trace_pferr_flags \
>
Applying this patch, thanks.
Paolo
next prev parent reply other threads:[~2014-07-31 11:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 13:27 [PATCH 1/4] x86/kvm: Resolve some missing-initializers warnings Jeff Kirsher
2014-07-25 13:27 ` [PATCH 2/4] kvm: Resolve missing-field-initializers warnings Jeff Kirsher
2014-07-25 14:06 ` Paolo Bonzini
2014-07-25 13:27 ` [PATCH 3/4] x86/kvm: Resolve shadow warnings in macro expansion Jeff Kirsher
2014-07-25 14:06 ` Paolo Bonzini
2014-07-25 17:18 ` Rustad, Mark D
2014-07-26 7:34 ` Paolo Bonzini
2014-07-30 21:19 ` [PATCH V2 " Mark D Rustad
2014-07-31 11:50 ` Paolo Bonzini [this message]
2014-07-31 16:59 ` [PATCH V3 " Mark D Rustad
2014-07-25 13:27 ` [PATCH 4/4] x86/kvm: Resolve shadow warning from min macro Jeff Kirsher
2014-07-25 14:06 ` Paolo Bonzini
2014-07-25 14:04 ` [PATCH 1/4] x86/kvm: Resolve some missing-initializers warnings Paolo Bonzini
2014-07-30 21:18 ` [PATCH V2 " Mark D Rustad
2014-07-31 11:50 ` Paolo Bonzini
2014-07-31 16:35 ` Rustad, Mark D
2014-07-31 16:50 ` Paolo Bonzini
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=53DA2D92.2010301@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mark.d.rustad@intel.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.