linux-kernel - [PATCH v2 0/4] Enable UFS provisioning via Linux

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-next>] [day] [month] [year] [list]

Message-Id: <20180615210049.126123-1-evgreen@chromium.org>
Date:   Fri, 15 Jun 2018 14:00:45 -0700
From:   Evan Green <evgreen@...omium.org>
To:     Vinayak Holikatti <vinholikatti@...il.com>,
        "James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        Stanislav Nijnikov <stanislav.nijnikov@....com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Bart Van Assche <Bart.VanAssche@....com>,
        Adrian Hunter <adrian.hunter@...el.com>,
        linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Cc:     Evan Green <evgreen@...omium.org>
Subject: [PATCH v2 0/4] Enable UFS provisioning via Linux

This series enables provisioning UFS devices using the existing sysfs
interface. This functionality is primarily useful along the assembly
line, but might also be useful for end users that receive devices that
aren't locked down.

Changes since v1:
	- Reworked the interface to show each unit of the config
descriptor as a separate directory, rather than the previous method I
had of a file for selecting the unit, and then a common set of files
that interacted with whichever unit was selected. I did some kobject
magic to accomplish this. I noticed from Greg KH's reply to Sayali's
patches [1] that configfs might be the preferred method. Let me know
if I should abandon this series in favor of Sayali's, with the
possible exception of "Make sysfs attributes writable".
	- Squashed documentation changes into their respective code
changes.
	- I decided to keep the config descriptor attributes as their
own files, rather than hiding writes behind device descriptor and unit
descriptor, as I think that's more future proof and true to the UFS spec.

[1] https://lkml.org/lkml/2018/6/8/210

Evan Green (4):
  scsi: ufs: Add Configuration Descriptor to sysfs
  scsi: ufs: Make sysfs attributes writable
  scsi: ufs: Refactor descriptor read for write
  scsi: ufs: Enable writing config descriptor

 Documentation/ABI/testing/sysfs-driver-ufs | 156 ++++++++++--
 drivers/scsi/ufs/ufs-sysfs.c               | 367 +++++++++++++++++++++++++++--
 drivers/scsi/ufs/ufs-sysfs.h               |   1 +
 drivers/scsi/ufs/ufs.h                     |  29 +++
 drivers/scsi/ufs/ufshcd.c                  | 110 ++++++---
 drivers/scsi/ufs/ufshcd.h                  |  30 ++-
 6 files changed, 620 insertions(+), 73 deletions(-)

-- 
2.13.5