On Mon, Feb 26, 2001 at 08:11:55AM +0100, Mike Galbraith <[EMAIL PROTECTED]> wrote:
> Hmm.. I remember having this problem and it was a problem with strace.
Well, I obviously strace'd it to find out why I get a memory fault without
one (I would be happy if it worked without strace ;->)
> Anyway, it works fine here with virgin 2.4.2, so it seems unlikely it's
> a kernel problem.
> 259 execve("/sbin/losetup", ["losetup", "/dev/loop0", "/dev/hda5"], [/* 47 vars
>*/]) = 0
The -e switch is causing the memory fault and subsequent breakage:
743 open("/dev/hdd", O_RDWR) = 4
743 open("/dev/loop0", O_RDWR) = 5
743 mlockall(0x3, 0x804c272) = 0
743 ioctl(5, LOOP_SET_FD, 0x4) = -1 ENOSYS (Function not implemented)
743 ioctl(5, LOOP_SET_FD, 0x4) = 0
743 ioctl(5, LOOP_SET_STATUS, 0xbffff5d8) = -1 ENOSYS (Function not implemented)
743 ioctl(5, LOOP_SET_STATUS, 0xbffff5d8) = -1 ENOSYS (Function not implemented)
743 ioctl(5, LOOP_SET_STATUS, 0xbffff5d8) = -1 ENOSYS (Function not implemented)
743 ioctl(5, LOOP_SET_STATUS, 0xbffff5d8) = -1 ENOSYS (Function not implemented)
743 ioctl(5, LOOP_SET_STATUS <unfinished ...>
743 +++ killed by SIGSEGV +++
(which is a strange strace anyway...)
However, I just need to wait until there is a new crypto patch (and, if
not, I'll eventually have to hack it myself to gte my data. After all it's
source... ...)
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
-
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://www.tux.org/lkml/
