From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: andrii.nakryiko@gmail.com, alexei.starovoitov@gmail.com,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, paulmck@kernel.org,
peterz@infradead.org, tglx@linutronix.de,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4] bpf: Remove in_atomic() from bpf_link_put().
Date: Fri, 16 Jun 2023 16:30:20 +0000 [thread overview]
Message-ID: <168693302002.15027.13621981423578755110.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230614083430.oENawF8f@linutronix.de>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 14 Jun 2023 10:34:30 +0200 you wrote:
> bpf_free_inode() is invoked as a RCU callback. Usually RCU callbacks are
> invoked within softirq context. By setting rcutree.use_softirq=0 boot
> option the RCU callbacks will be invoked in a per-CPU kthread with
> bottom halves disabled which implies a RCU read section.
>
> On PREEMPT_RT the context remains fully preemptible. The RCU read
> section however does not allow schedule() invocation. The latter happens
> in mutex_lock() performed by bpf_trampoline_unlink_prog() originated
> from bpf_link_put().
>
> [...]
Here is the summary with links:
- [v4] bpf: Remove in_atomic() from bpf_link_put().
https://git.kernel.org/bpf/bpf-next/c/ab5d47bd41b1
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:[~2023-06-16 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230509132433.2FSY_6t7@linutronix.de>
[not found] ` <CAEf4BzZcPKsRJDQfdVk9D1Nt6kgT4STpEUrsQ=UD3BDZnNp8eQ@mail.gmail.com>
[not found] ` <CAADnVQLzZyZ+cPqBFfrqa8wtQ8ZhWvTSN6oD9z4Y2gtrfs8Vdg@mail.gmail.com>
[not found] ` <CAEf4BzY-MRYnzGiZmW7AVJYgYdHW1_jOphbipRrHRTtdfq3_wQ@mail.gmail.com>
[not found] ` <20230525141813.TFZLWM4M@linutronix.de>
[not found] ` <CAEf4Bzaipoo6X_2Fh5WTV-m0yjP0pvhqi7-FPFtGOrSzNpdGJQ@mail.gmail.com>
[not found] ` <20230526112356.fOlWmeOF@linutronix.de>
[not found] ` <CAEf4Bzawgrn2DhR9uvXwFFiLR9g+j4RYC6cr3n+eRD_RoKBAJA@mail.gmail.com>
2023-06-05 16:37 ` [PATCH v3] bpf: Remove in_atomic() from bpf_link_put() Sebastian Andrzej Siewior
2023-06-05 22:47 ` Andrii Nakryiko
2023-06-09 14:19 ` Sebastian Andrzej Siewior
2023-06-14 8:34 ` [PATCH v4] " Sebastian Andrzej Siewior
2023-06-15 16:43 ` Paul E. McKenney
2023-06-15 19:13 ` Sebastian Andrzej Siewior
2023-06-15 19:32 ` Paul E. McKenney
2023-06-16 16:30 ` 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=168693302002.15027.13621981423578755110.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).