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]
Message-ID: <BY5PR04MB6705B7357AFEDF3AB07E1560FC1D0@BY5PR04MB6705.namprd04.prod.outlook.com>
Date:   Thu, 22 Oct 2020 06:52:06 +0000
From:   Avri Altman <Avri.Altman@....com>
To:     Chanho Park <chanho61.park@...sung.com>,
        'Bart Van Assche' <bvanassche@....org>,
        "jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
        "martin.petersen@...cle.com" <martin.petersen@...cle.com>
CC:     "alim.akhtar@...sung.com" <alim.akhtar@...sung.com>,
        "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] scsi: ufs: make sure scan sequence for multiple hosts

> 
> > > Did you mean /dev/disk/by-[part]label/ symlink? It's quite reasonable to
> > > use them by udev in userspace such as initramfs but some cases does not
> > use
> > > initramfs or initrd. In that case, we need to load the root
> > > device(/dev/sda[N]) directly from kernel.
> >
> > Please use udev or systemd instead of adding code in the UFS driver that
> > is
> > not necessary when udev or systemd is used.
> >
> 
> What I mentioned was how it can be handled when we mount rootfs directly
> from kernel.
> 
> 1) kernel -> initramfs (mount root) -> systemd
> 2) kernel (mount root) -> systemd
>  -> In this case, we normally use root=/dev/sda1 from kernel commandline to
> mount the rootfs.
> 
> Like fstab can support legacy node mount, ufs driver also needs to provide an
> option for using the permanent legacy node. If you're really worry about adding
> a new codes for all UFS driver, we can put this as controller specific or optional
> feature.
In case you'll convince Bart that this code is needed, maybe use a IDA handle for that?

Thanks,
Avri

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ