linux-kernel - Re: [GIT PULL] libata changes for v4.10-rc1

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, 12 Dec 2016 11:04:02 -0800
From:   Christoph Hellwig <hch@...radead.org>
To:     Tejun Heo <tj@...nel.org>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] libata changes for v4.10-rc1

On Mon, Dec 12, 2016 at 01:32:09PM -0500, Tejun Heo wrote:
> Hello, Linus.
> 
> * Adam added opt-in ATA command priority support.
> 
> * There are machines which hide multiple nvme devices behind an ahci
>   BAR.  Dan Williams proposed a solution to force-switch the mode but
>   deemed too hackishd.  People are gonna discuss the proper way to
>   handle the situation in nvme standard meetings.  For now, detect and
>   warn about the situation.

I wish that was the case.  We've pretty much agreed that we'll want
to implement it as a virtual PCIe root bridge, similar to Intels other
"innovation" VMD that we work around that way.  But Intel management
has apparently decided that they don't want to spend more cycles on
this now that Lenovo has an optional BIOS that doesn't force this
broken mode anymore, and no one outside of Intel has enough information
to implement something like this.

So for now I guess this warning is it, until Intel reconsideres and
spends resources on fixing up the damage their Chipset people caused.