public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Li Bin <huawei.libin@huawei.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org, Wang Nan <wangnan0@huawei.com>,
	zhangmengting@huawei.com
Subject: Re: [PATCH] perf probe: Fix kprobe blacklist checking condition
Date: Tue, 29 Aug 2017 11:51:12 -0300	[thread overview]
Message-ID: <20170829145112.GB4831@kernel.org> (raw)
In-Reply-To: <1504011443-7269-1-git-send-email-huawei.libin@huawei.com>

Em Tue, Aug 29, 2017 at 08:57:23PM +0800, Li Bin escreveu:
> The commit 9aaf5a5("perf probe: Check kprobes blacklist
> when adding new events"), perf probe supports checking
> the blacklist of the fuctions which can not be probed.
> But the checking condition is wrong, that the end_addr
> of the symbol which is the start_addr of the next symbol
> can't be included.

Applied, with the following committer notes added:

    Committer notes:
    
    IOW make it match its kernel counterpart in kernel/kprobes.c:
    
      bool within_kprobe_blacklist(unsigned long addr)
    
    Each entry have as its end address not its end address, but the first
    address _outside_ that symbol, which for related functions, is the first
    address of the next symbol, like these from kernel/trace/trace_probe.c:
    
    0xffffffffbd198df0-0xffffffffbd198e40   print_type_u8
    0xffffffffbd198e40-0xffffffffbd198e90   print_type_u16
    0xffffffffbd198e90-0xffffffffbd198ee0   print_type_u32
    0xffffffffbd198ee0-0xffffffffbd198f30   print_type_u64
    0xffffffffbd198f30-0xffffffffbd198f80   print_type_s8
    0xffffffffbd198f80-0xffffffffbd198fd0   print_type_s16
    0xffffffffbd198fd0-0xffffffffbd199020   print_type_s32
    0xffffffffbd199020-0xffffffffbd199070   print_type_s64
    0xffffffffbd199070-0xffffffffbd1990c0   print_type_x8
    0xffffffffbd1990c0-0xffffffffbd199110   print_type_x16
    0xffffffffbd199110-0xffffffffbd199160   print_type_x32
    0xffffffffbd199160-0xffffffffbd1991b0   print_type_x64
    
    But not always:
    
    0xffffffffbd1997b0-0xffffffffbd1997c0   fetch_kernel_stack_address (kernel/trace/trace_probe.c)
    0xffffffffbd1c57f0-0xffffffffbd1c58b0   __context_tracking_enter   (kernel/context_tracking.c)
    
    Fixes: 9aaf5a5f479b ("perf probe: Check kprobes blacklist when adding new events")

  reply	other threads:[~2017-08-29 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 12:57 [PATCH] perf probe: Fix kprobe blacklist checking condition Li Bin
2017-08-29 14:51 ` Arnaldo Carvalho de Melo [this message]
2017-08-29 21:25 ` [tip:perf/core] " tip-bot for Li Bin
2017-08-30 12:28 ` [PATCH] " Masami Hiramatsu

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=20170829145112.GB4831@kernel.org \
    --to=acme@kernel.org \
    --cc=huawei.libin@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=wangnan0@huawei.com \
    --cc=zhangmengting@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox