From: Linus Torvalds <torvalds@osdl.org>
To: Peter Lieverdink <linux@cafuego.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: loopback device + crypto = crash on 2.6.0-test7 ?
Date: Mon, 10 Nov 2003 16:15:16 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0311101613440.2881-100000@home.osdl.org> (raw)
In-Reply-To: <6.0.0.22.2.20031111101721.01bde418@caffeine.cc.com.au>
On Tue, 11 Nov 2003, Peter Lieverdink wrote:
>
> I agree that something is very broken, though. Mind you, I can only
> replicate this problem on one of my machines - the other one I've tried it
> on seems to work fine. Odder still, when I compile a kernel on the machine
> which is fine and ruin said kernel on the machine which is not fine, I
> don't experience the crash.
That _really_ sounds like your "broken machine" is nothing more than a
broken compiler (or possibly binutils, but compilers tend to be more
fragile by far, so it's more likely the compiler).
What compiler versions do you have installed on the broken vs good
machines?
Linus
next prev parent reply other threads:[~2003-11-11 0:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 7:09 loopback device + crypto = crash on 2.6.0-test7 ? Soeren Sonnenburg
2003-11-07 14:01 ` Bill Davidsen
2003-11-09 13:10 ` Florian Weimer
2003-11-09 12:23 ` Soeren Sonnenburg
2003-11-10 22:41 ` bill davidsen
2003-11-10 23:27 ` Peter Lieverdink
2003-11-10 23:46 ` bill davidsen
2003-11-11 0:15 ` Linus Torvalds [this message]
2003-11-11 8:54 ` Florian Weimer
2003-11-11 2:50 ` Valdis.Kletnieks
2003-11-11 9:43 ` Peter Lieverdink
2003-11-11 16:49 ` Linus Torvalds
2003-11-16 8:46 ` Peter Lieverdink
2004-01-06 10:36 ` Peter Lieverdink
2004-01-06 10:53 ` Matthias Hentges
2003-11-15 13:13 Jindrich Makovicka
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=Pine.LNX.4.44.0311101613440.2881-100000@home.osdl.org \
--to=torvalds@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@cafuego.net \
/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;
as well as URLs for NNTP newsgroup(s).