>Number:         14862
>Category:       kern
>Synopsis:       raidframe autoconfig causes panic during startup
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 07 01:47:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Wolfgang Stukenbrock
>Release:        NetBSD 1.5.2 release
>Organization:
Dr. Nagler & Company GmbH
>Environment:
	
System: NetBSD test-s3 1.5.2 NetBSD 1.5.2 (NSW-Firewall) #2: Thu Nov 29 15:07:53 CET 2001 wgstuken@test-s4:/export/netbsd-1.5.2/usr/src/sys/arch/i386/compile/NSW-Firewall i386


>Description:
	If for some reasons the raid configuration information on the harddisk get wired, the raidframe driver
	tries to autoconfigure raid-devices that are not configured in the kernel.
        The kernel variable numraid is set to 4 (as mentioned in the kernel configuration file). This will configure
	4 raidframe devices numbered 0 to 3.
	But in the file rf_netbsdkintf.c for example, valid raid device numbers are checked with '< 0" and '>= numraid'.
	This will accept raid4, but no memory has been allocated for that before ...
>How-To-Repeat:
	corrupt raidframe autoconfigure information so that raidframe assumes to configure a raid4 device and reboot.
>Fix:
	replace the '>=" by '>' in various places in the raidframe driver sources
>Release-Note:
>Audit-Trail:
>Unformatted: