From: patchwork-bot+netdevbpf@kernel.org
To: Noorain Eqbal <nooraineqbal@gmail.com>
Cc: andrii.nakryiko@gmail.com, alexei.starovoitov@gmail.com,
andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, david.hunter@linuxfoundation.org,
eddyz87@gmail.com, haoluo@google.com, john.fastabend@gmail.com,
jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel-mentees@lists.linux.dev,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
sdf@fomichev.me, skhan@linuxfoundation.org, song@kernel.org,
syzbot+2617fc732430968b45d2@syzkaller.appspotmail.com,
yonghong.song@linux.dev
Subject: Re: [PATCH v2] bpf: sync pending IRQ work before freeing ring buffer
Date: Tue, 21 Oct 2025 17:10:06 +0000 [thread overview]
Message-ID: <176106660601.1163561.6885193392074712225.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251020180301.103366-1-nooraineqbal@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 20 Oct 2025 23:33:01 +0530 you wrote:
> Fix a race where irq_work can be queued in bpf_ringbuf_commit()
> but the ring buffer is freed before the work executes.
> In the syzbot reproducer, a BPF program attached to sched_switch
> triggers bpf_ringbuf_commit(), queuing an irq_work. If the ring buffer
> is freed before this work executes, the irq_work thread may accesses
> freed memory.
> Calling `irq_work_sync(&rb->work)` ensures that all pending irq_work
> complete before freeing the buffer
>
> [...]
Here is the summary with links:
- [v2] bpf: sync pending IRQ work before freeing ring buffer
https://git.kernel.org/bpf/bpf/c/4e9077638301
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:[~2025-10-21 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 18:11 [PATCH] bpf: sync pending IRQ work before freeing ring buffer neqbal
2025-10-19 1:13 ` Alexei Starovoitov
2025-10-19 22:30 ` Noorain Eqbal
2025-10-20 16:17 ` Andrii Nakryiko
2025-10-20 18:03 ` [PATCH v2] " Noorain Eqbal
2025-10-21 17: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=176106660601.1163561.6885193392074712225.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=david.hunter@linuxfoundation.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=nooraineqbal@gmail.com \
--cc=sdf@fomichev.me \
--cc=skhan@linuxfoundation.org \
--cc=song@kernel.org \
--cc=syzbot+2617fc732430968b45d2@syzkaller.appspotmail.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