BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Wander Lairson Costa <wander@redhat.com>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
	yonghong.song@linux.dev, john.fastabend@gmail.com,
	kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
	jolsa@kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, wander.lairson@gmail.com,
	bgrech@redhat.com
Subject: Re: [PATCH] bpf: use raw_spinlock_t in ringbuf
Date: Wed, 25 Sep 2024 10:00:30 +0000	[thread overview]
Message-ID: <172725843003.522662.2025610414872346543.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240920190700.617253-1-wander@redhat.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Fri, 20 Sep 2024 16:06:59 -0300 you wrote:
> From: Wander Lairson Costa <wander.lairson@gmail.com>
> 
> The function __bpf_ringbuf_reserve is invoked from a tracepoint, which
> disables preemption. Using spinlock_t in this context can lead to a
> "sleep in atomic" warning in the RT variant. This issue is illustrated
> in the example below:
> 
> [...]

Here is the summary with links:
  - bpf: use raw_spinlock_t in ringbuf
    https://git.kernel.org/bpf/bpf/c/8b62645b09f8

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-09-25 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20 19:06 [PATCH] bpf: use raw_spinlock_t in ringbuf Wander Lairson Costa
2024-09-24 16:46 ` Daniel Borkmann
2024-09-25 10:00 ` 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=172725843003.522662.2025610414872346543.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bgrech@redhat.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=wander.lairson@gmail.com \
    --cc=wander@redhat.com \
    --cc=yonghong.song@linux.dev \
    /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