linux-kernel - Re: [PATCH v13 00/13] Introduce VDUSE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 11 Oct 2021 15:32:49 +0800
From:   Liuxiangdong <liuxiangdong5@...wei.com>
To:     <xieyongji@...edance.com>
CC:     "Fangyi (Eric)" <eric.fangyi@...wei.com>, <yebiaoxiang@...wei.com>,
        <x86@...nel.org>, <kvm@...r.kernel.org>,
        <linux-fsdevel@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v13 00/13] Introduce VDUSE - vDPA Device in Userspace

Hi, Yongji.

I tried vduse with null-blk:

   $ qemu-storage-daemon \
       --chardev socket,id=charmonitor,path=/tmp/qmp.sock,server,nowait \
       --monitor chardev=charmonitor \
       --blockdev 
driver=host_device,cache.direct=on,aio=native,filename=/dev/nullb0,node-name=disk0 
\
       --export 
type=vduse-blk,id=test,node-name=disk0,writable=on,name=vduse-null,num-queues=16,queue-size=128

The qemu-storage-daemon is yours 
(https://github.com/bytedance/qemu/tree/vduse)

And then, how can we use this vduse-null (dev/vduse/vduse-null) in vm(QEMU)?

Because qemu-storage-daemon open this vduse-null in vduse_dev_init(), 
all the operations which open this dev
will report "failed to open '/dev/vduse/vduse-null': Device or resource 
busy".

Or something I understood wrong?

Thanks!
Xiangdong Liu