From: Xie Yongji <xieyongji@bytedance.com>
To: mst@redhat.com, jasowang@redhat.com, stefanha@redhat.com,
sgarzare@redhat.com, kwolf@redhat.com, mreitz@redhat.com,
mlureau@redhat.com, jsnow@redhat.com, eblake@redhat.com,
Coiby.Xu@gmail.com, hreitz@redhat.com
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: [PATCH v5 1/8] block: Support passing NULL ops to blk_set_dev_ops()
Date: Wed, 4 May 2022 15:40:44 +0800 [thread overview]
Message-ID: <20220504074051.90-2-xieyongji@bytedance.com> (raw)
In-Reply-To: <20220504074051.90-1-xieyongji@bytedance.com>
This supports passing NULL ops to blk_set_dev_ops()
so that we can remove stale ops in some cases.
Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
---
block/block-backend.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/block-backend.c b/block/block-backend.c
index e0e1aff4b1..35457a6a1d 100644
--- a/block/block-backend.c
+++ b/block/block-backend.c
@@ -1062,7 +1062,7 @@ void blk_set_dev_ops(BlockBackend *blk, const BlockDevOps *ops,
blk->dev_opaque = opaque;
/* Are we currently quiesced? Should we enforce this right now? */
- if (blk->quiesce_counter && ops->drained_begin) {
+ if (blk->quiesce_counter && ops && ops->drained_begin) {
ops->drained_begin(opaque);
}
}
--
2.20.1
next prev parent reply other threads:[~2022-05-04 7:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 7:40 [PATCH v5 0/8] Support exporting BDSs via VDUSE Xie Yongji
2022-05-04 7:40 ` Xie Yongji [this message]
2022-05-18 13:22 ` [PATCH v5 1/8] block: Support passing NULL ops to blk_set_dev_ops() Stefan Hajnoczi
2022-05-04 7:40 ` [PATCH v5 2/8] block-backend: Introduce blk_get_guest_block_size() Xie Yongji
2022-05-18 13:16 ` Stefan Hajnoczi
2022-05-19 8:03 ` Yongji Xie
2022-05-04 7:40 ` [PATCH v5 3/8] block/export: Abstract out the logic of virtio-blk I/O process Xie Yongji
2022-05-18 13:13 ` Stefan Hajnoczi
2022-05-19 8:09 ` Yongji Xie
2022-05-04 7:40 ` [PATCH v5 4/8] linux-headers: Add vduse.h Xie Yongji
2022-05-18 13:22 ` Stefan Hajnoczi
2022-05-04 7:40 ` [PATCH v5 5/8] libvduse: Add VDUSE (vDPA Device in Userspace) library Xie Yongji
2022-05-18 13:46 ` Stefan Hajnoczi
2022-05-19 8:11 ` Yongji Xie
2022-05-04 7:40 ` [PATCH v5 6/8] vduse-blk: Implement vduse-blk export Xie Yongji
2022-05-18 13:50 ` Stefan Hajnoczi
2022-05-04 7:40 ` [PATCH v5 7/8] vduse-blk: Add vduse-blk resize support Xie Yongji
2022-05-18 13:51 ` Stefan Hajnoczi
2022-05-04 7:40 ` [PATCH v5 8/8] libvduse: Add support for reconnecting Xie Yongji
2022-05-18 14:03 ` Stefan Hajnoczi
2022-05-19 8:25 ` Yongji Xie
2022-05-19 9:44 ` Stefan Hajnoczi
2022-05-19 10:02 ` Yongji Xie
2022-05-19 11:28 ` Stefan Hajnoczi
2022-05-13 10:03 ` [PATCH v5 0/8] Support exporting BDSs via VDUSE Michael S. Tsirkin
2022-05-17 13:02 ` Yongji Xie
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=20220504074051.90-2-xieyongji@bytedance.com \
--to=xieyongji@bytedance.com \
--cc=Coiby.Xu@gmail.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mlureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).