linux-kernel - Re: [RFC PATCH] nvme: add NO APST quirk for Kioxia device

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: <20211109080634.GA28581@lst.de>
Date:   Tue, 9 Nov 2021 09:06:34 +0100
From:   Christoph Hellwig <hch@....de>
To:     Enzo Matsumiya <ematsumiya@...e.de>
Cc:     linux-nvme@...ts.infradead.org, Keith Busch <kbusch@...nel.org>,
        Jens Axboe <axboe@...com>, Christoph Hellwig <hch@....de>,
        Sagi Grimberg <sagi@...mberg.me>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] nvme: add NO APST quirk for Kioxia device

On Fri, Nov 05, 2021 at 11:08:57PM -0300, Enzo Matsumiya wrote:
> +	},
> +	{
> +		/*
> +		 * This Kioxia device times out and aborts I/O during any load,
> +		 * but more easily reproducible with discards (fstrim).
> +		 *
> +		 * Device is left in a state that is also not possible to use "nvme set-feature"
> +		 * to disable APST, but booting with nvme_core.default_ps_max_latency=0 works.
> +		 */

Overly long lines here, but I can fix that up.  Do you have a product
name for this device or is just a nameless OEM controller?