From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Friedrich Weber <f.weber@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH pve-kernel master 1/2] backport fix for network crashes when exiting ovs-tcpdump
Date: Fri, 24 Jan 2025 13:42:04 +0100 [thread overview]
Message-ID: <113d1a99-8508-4392-9980-d889230c95f4@proxmox.com> (raw)
In-Reply-To: <20250124102124.44227-1-f.weber@proxmox.com>
Am 24.01.25 um 11:21 schrieb Friedrich Weber:
> A user in enterprise support reported a low (<1/50) chance of network
> crash (with soft lockups reported) when exiting ovs-tcpdump (a tcpdump
> wrapper provided by Open vSwitch) which they could only resolve by
> rebooting the host.
>
> After reporting the issue upstream with a reproducer [1], an OVS
> developer submitted a kernel patch which is now included 6.13 and some
> stable kernels. With this patch, the reproducer does not seem to
> trigger the issue anymore. Hence, backport the patch.
>
> [1] https://mail.openvswitch.org/pipermail/ovs-discuss/2025-January/053423.html
>
> Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
> ---
>
> Notes:
> As the patch is included in stable kernels, it might also eventually
> appear in Ubuntu kernels, so not sure if it makes more sense to
> backport or to wait until then.
>
> ...lockup-on-tx-to-unregistering-netdev.patch | 77 +++++++++++++++++++
> 1 file changed, 77 insertions(+)
> create mode 100644 patches/kernel/0016-openvswitch-fix-lockup-on-tx-to-unregistering-netdev.patch
>
>
applied both patches, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-01-24 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 10:21 [pve-devel] " Friedrich Weber
2025-01-24 10:21 ` [pve-devel] [PATCH pve-kernel bookworm-6.8 2/2] " Friedrich Weber
2025-01-24 12:42 ` 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=113d1a99-8508-4392-9980-d889230c95f4@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.weber@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.