Skip to contentSkip to conversation

LARGE bug with 2.4.1ac10 and loop filesystem

DISCUSSION Mircea Ciocan 4 participants 6 messages Feb 12, 2001 – Feb 13, 2001

lore
Share & tools
lore
#0 lore raw

I think I hit a bug introduced between 2.4.1ac9 and 2.4.1ac10,
and a
really bad one I belive :(.
Bug description:
Distribution: Linux Mandrake 7.2
Machine Dual PIII-950, Asus CUBX-E motheboard, 256MB RAM Compiler (kgcc -v):Reading specs from
/usr/lib/gcc-lib/i586-mandrake-linux/egcs-2.91.66/specs

                        gcc version egcs-2.91.66 19990314/Linux

(egcs-1.1.2 release)
Filesystem "loop" compiled as module, filesystem "iso9660" and
juliet
extension compiled in kernel.
Symptom: When trying to: mount blah.iso /mnt/cdrom -o loop, the
console
hangs, Ctrl-C can not interrupt the command, kill can not kill the stalled mount process and while rebooting none of the filesystems are unmounted cleanly ( it squirts messeages like umount2: / is busy,
umount2: /home is busy, etc) and on restart the filesystems are checked but fortunately no errors are found.
By greping the patch I see that some interlocks were added on
the loop
filesystem but I have no knowledge of the intricate mechanism of the filesystem to correct the problem :(.
Kernel 2.4.1ac9 works OK from that point of view. Please advise me how can I help with debugging of that further.

Thank you,

Mircea C.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/

#2 lore raw

Those patches are online somewhere ???
If you need a hand (trained monkey willing to do compilings, testing
and traceing :) I'm here.

Mircea C.

Quoted 5 lines · Alan Cox
Quoted 2 lines

Kernel 2.4.1ac9 works OK from that point of view.

That was Im afraid pure luck. Jens is currently sorting out the loop problems and has test patches

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

#3 lore raw
In reply to Mircea Ciocan
Quoted 4 lines · Alan Cox
Quoted 1 line

Kernel 2.4.1ac9 works OK from that point of view.

That was Im afraid pure luck. Jens is currently sorting out the loop problems and has test patches

By any chance, are these loop problems the same ones affecting 2.4.2-pre2 and -pre3?

Signature · 8 lines
 .--.  Michael J. Maravillo                   office://+63.2.894.3592/
( () ) Q Linux Solutions, Inc.              mobile://+63.917.897.0919/
 `--\\ A Philippine Open Source Solutions Co.  http://www.q-linux.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://vger.kernel.org/lkml/
#4 lore raw
Quoted 5 lines
Quoted 2 lines

That was Im afraid pure luck. Jens is currently sorting out the loop problems and has test patches

By any chance, are these loop problems the same ones affecting 2.4.2-pre2 and -pre3?

And to varying degrees all 2.4.x kernels right now
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/

#5 lore raw

All,

I just compiled 2.4.1-ac10 with the loop-3 patch from adoeb and it seems to fix
the loopback problems. This is for someone NOT using the encrypted FS since I
did not test this.

If anyone has a better way to make sure everything is working correctly other than using mkinitrd to test if the loopback works then please let me know.

Thanks for the fix,

Sean

Quoted 6 lines · Alan Cox
Quoted 5 lines
Quoted 2 lines

That was Im afraid pure luck. Jens is currently sorting out the loop problems and has test patches

By any chance, are these loop problems the same ones affecting 2.4.2-pre2 and -pre3?

Quoted 8 lines

And to varying degrees all 2.4.x kernels right now
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/

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