From: "Ricardo Cañuelo Navarro" <rcn@igalia.com>
To: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6 v2 2/2] tun: Assign missing bpf_net_context.
Date: Wed, 26 Feb 2025 10:17:11 +0100 [thread overview]
Message-ID: <8734g1ysiw.fsf@igalia.com> (raw)
In-Reply-To: <20250225110429-9120aedc655f1a8f@stable.kernel.org>
Hi,
On Tue, Feb 25 2025 at 11:13:47, Sasha Levin <sashal@kernel.org> wrote:
> Found fixes commits:
> 9da49aa80d68 tun: Add missing bpf_net_ctx_clear() in do_xdp_generic()
Thanks for catching this, this one _should_ be part of the series as
well. I'll prepare a v3 with it.
Cheers,
Ricardo
prev parent reply other threads:[~2025-02-26 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 11:56 [PATCH 6.6 v2 0/2] Set the bpf_net_context before invoking BPF XDP in the TUN driver Ricardo Cañuelo Navarro
2025-02-25 11:56 ` [PATCH 6.6 v2 1/2] net: Reference bpf_redirect_info via task_struct on PREEMPT_RT Ricardo Cañuelo Navarro
2025-02-25 16:13 ` Sasha Levin
2025-02-26 9:15 ` Ricardo Cañuelo Navarro
2025-02-25 11:56 ` [PATCH 6.6 v2 2/2] tun: Assign missing bpf_net_context Ricardo Cañuelo Navarro
2025-02-25 16:13 ` Sasha Levin
2025-02-26 9:17 ` Ricardo Cañuelo Navarro [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=8734g1ysiw.fsf@igalia.com \
--to=rcn@igalia.com \
--cc=sashal@kernel.org \
--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