mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: kbuild-all@01.org, Ingo Molnar <mingo@kernel.org>,
	Francis Deslauriers <francis.deslauriers@efficios.com>,
	mathieu.desnoyers@efficios.com,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Masami Hiramatsu <mhiramat@kernel.org>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
	"David S . Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip V2] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code
Date: Tue, 25 Jul 2017 23:41:17 +0800	[thread overview]
Message-ID: <201707252331.cTLwrRql%fengguang.wu@intel.com> (raw)
In-Reply-To: <150095034226.4921.9289125363675682881.stgit@devbox>

[-- Attachment #1: Type: text/plain, Size: 3630 bytes --]

Hi Masami,

[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v4.13-rc2 next-20170725]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Masami-Hiramatsu/kprobes-x86-Do-not-jump-optimize-kprobes-on-irq-entry-code/20170725-231634
config: x86_64-randconfig-x018-201730 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   arch/x86//kernel/kprobes/opt.c: In function 'can_optimize':
>> arch/x86//kernel/kprobes/opt.c:259:32: error: '__irqentry_text_start' undeclared (first use in this function)
         ((paddr >= (unsigned long)__irqentry_text_start) &&
                                   ^~~~~~~~~~~~~~~~~~~~~
   arch/x86//kernel/kprobes/opt.c:259:32: note: each undeclared identifier is reported only once for each function it appears in
>> arch/x86//kernel/kprobes/opt.c:260:32: error: '__irqentry_text_end' undeclared (first use in this function)
          (paddr <  (unsigned long)__irqentry_text_end)))
                                   ^~~~~~~~~~~~~~~~~~~

vim +/__irqentry_text_start +259 arch/x86//kernel/kprobes/opt.c

   241	
   242	/* Decode whole function to ensure any instructions don't jump into target */
   243	static int can_optimize(unsigned long paddr)
   244	{
   245		unsigned long addr, size = 0, offset = 0;
   246		struct insn insn;
   247		kprobe_opcode_t buf[MAX_INSN_SIZE];
   248	
   249		/* Lookup symbol including addr */
   250		if (!kallsyms_lookup_size_offset(paddr, &size, &offset))
   251			return 0;
   252	
   253		/*
   254		 * Do not optimize in the entry code due to the unstable
   255		 * stack handling and registers setup.
   256		 */
   257		if (((paddr >= (unsigned long)__entry_text_start) &&
   258		     (paddr <  (unsigned long)__entry_text_end)) ||
 > 259		    ((paddr >= (unsigned long)__irqentry_text_start) &&
 > 260		     (paddr <  (unsigned long)__irqentry_text_end)))
   261			return 0;
   262	
   263		/* Check there is enough space for a relative jump. */
   264		if (size - offset < RELATIVEJUMP_SIZE)
   265			return 0;
   266	
   267		/* Decode instructions */
   268		addr = paddr - offset;
   269		while (addr < paddr - offset + size) { /* Decode until function end */
   270			unsigned long recovered_insn;
   271			if (search_exception_tables(addr))
   272				/*
   273				 * Since some fixup code will jumps into this function,
   274				 * we can't optimize kprobe in this function.
   275				 */
   276				return 0;
   277			recovered_insn = recover_probed_instruction(buf, addr);
   278			if (!recovered_insn)
   279				return 0;
   280			kernel_insn_init(&insn, (void *)recovered_insn, MAX_INSN_SIZE);
   281			insn_get_length(&insn);
   282			/* Another subsystem puts a breakpoint */
   283			if (insn.opcode.bytes[0] == BREAKPOINT_INSTRUCTION)
   284				return 0;
   285			/* Recover address */
   286			insn.kaddr = (void *)addr;
   287			insn.next_byte = (void *)(addr + insn.length);
   288			/* Check any instructions don't jump into target */
   289			if (insn_is_indirect_jump(&insn) ||
   290			    insn_jump_into_range(&insn, paddr + INT3_SIZE,
   291						 RELATIVE_ADDR_SIZE))
   292				return 0;
   293			addr += insn.length;
   294		}
   295	
   296		return 1;
   297	}
   298	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24044 bytes --]

      parent reply	other threads:[~2017-07-25 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25  2:39 Masami Hiramatsu
2017-07-25 10:40 ` Ingo Molnar
2017-07-25 13:45   ` Masami Hiramatsu
2017-07-25 15:41 ` kbuild test robot [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=201707252331.cTLwrRql%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=francis.deslauriers@efficios.com \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®