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: <c6a8636a-98e6-61d0-ff4b-350fb3869699@synopsys.com>
Date:   Thu, 22 Sep 2016 16:21:05 +0100
From:   Joao Pinto <Joao.Pinto@...opsys.com>
To:     "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: UFS API in the kernel

Hi!

I am designing an application that has the goal to be an utility for Unipro and
UFS testing purposes. This application is going to run on top of a recent Linux
Kernel containing the new UFS stack (including the new DWC drivers).

I am considering doing the following:
a) Create a new config item called CONFIG_UFS_CHARDEV which is going to create a
char device responsible to make some IOCTL available for user-space applications
b) Create a linux/ufs.h header file that contains data structures declarations
that will be needed in user-space applications

Could you please advise me about what the correct approach should be to make it
as standard as possible and usable in the future?

Thank you very much for your help!

regards,
Joao

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ