| To: | "'Richard Gooch'" <rgooch@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | RE: Possible problem with devfs removable drives patch |
| From: | Borsenkow Andrej <Andrej.Borsenkow@xxxxxxxxxxxxxx> |
| Date: | Tue, 19 Feb 2002 08:56:05 +0300 |
| Cc: | "'devfs mailing list'" <devfs@xxxxxxxxxxx>, Robert.Fox@xxxxxxxxxxx |
| Importance: | Normal |
| In-reply-to: | <200202181922.g1IJMIs03173@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-devfs@xxxxxxxxxxx |
>
> Odd. This should never happen. If you look at the code for
> devfs_register_disc(), you will see the very first line:
> if (dev->part[minor].de) return;
>
> which prevents duplicate registrations. The only way I can see this
> failing is if the "disc" entry for a different device is registered,
> but *the parent directory names are the same*. You can test this by
> putting a debugging line two lines after the call to
> devfs_generate_path() thus:
> printk ("Constructed: \"%s\"", dirname + 3 + pos);
>
> and then send me the kernel messages between the PIIX4: message and
> the error message you highlighted.
You mean attached patch? Robert could you try it?
-andrej
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] a little strings-aware code change, Denis Zaitsev |
|---|---|
| Next by Date: | RE: Possible problem with devfs removable drives patch, Richard Gooch |
| Previous by Thread: | Re: Possible problem with devfs removable drives patch, Richard Gooch |
| Next by Thread: | RE: Possible problem with devfs removable drives patch, Richard Gooch |
| Indexes: | [Date] [Thread] [Top] [All Lists] |