linux-kernel - Re: Re: [PATCH 1/3] nvme: introduce bit 5 of smart critical warning

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: <0859381a-5c09-ef54-89bf-e27f79429b97@bytedance.com>
Date:   Tue, 10 May 2022 14:44:11 +0800
From:   zhenwei pi <pizhenwei@...edance.com>
To:     Christoph Hellwig <hch@....de>
Cc:     kbusch@...nel.org, sagi@...mberg.me, axboe@...com,
        linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: Re: [PATCH 1/3] nvme: introduce bit 5 of smart critical warning



On 5/10/22 13:49, Christoph Hellwig wrote:
> On Sat, May 07, 2022 at 02:50:24PM +0800, zhenwei pi wrote:
>> According to NVM Express v1.4, Section 5.14.1.2 ("SMART / Health
>> Information"), introduce bit 5 for "Persistent Memory Region has become
>> read-only or unreliable".
> 
> Given that Linux does not support the PMR, do we really need this?

OK, let's drop this change.

Klaus Jensen corrected me about OAES[7:0]. Sorry, I misunderstand this.

-- 
zhenwei pi