public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Jari Ruusu <jari.ruusu@pp.inet.fi>
Cc: "steve j. kondik" <shade@chemlab.org>, linux-kernel@vger.kernel.org
Subject: Re: encrypted swap on loop in 2.4.10-pre12?
Date: Thu, 20 Sep 2001 14:25:55 +0200	[thread overview]
Message-ID: <20010920142555.B588@suse.de> (raw)
In-Reply-To: <1000912739.17522.2.camel@discord> <3BA907F6.3586811C@pp.inet.fi> <20010920081353.H588@suse.de> <3BA9DC30.DA46A008@pp.inet.fi>
In-Reply-To: <3BA9DC30.DA46A008@pp.inet.fi>

On Thu, Sep 20 2001, Jari Ruusu wrote:
> Jens Axboe wrote:
> > On Thu, Sep 20 2001, Jari Ruusu wrote:
> > > Cryptoapi can't be used to encrypt swap. It has nasties like sleeping in
> > > make_request_fn() and potential memory allocation deadlock.
> > 
> > sleeping in make_request_fn is not a nasty in itself, btw. in fact loop
> > just needs an emergency page pool for swap to be perfectly safe.
> 
> loop-AES provides emergency page pool for device backed loop. Take a look.

Then sleeping in make_request_fn is not a nasty at all. In fact the
kernel does it all the time anyways.

-- 
Jens Axboe


  reply	other threads:[~2001-09-20 12:26 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 [this message]
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
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=20010920142555.B588@suse.de \
    --to=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