All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Jackie Liu <liu.yun@linux.dev>
Cc: Jiri Olsa <olsajiri@gmail.com>,
	andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
	yhs@fb.com, bpf@vger.kernel.org, liuyun01@kylinos.cn,
	lkp@intel.com
Subject: Re: [PATCH v3 1/2] libbpf: kprobe.multi: cross filter using available_filter_functions and kallsyms
Date: Tue, 4 Jul 2023 16:07:43 +0200	[thread overview]
Message-ID: <ZKQnr0VZri1pWyrO@krava> (raw)
In-Reply-To: <437ed462-8950-755d-388f-e82c57bb8c44@linux.dev>

On Tue, Jul 04, 2023 at 09:33:15AM +0800, Jackie Liu wrote:

SNIP

> > 
> > should you check if you found anything (infos.cnt != 0) and return early
> > if there's nothing found
> > 
> > > +
> > > +	/* sort available functions */
> > > +	qsort(infos.syms, infos.cnt, sizeof(void *), qsort_compare_function);
> > > +
> > > +	f = fopen("/proc/kallsyms", "r");
> > 
> > why not use libbpf_kallsyms_parse for kallsyms parsing? the call below
> > would be in its callback
> 
> This place cannot directly use libbpf_kallsyms_parse, because we need
> info.syms, this value cannot be passed into the parameters of
> libbpf_kallsyms_parse, 

hum, libbpf_kallsyms_parse takes 'void *ctx', so you can pass anything
you want right? 

thanks,
jirka

> and we cannot turn info.syms into a global
> variable, which is unnecessary. The easiest way is to reimplement a A
> copy of libbpf_kallsyms_parse.
> 
> Modifications to other parts will be carried along with the next
> version.
> 
> -- 
> Jackie
> 
> > 
> > > +	if (!f) {
> > > +		err = -errno;
> > > +		pr_warn("failed to open /proc/kallsyms\n");
> > > +		goto free_infos;
> > > +	}
> > > +
> > > +	while (true) {
> > > +		unsigned long long sym_addr;
> > > +
> > > +		ret = fscanf(f, "%llx %*c %499s%*[^\n]\n", &sym_addr, sym_name);
> > > +		if (ret == EOF && feof(f))
> > > +			break;
> > > +
> > > +		if (ret != 2) {
> > > +			pr_warn("failed to read kallsyms entry: %d\n", ret);
> > > +			err = -EINVAL;
> > > +			break;
> > > +		}
> > > +
> > > +		if (!glob_match(sym_name, res->pattern))
> > > +			continue;
> > 
> > hm, we don't need to call glob_match again, we just want to check
> > if the kallsyms symbol is in infos.syms
> > 
> > > +
> > > +		if (!bsearch(&sym_name, infos.syms, infos.cnt, sizeof(void *),
> > > +			     bsearch_compare_function))
> > > +			continue;
> > > +
> > > +		err = libbpf_ensure_mem((void **)&res->addrs, &res->cap,
> > > +					sizeof(unsigned long), res->cnt + 1);
> > > +		if (err)
> > > +			break;
> > > +
> > > +		res->addrs[res->cnt++] = (unsigned long) sym_addr;
> > > +	}
> > 
> > res->cnt is check outside for 0, so we should be find here
> > 
> > jirka
> > 
> > > +
> > > +cleanup:
> > > +	fclose(f);
> > > +free_infos:
> > > +	for (i = 0; i < infos.cnt; i++)
> > > +		free((char *)infos.syms[i]);
> > > +	free(infos.syms);
> > > +
> > > +	return err;
> > >   }
> > >   struct bpf_link *
> > > @@ -10594,7 +10690,7 @@ bpf_program__attach_kprobe_multi_opts(const struct bpf_program *prog,
> > >   		return libbpf_err_ptr(-EINVAL);
> > >   	if (pattern) {
> > > -		err = libbpf_kallsyms_parse(resolve_kprobe_multi_cb, &res);
> > > +		err = libbpf_available_kallsyms_parse(&res);
> > >   		if (err)
> > >   			goto error;
> > >   		if (!res.cnt) {
> > > -- 
> > > 2.25.1
> > > 

  reply	other threads:[~2023-07-04 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  1:36 [PATCH v3 1/2] libbpf: kprobe.multi: cross filter using available_filter_functions and kallsyms Jackie Liu
2023-07-03  1:36 ` [PATCH v3 2/2] libbpf: kprobe.multi: Filter with available_filter_functions_addrs Jackie Liu
2023-07-03 12:59 ` [PATCH v3 1/2] libbpf: kprobe.multi: cross filter using available_filter_functions and kallsyms Jiri Olsa
2023-07-04  1:33   ` Jackie Liu
2023-07-04 14:07     ` Jiri Olsa [this message]
2023-07-04 14:20       ` Jiri Olsa
2023-07-03 19:38 ` John Fastabend
2023-07-04  1:30   ` Jackie Liu

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=ZKQnr0VZri1pWyrO@krava \
    --to=olsajiri@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=liu.yun@linux.dev \
    --cc=liuyun01@kylinos.cn \
    --cc=lkp@intel.com \
    --cc=martin.lau@linux.dev \
    --cc=song@kernel.org \
    --cc=yhs@fb.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.