Re: megaraid /proc under kernel 2.6.2

[Paul Wagland <paul@wagland.net>]

[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]

Hi again, further information to add....

On Sun, 2004-02-15 at 23:41, Paul Wagland wrote:
> the board. So, I am assuming that mega_create_proc_entry() is called.
> The first thing that this does is to call (effectively)
> proc_mkdir("hba0", mega_proc_dir_entry); The only way that this can fail
> to create /proc/megaraid/hba0 (as far as I can see) is if
> mega_proc_dir_entry is null. The only way that it can be null, is if
> megaraid_probe_one() is called before megaraid_init(), since the
> megaraid directory is created.

After adding some printk's to figure out what was going on, I am
officially confused. I added this line:

printk(KERN_WARNING "megaraid: trying to proc_mkdir index:%d, parent:%p, procdir:%s\n",index, parent, string);

to mega_create_proc_entry() which gives this response when booting the
kernel and loading the module:

megaraid: trying to proc_mkdir index:0, parent:00000000, procdir:hba0

Now, the problem is that this means that the following lines:

	controller_proc_dir_entry =
		adapter->controller_proc_dir_entry = proc_mkdir(string, parent);

	if(!controller_proc_dir_entry) {
		printk(KERN_WARNING "\nmegaraid: proc_mkdir failed\n");
		return;
	}

should print a warning and return. Well, it may or may not be returning,
but the "proc_mkdir failed" never turns up. But, if you pass NULL into
proc_mkdir as the parent, then it will return NULL as a result, or at
least it will as far as I can tell.

So, why is that message not turning up?

I have not looked any further into the missing driver references
problem, hopefully someone else will know what that problem is :-)

Cheers,
Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]