From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Mark Brown" <broonie@kernel.org>,
"Kumar Kartikeya Dwivedi" <memxor@gmail.com>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Alexei Starovoitov" <ast@kernel.org>,
"Andrii Nakryiko" <andrii@kernel.org>,
"bpf" <bpf@vger.kernel.org>,
"Networking" <netdev@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-next@vger.kernel.org>
Subject: Re: Fixes tags need work in the bpf-next tree
Date: Mon, 02 Nov 2026 16:56:33 +0000 [thread overview]
Message-ID: <DMKVTEMTLA43.8R6RXYD1UMWN@gmail.com> (raw)
In-Reply-To: <auiZYnNYLEgcR6TT@sirena.org.uk>
On Mon Nov 2, 2026 at 2:08 PM UTC, Mark Brown wrote:
> In commit
>
> b73855c31c7be ("libbpf: Enforce program limit only for loaded programs")
>
> Fixes tag
>
> Fixes: c9b2a0975c39 ("libbpf: Reject excessive program counts in generated loaders")
yeah. it's wrong, but it's too far behind to fix. We don't force push to address such mistakes.
prev parent reply other threads:[~2026-11-02 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 14:08 Fixes tags need work in the bpf-next tree Mark Brown
2026-11-02 16:56 ` Alexei Starovoitov [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=DMKVTEMTLA43.8R6RXYD1UMWN@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@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 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.