linux-kernel - Re: [PATCH] nvme-pci: Use PCI bus address for data/queues in CMB

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] [day] [month] [year] [list]

Date:   Tue, 3 Oct 2017 09:06:49 -0600
From:   Keith Busch <keith.busch@...el.com>
To:     Abhishek Shah <abhishek.shah@...adcom.com>
Cc:     Jens Axboe <axboe@...com>, Christoph Hellwig <hch@....de>,
        Sagi Grimberg <sagi@...mberg.me>,
        linux-nvme@...ts.infradead.org,
        open list <linux-kernel@...r.kernel.org>,
        BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>,
        stable@...r.kernel.org
Subject: Re: [PATCH] nvme-pci: Use PCI bus address for data/queues in CMB

On Sat, Sep 30, 2017 at 02:30:16PM +0530, Abhishek Shah wrote:
> > On a similar note, we also break CMB usage in virutalization with direct
> > assigned devices: the guest doesn't know the host physical bus address,
> > so it sets the CMB queue address incorrectly there, too. I don't know of
> > a way to fix that other than disabling CMB.
> 
> I don't have much idea on CMB usage in virtualization... will let
> someone else comment on this.

It's okay, I think it's a gap in the NVMe specification that would allow
such usage.