linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: martin@kfib.org (martin@kfib.org)
To: linux-kernel@vger.kernel.org
Cc: marcelo@conectiva.com.br
Subject: [PATCH] Bug in initrd-handling still there in 2.4.22-pre7
Date: 23 Jul 2003 16:16:56 +0200	[thread overview]
Message-ID: <m37k69s4yv.fsf@neko.kfib.org> (raw)

>From original posting (2 weeks ago):

> At work we've encountered a problem when trying to netboot 2.4.21.
> After /linuxrc has been executed and the kernel tries to remount the
> root, it panics with the all too well known message "Unable to mount
> root fs on ...".
> 
> The kernel bugs out in mount_block_root in the file init/do_mounts.c,
> to be more precise in the for-loop. What happens is that it tries to
> mount the file system as type ext2 (which happens to be first in the
> list in our case), but instead of returning -EINVAL it returns -EBUSY,
> the loop exits instead of trying the next (correct) fs-type and the
> kernel panics.

Patch for 2.4.22-pre7:

--- linux-2.4.22-pre7/init/do_mounts.c.orig     Wed Jul 23 16:16:51 2003
+++ linux-2.4.22-pre7/init/do_mounts.c  Wed Jul 23 16:16:54 2003
@@ -360,6 +360,7 @@
                                flags |= MS_RDONLY;
                                goto retry;
                        case -EINVAL:
+                       case -EBUSY:
                                continue;
                }
                /*

It's been broken since 2.4.19, so I definitely think it's about time it
gets fixed. ;>

-- 
Martin Persson           martin@kfib.org
http://martin.kfib.org/  http://ss.kfib.org/

  "esound is junk. The only thing esd has is a good client API for
   going boing at approximately the right time. Anything else is
   beyond it." -- Alan Cox

                 reply	other threads:[~2003-07-23 14:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m37k69s4yv.fsf@neko.kfib.org \
    --to=martin@kfib.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).