From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Hannes Laimer <h.laimer@proxmox.com>
Subject: applied: [PATCH pve-kernel] fix #8217: cherry-pick fix for flowtable vlan packets being untagged
Date: Wed, 28 Oct 2026 16:02:56 +0100 [thread overview]
Message-ID: <179319977473.1358349.16326462313899768480.b4-ty@b4> (raw)
In-Reply-To: <20261027142306.3245660-1-h.laimer@proxmox.com>
On Tue, 27 Oct 2026 15:23:06 +0100, Hannes Laimer wrote:
> The problem was that after the walk to construct the flowtable entry
> it was possible that only part of the constructed entry was copied
> into the table. Namely when the egress device the walk discovered in
> its chain was not in the set of devices for the flowtable. That
> resulted in the entry construction failing half way through, but the
> egress being set. That led to a flowtable entry for a vlan device that
> had its egress set, but missed the step to set the tag in its entry.
>
> [...]
Applied, thanks!
[1/1] fix #8217: cherry-pick fix for flowtable vlan packets being untagged
commit: 80c6388d3f54ac35bf6e30ad39fb620270a392c1
prev parent reply other threads:[~2026-10-28 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 14:23 [PATCH pve-kernel] fix #8217: cherry-pick fix for flowtable vlan packets being untagged Hannes Laimer
2026-10-28 15:02 ` Thomas Lamprecht [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=179319977473.1358349.16326462313899768480.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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.