linux-kernel - Re: SCSI discover order strangeness [Bug 8412] New: CONFIG_MOUSE

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: <17975.3196.435174.722895@notabene.brown>
Date:	Tue, 1 May 2007 19:46:36 +1000
From:	Neil Brown <neilb@...e.de>
To:	bugme-daemon@...zilla.kernel.org
Cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: SCSI discover order strangeness [Bug 8412] New: CONFIG_MOUSE_PS2 makes RAID detection fail

[Please reply-to-all rather than replying through bugzilla so that
 people on cc list get to see replies...
 I hope bugzilla can pick the Bug number out of the middle of the
 subject line....]

On Tuesday May 1, bugme-daemon@...zilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8412
> 
>            Summary: CONFIG_MOUSE_PS2 makes RAID detection fail

Based on subsequent comments, I think you got that backwards - absense
of CONFIG_MOUSE_PS2 makes RAID detection fail, but no matter..

>     Kernel Version: 2.6.21
>             Status: NEW
>           Severity: low
>              Owner: io_md@...nel-bugs.osdl.org
>          Submitter: shutdown@...nd.org
> 
> Problem Description: If a kernel without CONFIG_MOUSE_PS2 enabled is used, the
> kernel won't detect my RAID1 array, but the hard drives it consits of are
> properly detected and the partition type reads "FD - Linux Raid Autodetect" as well.
> No /dev/md0 is created while booting the kernel.
> I built 2.6.21 with the same .config except for CONFIG_MOUSE_PS2 twice for
> testing purposes and discovered this weird thing.
> I'm going to attach the .config (without CONFIG_MOUSE_PS2), the dmesg of this
> kernel as well as the CONFIG_MOUSE_PS2-enabled kernels dmesg.

In the failure case, the SCSI drives (sdb, sdc) on which your raid
resides are not getting detected until after md initialisation has
decided that there is nothing to assemble.

My first thought was that the new threaded device discovery was
allowing md init to happen before scsi discovery was complete.  Maybe
the presence of CONFIG_MOUSE_PS2 makes some bit go faster...

However 
  # CONFIG_SCSI_SCAN_ASYNC is not set

so maybe not...

Greg (or anyone else reading): you know about this threaded
discovery.. could it allow some discovery to complete after userspace
has started, and does CONFIG_SCSI_SCAN_ASYNC affect it?

I think you best bet is to not depend on raid-auto-detect but to run
mdadm to assemble your arrays instead.  As your root isn't on md/raid,
that should be trivial to arrange.

NeilBrown
-
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/