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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201023091408.GA5201@lst.de>
Date:   Fri, 23 Oct 2020 11:14:08 +0200
From:   Christoph Hellwig <hch@....de>
To:     Ulf Hansson <ulf.hansson@...aro.org>
Cc:     冯锐 <rui_feng@...lsil.com.cn>,
        Christoph Hellwig <hch@....de>, Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>
Subject: Re: [PATCH 3/3] mmc: rtsx: Add SD Express mode support for RTS5261

On Fri, Oct 23, 2020 at 10:02:15AM +0200, Ulf Hansson wrote:
> > > Is there no mechanism to support read-only PCIe/NVMe based storage devices?
> > > If that is the case, maybe it's simply better to not support the readonly option
> > > at all for SD express cards?
> > >
> > I think there's no mechanism to support read-only PCIe/NVMe based storage devices.
> 
> I have looped in Christoph, maybe he can give us his opinion on this.

NVMe namespaces can have a bunch of 'write protection' modes advertised
by the controller, which Linux respects.  The controller in this case would
be part of the SD-Card.  IMHO it is a quality of implementation issue
of the SD-Card/Controller to have the the write protection mode of the
namespace(s) match that of the SD interface, and the SD card spec should
talk about that if it doesn't already.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ