All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH vz10-latest 1/1] openvswitch: fix soft lockup in the netlink dump callbacks #VSTOR-144650
Date: Tue, 15 Sep 2026 22:42:04 +0200	[thread overview]
Message-ID: <178950492496.2412229.2603262189008554175.b4-review@b4> (raw)
In-Reply-To: <20260915114849.3869609-1-den@openvz.org>

On Tue, 15 Sep 2026 13:48:49 +0200, Denis V. Lunev <den@openvz.org> wrote:
> A production compute node carrying a few thousand datapath flows and
> ports hit a soft lockup inside a single netlink flow dump and panicked.
> 
> ovs_flow_cmd_dump() calls ovs_flow_stats_get() for every flow it
> emits, and that releases stats->lock with spin_unlock_bh() once per
> CPU that has touched the flow. ovs_vport_cmd_dump() calls
> peernet2id_alloc() for every vport that lives in a foreign netns, and
> that releases nsid_lock with spin_unlock_bh(). Every release is a
> local_bh_enable(), and each one runs the pending softirq backlog in
> the dumping thread's own context.
> 
> [...]

Reviewed-by: Konstantin Khorenko <khorenko@virtuozzo.com>

-- 
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

  reply	other threads:[~2026-09-15 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 11:48 Denis V. Lunev
2026-09-15 20:42 ` Konstantin Khorenko [this message]
2026-09-16  9:59 ` Konstantin Khorenko

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=178950492496.2412229.2603262189008554175.b4-review@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=devel@openvz.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 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.