public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Bang Li <libang.linuxer@gmail.com>
Cc: naveen.n.rao@linux.ibm.com, anil.s.keshavamurthy@intel.com,
	davem@davemloft.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kprobes: Allow both @symbol_name and @addr to exist
Date: Sun, 13 Mar 2022 17:36:46 +0900	[thread overview]
Message-ID: <20220313173646.e3d797f9ee3105239179fb5d@kernel.org> (raw)
In-Reply-To: <20220313032125.124094-1-libang.linuxer@gmail.com>

On Sun, 13 Mar 2022 11:21:25 +0800
Bang Li <libang.linuxer@gmail.com> wrote:

> If the address found by the @symbol_name is equal to the @addr, this case
> should be considered a valid parameter combinations.

Could you tell me the reason why this is needed and use case?
I explictly made this case as an error, because I couldn't find
any good reason to support this case.

Thank you,

> 
> Example:
> 
> static struct kprobe kp = {
>     .symbol_name    = "kernel_clone",
>     .addr           = (kprobe_opcode_t*)kernel_clone,
> };
> 
> Signed-off-by: Bang Li <libang.linuxer@gmail.com>
> ---
>  kernel/kprobes.c | 15 ++++++++++-----
>  1 file changed, 10 insertions(+), 5 deletions(-)
> 
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index 94cab8c9ce56..70d4ed9e7dc7 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -1497,13 +1497,19 @@ bool within_kprobe_blacklist(unsigned long addr)
>  static kprobe_opcode_t *_kprobe_addr(kprobe_opcode_t *addr,
>  			const char *symbol_name, unsigned int offset)
>  {
> -	if ((symbol_name && addr) || (!symbol_name && !addr))
> +	kprobe_opcode_t *symbol_addr;
> +
> +	if (!symbol_name && !addr)
>  		goto invalid;
>  
>  	if (symbol_name) {
> -		addr = kprobe_lookup_name(symbol_name, offset);
> -		if (!addr)
> +		symbol_addr = kprobe_lookup_name(symbol_name, offset);
> +		if (!symbol_addr)
>  			return ERR_PTR(-ENOENT);
> +
> +		if (addr && symbol_addr != addr)
> +			goto invalid;
> +		addr = symbol_addr;
>  	}
>  
>  	addr = (kprobe_opcode_t *)(((char *)addr) + offset);
> @@ -2062,8 +2068,7 @@ bool __weak arch_kprobe_on_func_entry(unsigned long offset)
>   * function entry address or not.
>   * This returns 0 if it is the function entry, or -EINVAL if it is not.
>   * And also it returns -ENOENT if it fails the symbol or address lookup.
> - * Caller must pass @addr or @sym (either one must be NULL), or this
> - * returns -EINVAL.
> + * Caller must pass @addr or @sym, or this returns -EINVAL.
>   */
>  int kprobe_on_func_entry(kprobe_opcode_t *addr, const char *sym, unsigned long offset)
>  {
> -- 
> 2.25.1
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2022-03-13  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13  3:21 [PATCH] kprobes: Allow both @symbol_name and @addr to exist Bang Li
2022-03-13  8:36 ` Masami Hiramatsu [this message]
2022-03-15 13:56   ` 李棒

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=20220313173646.e3d797f9ee3105239179fb5d@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=libang.linuxer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveen.n.rao@linux.ibm.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