[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8ae86a4b-1c4b-48cc-b584-f61f4e13ac4b@proxmox.com>
Date: Fri, 10 Jan 2025 12:50:44 +0100
From: Friedrich Weber <f.weber@...xmox.com>
To: Aaron Conole <aconole@...hat.com>, Ilya Maximets <i.maximets@....org>
Cc: netdev@...r.kernel.org, dev@...nvswitch.org,
Luca Czesla <luca.czesla@...l.schwarz>, linux-kernel@...r.kernel.org,
Felix Huettner <felix.huettner@...l.schwarz>,
Eric Dumazet <edumazet@...gle.com>, Simon Horman <horms@...nel.org>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [ovs-dev] [PATCH net] openvswitch: fix lockup on tx to
unregistering netdev with carrier
On 09/01/2025 18:05, Aaron Conole wrote:
> [...]
>
> I tried on with my VMs to reproduce the issue as described in the email
> report, but I probably didn't give enough resources (or gave too many
> resources) to get the race condition to bubble up. I was using kernel
> 6.13-rc5 (0bc21e701a6f) also.
Thanks for trying the reproducer! Sounds plausible that the resources
assigned to the VM make the issue more/less likely to trigger, and I
didn't describe them very well. Just in case it helps, I've just posted
a reply [1] with the QEMU command line I've been using.
[1]
https://mail.openvswitch.org/pipermail/ovs-discuss/2025-January/053426.html
Powered by blists - more mailing lists