From: Daniel Micay <danielmicay@gmail.com>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
Mark Rutland <mark.rutland@arm.com>,
Daniel Axtens <dja@axtens.net>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Chris Metcalf <cmetcalf@ezchip.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp-robot] [include/linux/string.h] 6974f0c455: kernel_BUG_at_lib/string.c
Date: Thu, 20 Jul 2017 00:02:23 -0400 [thread overview]
Message-ID: <1500523343.2055.2.camel@gmail.com> (raw)
In-Reply-To: <20170720014238.GH27396@yexl-desktop>
> [ 8.134886] arch_prepare_optimized_kprobe+0xd5/0x171
> [ 8.134886] arch_prepare_optimized_kprobe+0xd5/0x171
Probably this:
/* Copy arch-dep-instance from template */
memcpy(buf, &optprobe_template_entry, TMPL_END_IDX);
Not a real bug, just technically undefined because these are u32:
typedef u32 kprobe_opcode_t;
extern __visible kprobe_opcode_t optprobe_template_entry;
extern __visible kprobe_opcode_t optprobe_template_val;
extern __visible kprobe_opcode_t optprobe_template_call;
extern __visible kprobe_opcode_t optprobe_template_end;
extern __visible kprobe_opcode_t optprobe_template_sub_sp;
extern __visible kprobe_opcode_t optprobe_template_add_sp;
extern __visible kprobe_opcode_t optprobe_template_restore_begin;
extern __visible kprobe_opcode_t optprobe_template_restore_orig_insn;
extern __visible kprobe_opcode_t optprobe_template_restore_end;
Could be switched to unknown size arrays like optprobe_template_entry[]
but it might be best to just mark the kprobe code with #define
__NO_FORTIFY.
next prev parent reply other threads:[~2017-07-20 4:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 1:42 [lkp-robot] [include/linux/string.h] 6974f0c455: kernel_BUG_at_lib/string.c kernel test robot
2017-07-20 1:42 ` kernel test robot
2017-07-20 4:02 ` Daniel Micay [this message]
2017-07-20 4:04 ` Linus Torvalds
2017-07-20 4:04 ` Linus Torvalds
2017-07-20 4:41 ` Daniel Micay
2017-07-20 13:46 ` Masami Hiramatsu
2017-07-20 13:46 ` Masami Hiramatsu
2017-07-20 14:50 ` Ye Xiaolong
2017-07-21 1:30 ` Fengguang Wu
2017-07-21 1:52 ` Ye Xiaolong
2017-07-21 1:56 ` Fengguang Wu
2017-07-21 2:03 ` Ye Xiaolong
2017-07-20 15:51 ` Masami Hiramatsu
2017-07-20 15:51 ` Masami Hiramatsu
2017-07-20 18:41 ` Linus Torvalds
2017-07-20 18:41 ` Linus Torvalds
2017-07-20 22:20 ` Masami Hiramatsu
2017-07-20 22:20 ` Masami Hiramatsu
2017-07-21 3:29 ` Masami Hiramatsu
2017-07-21 3:29 ` Masami Hiramatsu
2017-07-21 3:29 ` Masami Hiramatsu
2017-07-21 1:59 ` Ye Xiaolong
2017-07-21 1:59 ` Ye Xiaolong
2017-07-21 5:48 ` Kees Cook
2017-07-21 5:48 ` Kees Cook
2017-07-21 9:15 ` Andy Shevchenko
2017-07-21 9:15 ` Andy Shevchenko
2017-07-21 10:03 ` Petr Mladek
2017-07-21 10:03 ` Petr Mladek
2017-07-25 23:35 ` Kees Cook
2017-07-25 23:35 ` Kees Cook
2017-07-26 0:11 ` Linus Torvalds
2017-07-26 0:11 ` Linus Torvalds
2017-07-26 0:38 ` Kees Cook
2017-07-26 0:38 ` Kees Cook
2017-07-26 2:37 ` Daniel Micay
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=1500523343.2055.2.camel@gmail.com \
--to=danielmicay@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=cmetcalf@ezchip.com \
--cc=dja@axtens.net \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=lkp@01.org \
--cc=mark.rutland@arm.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=xiaolong.ye@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.