From: Andrey Ignatov <rdna@fb.com>
To: Takshak Chahande <ctakshak@fb.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"ast@kernel.org" <ast@kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
Kernel Team <Kernel-team@fb.com>, Hechao Li <hechaol@fb.com>,
"jakub.kicinski@netronome.com" <jakub.kicinski@netronome.com>
Subject: Re: [Potential Spoof] [PATCH bpf v2] libbpf : make libbpf_num_possible_cpus function thread safe
Date: Wed, 31 Jul 2019 22:17:35 +0000 [thread overview]
Message-ID: <20190731221733.GB21873@rdna-mbp> (raw)
In-Reply-To: <20190731221055.1478201-1-ctakshak@fb.com>
Takshak Chahande <ctakshak@fb.com> [Wed, 2019-07-31 15:11 -0700]:
> Having static variable `cpus` in libbpf_num_possible_cpus function
> without guarding it with mutex makes this function thread-unsafe.
>
> If multiple threads accessing this function, in the current form; it
> leads to incrementing the static variable value `cpus` in the multiple
> of total available CPUs.
>
> Used local stack variable to calculate the number of possible CPUs and
> then updated the static variable using WRITE_ONCE().
>
> Changes since v1:
> * added stack variable to calculate cpus
> * serialized static variable update using WRITE_ONCE()
> * fixed Fixes tag
This "Changes" section should be after "---" line not to be included in
the final commit message.
Not sure if resubmit is needed because of it, but other than this looks
good to me.
Acked-by: Andrey Ignatov <rdna@fb.com>
> Fixes: 6446b3155521 ("bpf: add a new API libbpf_num_possible_cpus()")
> Signed-off-by: Takshak Chahande <ctakshak@fb.com>
> ---
> tools/lib/bpf/libbpf.c | 18 +++++++++++-------
> 1 file changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> index 6718d0b90130..2e84fa5b8479 100644
> --- a/tools/lib/bpf/libbpf.c
> +++ b/tools/lib/bpf/libbpf.c
> @@ -4995,13 +4995,15 @@ int libbpf_num_possible_cpus(void)
> static const char *fcpu = "/sys/devices/system/cpu/possible";
> int len = 0, n = 0, il = 0, ir = 0;
> unsigned int start = 0, end = 0;
> + int tmp_cpus = 0;
> static int cpus;
> char buf[128];
> int error = 0;
> int fd = -1;
>
> - if (cpus > 0)
> - return cpus;
> + tmp_cpus = READ_ONCE(cpus);
> + if (tmp_cpus > 0)
> + return tmp_cpus;
>
> fd = open(fcpu, O_RDONLY);
> if (fd < 0) {
> @@ -5024,7 +5026,7 @@ int libbpf_num_possible_cpus(void)
> }
> buf[len] = '\0';
>
> - for (ir = 0, cpus = 0; ir <= len; ir++) {
> + for (ir = 0, tmp_cpus = 0; ir <= len; ir++) {
> /* Each sub string separated by ',' has format \d+-\d+ or \d+ */
> if (buf[ir] == ',' || buf[ir] == '\0') {
> buf[ir] = '\0';
> @@ -5036,13 +5038,15 @@ int libbpf_num_possible_cpus(void)
> } else if (n == 1) {
> end = start;
> }
> - cpus += end - start + 1;
> + tmp_cpus += end - start + 1;
> il = ir + 1;
> }
> }
> - if (cpus <= 0) {
> - pr_warning("Invalid #CPUs %d from %s\n", cpus, fcpu);
> + if (tmp_cpus <= 0) {
> + pr_warning("Invalid #CPUs %d from %s\n", tmp_cpus, fcpu);
> return -EINVAL;
> }
> - return cpus;
> +
> + WRITE_ONCE(cpus, tmp_cpus);
> + return tmp_cpus;
> }
> --
> 2.17.1
>
--
Andrey Ignatov
next prev parent reply other threads:[~2019-07-31 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 22:10 [PATCH bpf v2] libbpf : make libbpf_num_possible_cpus function thread safe Takshak Chahande
2019-07-31 22:17 ` Andrey Ignatov [this message]
2019-07-31 22:31 ` Jakub Kicinski
2019-08-01 3:40 ` Alexei Starovoitov
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=20190731221733.GB21873@rdna-mbp \
--to=rdna@fb.com \
--cc=Kernel-team@fb.com \
--cc=ast@kernel.org \
--cc=ctakshak@fb.com \
--cc=daniel@iogearbox.net \
--cc=hechaol@fb.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.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