public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: Please apply commit 9990ddf47d41 ("net: tunnel: make skb_vlan_inet_prepare() return drop reasons") down to 6.1.y at least
Date: Tue, 17 Feb 2026 11:57:25 +0100	[thread overview]
Message-ID: <2026021740-mom-remix-8103@gregkh> (raw)
In-Reply-To: <177132401902.2893171.1371685164011289024@eldamar.lan>

On Tue, Feb 17, 2026 at 11:28:20AM +0100, Salvatore Bonaccorso wrote:
> Hi stable maintainers,
> 
> 9990ddf47d41 ("net: tunnel: make skb_vlan_inet_prepare() return drop
> reasons") was alrady backported as well to 6.12.71 to address a
> regression when backporting 81c734dae203 ("ip6_tunnel: use
> skb_vlan_inet_prepare() in __ip6_tnl_rcv()") (this one was backported
> without the prequisite commit to 6.12.67, 6.6.122, 6.1.162, 5.15.199
> and 5.10.249).
> 
> Can you pick please as well 9990ddf47d41 for the other stable series
> as needed? I can only give a confirmation that it works as exepcted
> for the 6.1.y series as per https://bugs.debian.org/1127823#36 .

it does not apply to any of those older kernels, which is probably why
it didn't get added there.  I tried to do the backport myself, but the
changes to drivers/net/vxlan/vxlan_core.c doesn't make sense to me, so I
can't do it, sorry.

Do you have a working backport anywhere?

thanks,

greg k-h

  reply	other threads:[~2026-02-17 10:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 10:28 Please apply commit 9990ddf47d41 ("net: tunnel: make skb_vlan_inet_prepare() return drop reasons") down to 6.1.y at least Salvatore Bonaccorso
2026-02-17 10:57 ` Greg Kroah-Hartman [this message]
2026-02-17 18:29   ` Salvatore Bonaccorso
2026-02-17 18:47     ` Sasha Levin
2026-02-21 21:14       ` Ben Hutchings
2026-02-21 22:42         ` Ben Hutchings

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=2026021740-mom-remix-8103@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=carnil@debian.org \
    --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