From: Jens Axboe <axboe@suse.de>
To: Jonathan Oppenheim <jono@Phys.UAlberta.CA>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 242-ac3 loop bug
Date: Mon, 26 Feb 2001 01:27:30 +0100 [thread overview]
Message-ID: <20010226012730.W7830@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10102251701520.2320-100000@dirac.phys.ualberta.ca>
In-Reply-To: <Pine.LNX.4.10.10102251701520.2320-100000@dirac.phys.ualberta.ca>; from jono@Phys.UAlberta.CA on Sun, Feb 25, 2001 at 05:15:52PM -0700
On Sun, Feb 25 2001, Jonathan Oppenheim wrote:
> i have also been having trouble with many cyphers including
> blowfish (although twofish and idea worked). the error seems to be the
> same in all 2.4.x kernels (i have all the relevant options compiled
> as modules eg. loopback and ciphers))
>
> i follow the encryptionhowto, but when i do a
> losetup -e blah blah blah
> i get a segmentation fault (no core, no other error
> messages as far as i can see)
>
> then, i can't rmmod the loop module and other modules because
> they are busy.
>
> so i can't unmount the disk.
>
> i haven't yet tried things with 2.4.2-ac3, but the problem
> seems to be with particular cyphers not with loopback.
So report the problem to the crypto folks people? I've seen several
of these now, but not one includes ksymoops info etc.
--
Jens Axboe
next prev parent reply other threads:[~2001-02-26 0:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 0:15 242-ac3 loop bug Jonathan Oppenheim
2001-02-26 0:27 ` Jens Axboe [this message]
2001-02-26 1:17 ` Mario Hermann
-- strict thread matches above, loose matches on Subject: below --
2001-02-24 17:32 Mark Swanson
2001-02-24 17:59 ` Doug McNaught
2001-02-24 18:11 ` Mark Swanson
2001-02-24 18:57 ` Doug McNaught
2001-02-24 19:18 ` Arjan van de Ven
2001-02-24 23:14 ` Jens Axboe
2001-02-25 7:48 ` Mircea Ciocan
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=20010226012730.W7830@suse.de \
--to=axboe@suse.de \
--cc=jono@Phys.UAlberta.CA \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).