From: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.19
Date: Thu, 30 Nov 2006 01:26:00 +0100 [thread overview]
Message-ID: <20061130012600.0dcb1337@laptop.hypervisor.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0611291411300.3513@woody.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]
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
LT> happen to compile with your config (or it does compile, but then does
LT> unspeakable acts of perversion with your pet dachshund), you can rest easy
LT> knowing that it's all your own d*mn fault, and you should just fix your
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 the
terminal interaction shows:
open("/dev/hda7", O_RDWR|O_LARGEFILE) = 3
open("/dev/loop0", O_RDWR|O_LARGEFILE) = 4
mlockall(MCL_CURRENT|MCL_FUTURE) = 0
...
munmap(0xb7fc8000, 4096) = 0
ioctl(4, 0x4c00, 0x3) = 0
close(3) = 0
ioctl(4, 0x4c04, 0xbfc21670) = -1 ENOENT (No such file or directory)
ioctl(4, 0x4c02, 0xbfc215e0) = -1 ENOENT (No such file or directory)
dup(2) = 3
fcntl64(3, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat64(3, {st_mode=S_IFCHR|0720, st_rdev=makedev(4, 1), ...}) = 0
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7fc8000
_llseek(3, 0, 0xbfc21040, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(3, "ioctl: LOOP_SET_STATUS: No such "..., 50ioctl: LOOP_SET_STATUS: No such file or directory) = 50
close(3) = 0
munmap(0xb7fc8000, 4096) = 0
ioctl(4, 0x4c01, 0) = 0
close(4) = 0
exit_group(1) = ?
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-30 0:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 22:21 Linux 2.6.19 Linus Torvalds
2006-11-29 22:55 ` Romano Giannetti
2006-11-29 23:11 ` Randy Dunlap
2006-11-29 23:21 ` Alan
2006-11-29 23:15 ` Randy Dunlap
2006-11-29 23:25 ` Geraldo Netto
2006-11-29 23:32 ` Randy Dunlap
2006-11-29 23:31 ` Geraldo Netto
2006-11-29 23:52 ` Linus Torvalds
2006-11-30 0:56 ` Greg Norris
2006-11-30 1:08 ` Randy Dunlap
2006-11-30 2:20 ` Greg Norris
2006-11-30 1:49 ` Phil Oester
2006-11-30 2:15 ` David Miller
2006-11-30 2:22 ` Phil Oester
2006-11-30 20:30 ` Malte Schröder
2006-12-02 9:48 ` Malte Schröder
2006-11-30 0:26 ` Udo A. Steinberg [this message]
2006-11-30 21:15 ` Herbert Xu
2006-11-30 22:32 ` Udo A. Steinberg
2006-11-30 23:51 ` Herbert Xu
2006-11-30 8:01 ` Jindrich Makovicka
2006-12-02 19:54 ` Matthijs
2006-12-08 18:56 ` [PATCH] fs/jfs: fix error due to PF_* undeclared Richard Knutsson
2006-12-08 19:23 ` Randy Dunlap
2006-12-08 21:29 ` Richard Knutsson
2006-12-08 21:59 ` Dave Kleikamp
2006-12-11 14:47 ` Linux 2.6.19 Romano Giannetti
2006-12-11 20:38 ` Dominik Brodowski
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=20061130012600.0dcb1337@laptop.hypervisor.org \
--to=us15@os.inf.tu-dresden.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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