From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dominique Martinet <dominique.martinet@atmark-techno.com>
Cc: stable@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Bing-Jhong Billy Jheng <billy@starlabs.sg>,
Muhammad Ramdhan <ramdhan@starlabs.sg>,
Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH 5.10] bpf: Fix overrunning reservations in ringbuf
Date: Tue, 23 Jul 2024 15:24:46 +0200 [thread overview]
Message-ID: <2024072339-aneurism-unclaimed-bda2@gregkh> (raw)
In-Reply-To: <ZpeEo2nt-9vOPzg7@atmark-techno.com>
On Wed, Jul 17, 2024 at 05:45:23PM +0900, Dominique Martinet wrote:
> Dominique Martinet wrote on Wed, Jul 17, 2024 at 03:59:46PM +0900:
> > The only conflict with the patch was in the comment at top of the patch
> > (the commit that had changed this comment, 583c1f420173 ("bpf: Define
> > new BPF_MAP_TYPE_USER_RINGBUF map type"), has nothing to do with this
> > fix), so I went ahead with it.
> >
> > I'm not familiar with the ringbuf code but it doesn't look too wrong to
> > me at first glance; and with this all stable branches are covered.
>
> I need a bit more sleep; that obviously missed 5.15 which didn't get
> the fix backported either due to the same conflict; this commit applies
> to both branches.
>
> I've also checked something like bpftrace which uses the ring buffer for
> message passing doesn't blow up when spamming a bit on 5.10, just in
> case.
Both now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-07-23 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 6:59 [PATCH 5.10] bpf: Fix overrunning reservations in ringbuf Dominique Martinet
2024-07-17 8:45 ` Dominique Martinet
2024-07-23 13:24 ` Greg Kroah-Hartman [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=2024072339-aneurism-unclaimed-bda2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=billy@starlabs.sg \
--cc=daniel@iogearbox.net \
--cc=dominique.martinet@atmark-techno.com \
--cc=ramdhan@starlabs.sg \
--cc=stable@vger.kernel.org \
/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