From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Ren Wei" <weir@nebusec.ai>, <bpf@vger.kernel.org>
Cc: <andrii@kernel.org>, <daniel@iogearbox.net>, <eddyz87@gmail.com>,
<memxor@gmail.com>, <martin.lau@linux.dev>, <song@kernel.org>,
<yonghong.song@linux.dev>, <jolsa@kernel.org>,
<emil@etsalapatis.com>, <ihor.solodrai@linux.dev>,
<void@manifault.com>, <vega@nebusec.ai>, <rakukuip@gmail.com>
Subject: Re: [PATCH bpf 1/2] bpf: Reject user ringbuf backlogs larger than total ring size
Date: Mon, 09 Nov 2026 18:28:10 +0000 [thread overview]
Message-ID: <DMQW5CZKKR8Q.2ASEAH53BMYV9@gmail.com> (raw)
In-Reply-To: <ecf1a73cac8881d58b0b5957fb72caaeaa055339.1793951856.git.rakukuip@gmail.com>
On Sun, Nov 08, 2026 at 07:03 PM Ren Wei <weir@nebusec.ai> wrote:
> When bpf_user_ringbuf_drain() drains the ring buffer, cons_pos wraps
> around the physical buffer repeatedly within the oversized unread window,
> replaying stale or already-consumed samples without new writes from user
> space. In the worst case, this leads to excessive CPU consumption and
> watchdog softlockups.
No.
Stop the slop
pw-bot: cr
next prev parent reply other threads:[~2026-11-09 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 3:03 [PATCH bpf 0/2] bpf: Reject user ringbuf backlogs larger than total ring size Ren Wei
2026-11-09 3:03 ` [PATCH bpf 1/2] " Ren Wei
2026-11-09 3:17 ` sashiko-bot
2026-11-09 18:28 ` Alexei Starovoitov [this message]
2026-11-09 3:03 ` [PATCH bpf 2/2] selftests/bpf: Test user ringbuf backlog larger than " Ren Wei
2026-11-09 3:14 ` sashiko-bot
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=DMQW5CZKKR8Q.2ASEAH53BMYV9@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=rakukuip@gmail.com \
--cc=song@kernel.org \
--cc=vega@nebusec.ai \
--cc=void@manifault.com \
--cc=weir@nebusec.ai \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.