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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 5 Jul 2020 18:31:25 -0300
From:   Henrique de Moraes Holschuh <>
To:     Christoph Hellwig <>
Cc:     Simon Arlott <>,
        "James E.J. Bottomley" <>,
        "Martin K. Petersen" <>,
        Jonathan Corbet <>,
        Linux Kernel Mailing List <>,,
Subject: Re: [PATCH] scsi: sd: stop SSD (non-rotational) disks before reboot

On Thu, 18 Jun 2020, Christoph Hellwig wrote:
> > For SSDs, I don't think an extra stop should ever be an issue.
> Extra shutdowns will usually cause additional P/E cycles.

I am not so sure.  We're talking about enforcing clean shutdowns here
(from the SSD PoV).

A system reboot takes enough time that the SSD is likely to do about the
same amount of P cycles commiting to FLASH any important data that it
would trigger by a shutdown sequence, simply because it should not keep
important data in RAM for too long.  By extension, it would not increase
E cycles either.

OTOH, unclean shutdowns *always* cause extra P/E, and that's if you're
lucky enough for it to not cause anything much worse.

  Henrique Holschuh

Powered by blists - more mailing lists