linux-kernel - Re: [PATCH] mptsas: scan the logical volume at first

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: <46D3557C.9010500@sun.com>
Date:	Mon, 27 Aug 2007 15:51:40 -0700
From:	Yinghai Lu <Yinghai.Lu@....COM>
To:	"Moore, Eric" <Eric.Moore@....com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	"Prakash, Sathya" <Sathya.Prakash@....com>,
	James Bottomley <James.Bottomley@...eleye.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org
Subject: Re: [PATCH] mptsas: scan the logical volume at first

Moore, Eric wrote:
> On Monday, August 27, 2007 11:58 AM,  Yinghai Lu wrote:
>> [PATCH] mptsas: scan the logical volume at first
>>
>> user like to see the raid show as /dev/sda before left raw disks.
>> So scan the volume at first to make their life easier.
>>
>> Signed-off-by: Yinghai Lu <yinghai.lu@....com>
>>
> 
> Although I agree with the patch, there are people on this list that will
> reject it due to the fact distro's ship today having udev label and
> device id mapping, so device ordering should be an non-issue.  However

even so, user still can customize it to use /dev/sdaX as root instead of use /dev/scsi/by-id/...or LABEL=/ as root.

> there are systems that ship that don't have BIOS BBS support, allowing
> you to select the boot device. Without it BBS support, you are forced to
> boot to the lowest device id.  There are HP and Dell systems like that.
> Are SUN systems like that?   If so, there is an additional patch which I
> have yet posted that will sort the raid volumes in acsending order.
> Currently they are in descending order (due to Firmware putting them in
> that order), which if you did a install to what you think is /dev/sda,
> its really the highest target id, and when you reboot, the BIOS will
> boot to the lowest id, which is /dev/sdb, and it will not find the boot
> partition.
Yes, I was wondering why kernel.org mainline will have /dev/sdb for first raid. but it seems RHEL 5 kernel have first raid before second raid...( it 
after all left over raw devices..), maybe they already aplied some patch?

can you send out patch?

Thanks

Yinghai Lu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/