From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com,
syzbot+7ee5c2c09c284495371f@syzkaller.appspotmail.com
Subject: Re: [PATCH bpf] bpf: fix rcu warning in bpf_prog_run_pin_on_cpu()
Date: Thu, 29 Jul 2021 22:10:05 +0000 [thread overview]
Message-ID: <162759660566.3171.3401866075961092975.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210728172307.1030271-1-yhs@fb.com>
Hello:
This patch was applied to bpf/bpf.git (refs/heads/master):
On Wed, 28 Jul 2021 10:23:07 -0700 you wrote:
> syzbot reported a RCU warning like below:
> WARNING: suspicious RCU usage
> ...
> Call Trace:
> __dump_stack lib/dump_stack.c:88 [inline]
> dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:105
> task_css_set include/linux/cgroup.h:481 [inline]
> task_dfl_cgroup include/linux/cgroup.h:550 [inline]
> ____bpf_get_current_cgroup_id kernel/bpf/helpers.c:356 [inline]
> bpf_get_current_cgroup_id+0x1ce/0x210 kernel/bpf/helpers.c:354
> bpf_prog_08c4887f705f20b8+0x10/0x824
> bpf_dispatcher_nop_func include/linux/bpf.h:687 [inline]
> bpf_prog_run_pin_on_cpu include/linux/filter.h:624 [inline]
> bpf_prog_test_run_syscall+0x2cf/0x5f0 net/bpf/test_run.c:954
> bpf_prog_test_run kernel/bpf/syscall.c:3207 [inline]
> __sys_bpf+0x1993/0x53b0 kernel/bpf/syscall.c:4487
>
> [...]
Here is the summary with links:
- [bpf] bpf: fix rcu warning in bpf_prog_run_pin_on_cpu()
https://git.kernel.org/bpf/bpf/c/8118b11cb603
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-07-29 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 17:23 [PATCH bpf] bpf: fix rcu warning in bpf_prog_run_pin_on_cpu() Yonghong Song
2021-07-29 22:10 ` patchwork-bot+netdevbpf [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=162759660566.3171.3401866075961092975.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=syzbot+7ee5c2c09c284495371f@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox