[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176247202182.294230.13399520810544725524.b4-ty@kernel.dk>
Date: Thu, 06 Nov 2025 16:33:41 -0700
From: Jens Axboe <axboe@...nel.dk>
To: "Michael S. Tsirkin" <mst@...hat.com>, Jason Wang <jasowang@...hat.com>,
Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
Eugenio Pérez <eperezma@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>, Stefan Hajnoczi <stefanha@...hat.com>,
Cong Zhang <cong.zhang@....qualcomm.com>
Cc: linux-arm-msm@...r.kernel.org, virtualization@...ts.linux.dev,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
pavan.kondeti@....qualcomm.com
Subject: Re: [PATCH] virtio_blk: NULL out vqs to avoid double free on
failed resume
On Tue, 21 Oct 2025 19:07:56 +0800, Cong Zhang wrote:
> The vblk->vqs releases during freeze. If resume fails before vblk->vqs
> is allocated, later freeze/remove may attempt to free vqs again.
> Set vblk->vqs to NULL after freeing to avoid double free.
>
>
Applied, thanks!
[1/1] virtio_blk: NULL out vqs to avoid double free on failed resume
commit: 0739c2c6a015604a7c01506bea28200a2cc2e08c
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists