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]
Date:   Thu, 28 Jul 2022 20:29:00 +0000
From:   Avri Altman <Avri.Altman@....com>
To:     Chetan C R <quic_cchinnad@...cinc.com>,
        "bvanassche@....org" <bvanassche@....org>
CC:     "jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>
Subject: RE: [PATCH V3] scsi: ufs: Get boot device storage type from command
 line

 
> Get the boot device storage type by reading it from kernel command line
> arguments and export the same information to ufs modules.
Who are the callers of get_storage_boot_device?
Is this code designated for ufs boot devices?
If yes, maybe we should call it get_ufs_boot_device?
Otherwise, why is it in the ufs core?

Thanks,
Avri 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ