Netdev List
 help / color / mirror / Atom feed
From: jungwon park <jwpark@whitecode.co.kr>
To: gregkh@linuxfoundation.org
Cc: stable@vger.kernel.org, gnault@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH 6.1 000/982] 6.1.189-rc1 review
Date: Fri, 2 Oct 2026 14:16:50 +0900	[thread overview]
Message-ID: <0f382474-d85d-4736-8ee8-e934a96ae2d2@whitecode.co.kr> (raw)
In-Reply-To: <a1a0f247-e847-4598-9b84-9840ddbf50b4@whitecode.co.kr>

 > This is the start of the stable review cycle for the 6.1.189 release.
 > There are 982 patches in this series, all will be posted as a response
 > to this one.  If anyone has any issues with these being applied, please
 > let me know.
 >
 > Responses should be made by Fri, 02 Oct 2026 15:23:04 +0000.
 > Anything received after that time might be too late.
 >
 > The whole patch series can be found in one patch at:
 > 
  https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.189-rc1.gz
 > or in the git tree and branch at:
 > 
  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
linux-6.1.y
 > and the diffstat can be found below.
 >
 > thanks,
 >
 > greg k-h

Hi!

VXLAN stops working after applying patch-6.1.189-rc1.

all VXLAN packets are dropped (only the "dropped" counter keeps increasing).
This appears to be caused by the patch titled "vxlan: Pull inner IP 
header in vxlan_xmit_one()" - 667b5d5945e8947868fef8d75bf3ce4accb81b30.

It seems likely that this patch was written before the change to 
skb_vlan_inet_prepare() (net: tunnel: make skb_vlan_inet_prepare() 
return drop reasons) was implemented - 
6dedc8c2a4bfc64ef07410634e944c0506eb98c1).

Best regards,

Jungwon

       reply	other threads:[~2026-10-02  5:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a1a0f247-e847-4598-9b84-9840ddbf50b4@whitecode.co.kr>
2026-10-02  5:16 ` jungwon park [this message]
2026-10-02 12:14   ` [PATCH 6.1 000/982] 6.1.189-rc1 review Greg KH
2026-10-03 22:33     ` Sasha Levin

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=0f382474-d85d-4736-8ee8-e934a96ae2d2@whitecode.co.kr \
    --to=jwpark@whitecode.co.kr \
    --cc=gnault@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=netdev@vger.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