Re: bug in 2.6.0test2

From: Steve Lord (lord_at_sgi.com)
Date: 07/29/03

  • Next message: Kathy Frazier: "RE: DMA not supported with Intel ICH4 I/O controller?" 
    To: Nico Schottelius <nico-kernel@schottelius.org>
Date:	29 Jul 2003 06:43:17 -0500

    On Mon, 2003-07-28 at 17:26, Nico Schottelius wrote:
    > Steve Lord [Mon, Jul 28, 2003 at 03:47:30PM -0500]:
    > >
    > > Something else went wrong before you crashed:
    > >
    > > bio too big device loop0 (2 > 0)
    > >
    > > This means you cannot use any bio larger than zero to this device,
    >
    > assume i didn't understand very much you told me..what is a bio?
    > how do I use it? and why is it too big here?

    It looks like the loop device may not be correctly initialized yet,
    no I/O is possible to it yet.

    >
    > > which is probably why ext2 said this, since it caught the error when
    > > building the bio.
    >
    > ext2? I am wondering..afai understood that, the root wasn't even
    > decrypted, how can the kernel try to ext2-mount it?
    >
    > > EXT2-fs: unable to read superblock
    > >
    > > XFS didn't catch the error building the bio and submitted it, at
    > > which point the I/O tripped the BUG. I can fix this part, but
    > > the original problem is something I know nothing about.
    >
    > ..or better why does it start mounting/before decrypt?
    >

    I have never used a crypto loop device, so I cannot what is really
    going on. Some initialization step may be missing in the loop device
    which means it is not usable, the mount it happening because the
    kernel was told to mount it. If you are not specifying a filesystem
    type, then possibly what is happening is it is attempting to open
    the device as different filesystems, these all fail, until xfs
    which does not detect the underlying error on the loop device,
    and issues the IO which causes the BUG.

    So, we caused the crash, but you were on your way to one anyway,
    eventually it would have failed to find a root device and given
    up that way.

    Steve

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Kathy Frazier: "RE: DMA not supported with Intel ICH4 I/O controller?"

    Relevant Pages

    • Re: [PATCH]tar filesystem for 2.6.10-rc1-mm3(easily access tar file)
      ... I am a newbie.so your simple tar filesystem is good for me to learn ... >> oh,sorry.it's a readonly filesystem now.i will try to make it writeable. ... >> but i use tar file as loop device. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: [PATCH] barrier patch set
      ... If we must perform the barrier by tagging the ... > is the final BIO for this operation" is a fairly hard thing to do. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [BIO] Bounce queue in bio_add_page
      ... On Tue, Nov 04 2003, Herbert Xu wrote: ... >> I think the best fix would be to simply not allow more than one page ... >> that needs to be bounced to a bio. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Errors and later panics in 2.6.0-test11.
      ... instead (the memory debugging interferes with it). ... It's definitely a bio ... clone_endioends up with a freed bio. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • [2.6 patch] bio.c: make bio_destructor static (fwd)
      ... The patch forwarded below still applies and compiles against ... * default destructor for a bio allocated with bio_alloc ... send the line "unsubscribe linux-kernel" in ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)