public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Ingo Molnar <mingo@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	"Naveen N . Rao" <naveen.n.rao@linux.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] kprobes: Prohibit probing on BUG() and WARN() address
Date: Tue, 3 Sep 2019 18:31:40 +0900	[thread overview]
Message-ID: <20190903183140.9727fd5b4cc5c90cdd018096@kernel.org> (raw)
In-Reply-To: <201909022327.IrP9O0nh%lkp@intel.com>

Oops, for sparc64 and ppc64, we have to check the CONFIG_GENERIC_BUG...

On Mon, 2 Sep 2019 23:48:41 +0800
kbuild test robot <lkp@intel.com> wrote:

> Hi Masami,
> 
> I love your patch! Yet something to improve:
> 
> [auto build test ERROR on linus/master]
> [cannot apply to v5.3-rc6 next-20190902]
> [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-Prohibit-probing-on-BUG-and-WARN-address/20190902-211736
> config: sparc64-allmodconfig (attached as .config)
> compiler: sparc64-linux-gcc (GCC) 7.4.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # save the attached .config to linux build tree
>         GCC_VERSION=7.4.0 make.cross ARCH=sparc64 
> 
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    kernel/kprobes.c: In function 'check_kprobe_address_safe':
> >> kernel/kprobes.c:1518:6: error: implicit declaration of function 'find_bug'; did you mean 'find_vma'? [-Werror=implicit-function-declaration]
>          find_bug(p->addr)) {
>          ^~~~~~~~
>          find_vma
>    cc1: some warnings being treated as errors
> 
> vim +1518 kernel/kprobes.c
> 
>   1502	
>   1503	static int check_kprobe_address_safe(struct kprobe *p,
>   1504					     struct module **probed_mod)
>   1505	{
>   1506		int ret;
>   1507	
>   1508		ret = arch_check_ftrace_location(p);
>   1509		if (ret)
>   1510			return ret;
>   1511		jump_label_lock();
>   1512		preempt_disable();
>   1513	
>   1514		/* Ensure it is not in reserved area nor out of text */
>   1515		if (!kernel_text_address((unsigned long) p->addr) ||
>   1516		    within_kprobe_blacklist((unsigned long) p->addr) ||
>   1517		    jump_label_text_reserved(p->addr, p->addr) ||
> > 1518		    find_bug(p->addr)) {
>   1519			ret = -EINVAL;
>   1520			goto out;
>   1521		}
>   1522	
>   1523		/* Check if are we probing a module */
>   1524		*probed_mod = __module_text_address((unsigned long) p->addr);
>   1525		if (*probed_mod) {
>   1526			/*
>   1527			 * We must hold a refcount of the probed module while updating
>   1528			 * its code to prohibit unexpected unloading.
>   1529			 */
>   1530			if (unlikely(!try_module_get(*probed_mod))) {
>   1531				ret = -ENOENT;
>   1532				goto out;
>   1533			}
>   1534	
>   1535			/*
>   1536			 * If the module freed .init.text, we couldn't insert
>   1537			 * kprobes in there.
>   1538			 */
>   1539			if (within_module_init((unsigned long)p->addr, *probed_mod) &&
>   1540			    (*probed_mod)->state != MODULE_STATE_COMING) {
>   1541				module_put(*probed_mod);
>   1542				*probed_mod = NULL;
>   1543				ret = -ENOENT;
>   1544			}
>   1545		}
>   1546	out:
>   1547		preempt_enable();
>   1548		jump_label_unlock();
>   1549	
>   1550		return ret;
>   1551	}
>   1552	
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation


-- 
Masami Hiramatsu <mhiramat@kernel.org>

      reply	other threads:[~2019-09-03  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 11:06 [PATCH -tip] kprobes: Prohibit probing on BUG() and WARN() address Masami Hiramatsu
2019-09-02 14:45 ` kbuild test robot
2019-09-02 15:48 ` kbuild test robot
2019-09-03  9:31   ` Masami Hiramatsu [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=20190903183140.9727fd5b4cc5c90cdd018096@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@kernel.org \
    --cc=naveen.n.rao@linux.ibm.com \
    --cc=rostedt@goodmis.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