public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Jari Ruusu <jari.ruusu@pp.inet.fi>
Cc: "steve j. kondik" <shade@chemlab.org>, Jens Axboe <axboe@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: encrypted swap on loop in 2.4.10-pre12?
Date: Thu, 20 Sep 2001 14:59:50 -0400	[thread overview]
Message-ID: <20010920145950.I16647@alcove.wittsend.com> (raw)
In-Reply-To: <1000912739.17522.2.camel@discord> <3BA907F6.3586811C@pp.inet.fi> <20010920081353.H588@suse.de> <3BA9DC30.DA46A008@pp.inet.fi> <20010920142555.B588@suse.de> <1000991848.569.1.camel@discord> <3BAA21B1.B579D368@pp.inet.fi> <1001006425.1498.9.camel@discord> <3BAA2D7F.DBBCFC8C@pp.inet.fi>
In-Reply-To: <3BAA2D7F.DBBCFC8C@pp.inet.fi>

On Thu, Sep 20, 2001 at 08:55:11PM +0300, Jari Ruusu wrote:
> "steve j. kondik" wrote:
> > hmm?  both cryptoapi and loop-aes work just fine when encrypting
> > anything but swap.  this is _only_ with kernel 2.4.10-pre12.  i would
> > suspect something changed that breaks swap on loopdev in general in this
> > kernel.

> loop-AES encrypted swap works just fine on 2.4.10-pre12, see:

	But that's only your system.  He obvious has a counter example
(which may not be the fault of loop-AES, but something else, that has
yet to be determined).  So the two of you are now reduced to figuring
out why his is broken as yours is not.  Standard debugging situation.

> # uname -a
> Linux debian 2.4.10-pre12 #1 Thu Sep 20 20:15:08 EEST 2001 i686 unknown
> # vmstat 
>    procs                      memory    swap          io     system         cpu
>  r  b  w   swpd   free   buff  cache  si  so    bi    bo   in    cs  us  sy  id
>  0  0  1   4708   2708   1824  12856  19  28   682   623  223   119   5  74  21
> # swapon -s
> Filename                        Type            Size    Used    Priority
> /dev/loop6                      partition       191512  4704    -1
> # losetup /dev/loop6
> /dev/loop6: [0301]:170184 (/dev/hda2) offset 0, AES encryption

> Regards,
> Jari Ruusu <jari.ruusu@pp.inet.fi>

	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw@WittsEnd.com
  (The Mad Wizard)      |  (678) 463-0932   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!


  reply	other threads:[~2001-09-20 19:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-19 15:18 encrypted swap on loop in 2.4.10-pre12? steve j. kondik
2001-09-19 15:37 ` Jens Axboe
2001-09-19 17:38   ` steve j. kondik
2001-09-19 21:02 ` Jari Ruusu
2001-09-20  6:13   ` Jens Axboe
2001-09-20 12:08     ` Jari Ruusu
2001-09-20 12:25       ` Jens Axboe
2001-09-20 13:17         ` steve j. kondik
2001-09-20 17:04           ` Jari Ruusu
2001-09-20 17:20             ` steve j. kondik
2001-09-20 17:55               ` Jari Ruusu
2001-09-20 18:59                 ` Michael H. Warfield [this message]
2001-09-21  0:36                   ` steve j. kondik
2001-09-21  9:15                     ` Jari Ruusu
2001-09-21 14:52                       ` steve j. kondik

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=20010920145950.I16647@alcove.wittsend.com \
    --to=mhw@wittsend.com \
    --cc=axboe@suse.de \
    --cc=jari.ruusu@pp.inet.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shade@chemlab.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