From: Ingo Molnar <mingo@kernel.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
live-patching@vger.kernel.org, Michal Marek <mmarek@suse.cz>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>, Pedro Alves <palves@redhat.com>,
Namhyung Kim <namhyung@gmail.com>,
Bernd Petrovitsch <bernd@petrovitsch.priv.at>,
Chris J Arges <chris.j.arges@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Slaby <jslaby@suse.cz>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
David Vrabel <david.vrabel@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v17 6/9] x86/xen: Add xen_cpuid() to objtool whitelist
Date: Thu, 25 Feb 2016 08:54:04 +0100 [thread overview]
Message-ID: <20160225075404.GB2354@gmail.com> (raw)
In-Reply-To: <6998e9cee71397e08f69712c6ec7f8f5a2745cda.1456331595.git.jpoimboe@redhat.com>
* Josh Poimboeuf <jpoimboe@redhat.com> wrote:
> 'objtool check' reports the following false positive warning:
>
> objtool: arch/x86/xen/enlighten.o: xen_cpuid()+0x41: can't find jump dest instruction at .text+0x108
>
> The warning is due to xen_cpuid()'s use of XEN_EMULATE_PREFIX to insert
> some fake instructions which objtool doesn't know how to decode.
>
> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
> Cc: David Vrabel <david.vrabel@citrix.com>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> ---
> arch/x86/xen/enlighten.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
> index d09e4c9..b7f5909 100644
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -32,6 +32,7 @@
> #include <linux/gfp.h>
> #include <linux/memblock.h>
> #include <linux/edd.h>
> +#include <linux/objtool.h>
>
> #ifdef CONFIG_KEXEC_CORE
> #include <linux/kexec.h>
> @@ -351,8 +352,8 @@ static void xen_cpuid(unsigned int *ax, unsigned int *bx,
> *cx &= maskecx;
> *cx |= setecx;
> *dx &= maskedx;
> -
> }
> +STACK_FRAME_NON_STANDARD(xen_cpuid); /* XEN_EMULATE_PREFIX */
Could you please change the title and changelog of all such annotation patches to
say something like:
x86/xen: Mark xen_cpuid() stack frame as non-standard
?
It's not an objtool whitelist anymore, but a more generic annotation that objtool
uses.
Thanks,
Ingo
next prev parent reply other threads:[~2016-02-25 7:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 16:36 [PATCH v17 0/9] Compile-time stack metadata validation Josh Poimboeuf
2016-02-24 16:36 ` [PATCH v17 1/9] x86/objtool: " Josh Poimboeuf
2016-02-24 16:36 ` [PATCH v17 2/9] x86/objtool: Add CONFIG_STACK_VALIDATION option Josh Poimboeuf
2016-02-24 16:36 ` [PATCH v17 3/9] x86/objtool: Enable objtool on x86_64 Josh Poimboeuf
2016-02-24 16:36 ` [PATCH v17 4/9] x86/objtool: Add STACK_FRAME_NON_STANDARD macro Josh Poimboeuf
2016-02-25 7:51 ` Ingo Molnar
2016-02-25 20:26 ` Josh Poimboeuf
2016-02-24 16:36 ` [PATCH v17 5/9] x86/objtool: Add directory and file whitelists Josh Poimboeuf
2016-02-24 16:36 ` [PATCH v17 6/9] x86/xen: Add xen_cpuid() to objtool whitelist Josh Poimboeuf
2016-02-25 7:54 ` Ingo Molnar [this message]
2016-02-24 16:36 ` [PATCH v17 7/9] bpf: Add __bpf_prog_run() " Josh Poimboeuf
2016-02-24 16:36 ` [PATCH v17 8/9] sched: Add __schedule() " Josh Poimboeuf
2016-02-24 16:36 ` [PATCH v17 9/9] x86/kprobes: Add kretprobe_trampoline() " Josh Poimboeuf
2016-02-25 8:02 ` [PATCH v17 0/9] Compile-time stack metadata validation Ingo Molnar
2016-02-25 17:04 ` Josh Poimboeuf
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=20160225075404.GB2354@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=bernd@petrovitsch.priv.at \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=chris.j.arges@canonical.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=jslaby@suse.cz \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=namhyung@gmail.com \
--cc=palves@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).