From: Daniel Borkmann <daniel@iogearbox.net>
To: Ingo Molnar <mingo@kernel.org>, Uros Bizjak <ubizjak@gmail.com>
Cc: patchwork-bot+netdevbpf@kernel.org, ast@kernel.org,
x86@kernel.org, bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND bpf v2 0/2] x86/bpf: Fixes for the BPF JIT with retbleed=stuff
Date: Wed, 3 Apr 2024 11:04:50 +0200 [thread overview]
Message-ID: <504a2e70-3bd5-a9f0-60ec-49c4b17566ae@iogearbox.net> (raw)
In-Reply-To: <Zg0Mvb6kkHceEENb@gmail.com>
On 4/3/24 10:01 AM, Ingo Molnar wrote:
> * Uros Bizjak <ubizjak@gmail.com> wrote:
>
>>>> Here is the summary with links:
>>>> - [RESEND,bpf,v2,1/2] x86/bpf: Fix IP after emitting call depth accounting
>>>> https://git.kernel.org/bpf/bpf/c/9d98aa088386
>>>> - [RESEND,bpf,v2,2/2] x86/bpf: Fix IP for relocating call depth accounting
>>>> https://git.kernel.org/bpf/bpf/c/6a537453000a
>>>
>>> Just wondering, which kernel version is this targeted for?
>>
>> The whole series is intended for the current mainline (v6.9), this is
>> why it is developed against the bpf (*not* bpf-next) branch.
>
> I see - so bpf.git:master are current-mainline BPF fixes - that's perfect.
Yes, correct, that is for mainline (v6.9).
Thanks,
Daniel
prev parent reply other threads:[~2024-04-03 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 18:55 Uros Bizjak
2024-04-01 18:55 ` [PATCH RESEND bpf v2 1/2] x86/bpf: Fix IP after emitting call depth accounting Uros Bizjak
2024-04-01 18:55 ` [PATCH RESEND bpf v2 2/2] x86/bpf: Fix IP for relocating " Uros Bizjak
2024-04-02 4:10 ` [PATCH RESEND bpf v2 0/2] x86/bpf: Fixes for the BPF JIT with retbleed=stuff patchwork-bot+netdevbpf
2024-04-03 7:26 ` Ingo Molnar
2024-04-03 7:43 ` Uros Bizjak
2024-04-03 8:01 ` Ingo Molnar
2024-04-03 9:04 ` Daniel Borkmann [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=504a2e70-3bd5-a9f0-60ec-49c4b17566ae@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=ubizjak@gmail.com \
--cc=x86@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
all inboxes | Powered by JetHome®