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]
Message-ID: <61B9BF2C.6070703@huawei.com>
Date:   Wed, 15 Dec 2021 18:10:52 +0800
From:   Liuxiangdong <liuxiangdong5@...wei.com>
To:     <xieyongji@...edance.com>
CC:     "Fangyi (Eric)" <eric.fangyi@...wei.com>, <kvm@...r.kernel.org>,
        <linux-fsdevel@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <mst@...hat.com>, <netdev@...r.kernel.org>,
        <virtualization@...ts.linux-foundation.org>
Subject: Re: [PATCH v9 00/17] Introduce VDUSE - vDPA Device in Userspace

Hi, yongji.

In vduse patches serial[1], you said "The support for other device types
can be added after the security issue of corresponding device driver
is clarified or fixed in the future."

What does this "security issue" mean?

[1]https://lore.kernel.org/all/20210831103634.33-1-xieyongji@bytedance.com/

Do you mean that vduse device is untrusted, so we should check config or 
data transferred
from vduse to virtio module? Or something others?
Because I found you added some validation in virtio module just like 
this patch[2].

[2]https://lore.kernel.org/lkml/20210531135852.113-1-xieyongji@bytedance.com/

Thanks!
Xiangdong Liu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ