From: Tamir Duberstein <tamird@kernel.org>
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: sashiko-reviews@lists.linux.dev, bpf@vger.kernel.org
Subject: Re: [PATCH bpf 3/6] libbpf: ringbuf: Handle position counter wrap
Date: Thu, 18 Jun 2026 17:12:01 -0400 [thread overview]
Message-ID: <deddbbbc947400fa0cb3f0a6e164c290@kernel.org> (raw)
In-Reply-To: <DJAXGXLF4NHZ.17HAW2R1YDK7I@etsalapatis.com>
On Tue, Jun 16, 2026 at 09:19:43PM -0400, Emil Tsalapatis wrote:
[...]
> This seems like a fair point, if we're going to modify one let's also
> modify the other. Wrt the "32-bit binaries on 64-bit" Sashiko warnings
> they're a bridge too far, we have to draw the line somewhere.
Yep, my clanker also flagged the 32-bit-on-64-bit problem -- I agree
it doesn't make sense to tackle here. The other two now have their own
patches in v2.
> Can we also add a comment as to why we're using != in both locations?
Done in v2.
next prev parent reply other threads:[~2026-06-18 21:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 1:48 [PATCH bpf 0/6] libbpf: Fix ring buffer consumption Tamir Duberstein
2026-06-14 1:48 ` [PATCH bpf 1/6] libbpf: ringbuf: Honor zero consume bounds Tamir Duberstein
2026-06-17 0:35 ` Emil Tsalapatis
2026-06-14 1:48 ` [PATCH bpf 2/6] libbpf: ringbuf: Prevent NULL callback crash Tamir Duberstein
2026-06-17 0:44 ` Emil Tsalapatis
2026-06-18 20:49 ` Tamir Duberstein
2026-06-14 1:48 ` [PATCH bpf 3/6] libbpf: ringbuf: Handle position counter wrap Tamir Duberstein
2026-06-14 2:05 ` sashiko-bot
2026-06-17 1:19 ` Emil Tsalapatis
2026-06-18 21:12 ` Tamir Duberstein [this message]
2026-06-14 1:48 ` [PATCH bpf 4/6] libbpf: ringbuf: Use compiler atomics Tamir Duberstein
2026-06-14 1:59 ` sashiko-bot
2026-06-17 1:30 ` Emil Tsalapatis
2026-06-14 1:48 ` [PATCH bpf 5/6] libbpf: ringbuf: Prevent missed wakeups Tamir Duberstein
2026-06-14 1:57 ` sashiko-bot
2026-06-18 6:41 ` Emil Tsalapatis
2026-06-18 22:05 ` Tamir Duberstein
2026-06-14 1:48 ` [PATCH bpf 6/6] libbpf: ringbuf: Reject overwrite callback use Tamir Duberstein
2026-06-18 6:52 ` Emil Tsalapatis
2026-06-19 0:26 ` Tamir Duberstein
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=deddbbbc947400fa0cb3f0a6e164c290@kernel.org \
--to=tamird@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=emil@etsalapatis.com \
--cc=sashiko-reviews@lists.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.