Re: Linux 2.6.19

[Udo A. Steinberg]

--Sig_lNHeAuU2SpU9h3j26PeBDj+
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Wed, 29 Nov 2006 14:21:21 -0800 (PST) Linus Torvalds (LT) wrote:

LT> So go get it. It's one of those rare "perfect" kernels. So if it doesn'=
t=20
LT> happen to compile with your config (or it does compile, but then does=20
LT> unspeakable acts of perversion with your pet dachshund), you can rest e=
asy=20
LT> knowing that it's all your own d*mn fault, and you should just fix your=
=20
LT> evil ways.

Ok, so 2.6.18 used to get along fine with cryptoloop and 2.6.19 refuses to
cooperate. An strace of "losetup -e aes /dev/loop0 /dev/hda7" without all t=
he
terminal interaction shows:

open("/dev/hda7", O_RDWR|O_LARGEFILE)   =3D 3
open("/dev/loop0", O_RDWR|O_LARGEFILE)  =3D 4
mlockall(MCL_CURRENT|MCL_FUTURE)        =3D 0
...
munmap(0xb7fc8000, 4096)                =3D 0
ioctl(4, 0x4c00, 0x3)                   =3D 0
close(3)                                =3D 0
ioctl(4, 0x4c04, 0xbfc21670)            =3D -1 ENOENT (No such file or dire=
ctory)
ioctl(4, 0x4c02, 0xbfc215e0)            =3D -1 ENOENT (No such file or dire=
ctory)
dup(2)                                  =3D 3
fcntl64(3, F_GETFL)                     =3D 0x8002 (flags O_RDWR|O_LARGEFIL=
E)
fstat64(3, {st_mode=3DS_IFCHR|0720, st_rdev=3Dmakedev(4, 1), ...}) =3D 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}=
) =3D 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
=3D 0xb7fc8000
_llseek(3, 0, 0xbfc21040, SEEK_CUR)     =3D -1 ESPIPE (Illegal seek)
write(3, "ioctl: LOOP_SET_STATUS: No such "..., 50ioctl: LOOP_SET_STATUS: N=
o such file or directory) =3D 50
close(3)                                =3D 0
munmap(0xb7fc8000, 4096)                =3D 0
ioctl(4, 0x4c01, 0)                     =3D 0
close(4)                                =3D 0
exit_group(1)                           =3D ?

Linux 2.6.18 does not fail at

	ioctl(4, 0x4c04, ...)

I know that dm-crypt is now the preferred method of doing such things, but =
as
long as cryptoloop exists in the kernel I'd expect it to work.

Cheers,
	- Udo

--Sig_lNHeAuU2SpU9h3j26PeBDj+
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFbiUbnhRzXSM7nSkRAhTHAJ4rkooLVFko48Bg0gdYTDIRN9rx8ACcCqCz
xE6c+0RcmJN9LJfY+9+Geao=
=sZww
-----END PGP SIGNATURE-----

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