From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 0/2] blk-throttle: fix a host panic setting the first throttle limit on a disk under I/O
Date: Mon, 02 Nov 2026 18:24:24 +0100 [thread overview]
Message-ID: <179364026442.2253555.12584666114221667831.b4-ty@b4> (raw)
In-Reply-To: <20261102161219.3735623-1-den@openvz.org>
On Mon, 02 Nov 2026 17:12:15 +0100, Denis V. Lunev wrote:
> blk-throttle: fix a host panic setting the first throttle limit on a disk under I/O
>
> A compute node panicked in submit_bio_noacct() under a vhost-blk worker
> (ASUP-3910):
>
> BUG: kernel NULL pointer dereference, address: 000000000000019e
> RIP: 0010:submit_bio_noacct+0x12e/0x530
> vhost_blk_req_submit+0xf7/0x1c0 [vhost_blk]
> vhost_blk_req_handle+0x3b4/0x400 [vhost_blk]
> vhost_blk_handle_guest_kick+0x1a0/0x2c6 [vhost_blk]
>
> [...]
Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.16.vz10, thanks!
[1/2] ms/blk-throttle: fix access race during throttle policy activation
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/5252718bd1d0
[2/2] ms/blk-throttle: fix throtl_data leak during disk release
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/fc434d3705a0
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-11-02 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 16:12 Denis V. Lunev
2026-11-02 16:12 ` [Devel] [PATCH hci-8.1 1/2] ms/blk-throttle: fix access race during throttle policy activation Denis V. Lunev
2026-11-02 16:59 ` no-reply
2026-11-02 17:34 ` Konstantin Khorenko
2026-11-02 16:12 ` [Devel] [PATCH hci-8.1 2/2] ms/blk-throttle: fix throtl_data leak during disk release Denis V. Lunev
2026-11-02 16:58 ` no-reply
2026-11-02 17:24 ` Konstantin Khorenko [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=179364026442.2253555.12584666114221667831.b4-ty@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.