public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Announce loop-AES-v3.6b file/swap crypto package
Date: Sat, 26 Feb 2011 20:40:43 +0200	[thread overview]
Message-ID: <4D69492B.CB694458@users.sourceforge.net> (raw)

loop-AES changes since previous release:
- Fixed a bug that can cause "NULL pointer dereference" at /dev/md* backing
  device, and possibly other backing devices that call __bio_clone(). This
  bug is present in loop-AES-v3.6a (and loop-AES-v3.5 versions with
  linux-2.6.37 or later kernels).
- Fixed a bug that can cause slow operation or even deadlock. This bug is
  present only in loop-AES-v3.6a version. Older versions are not affected.


bzip2 compressed tarball is here:

    http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.6b.tar.bz2
    md5sum 247e5a909877577bdcd246f8caada689

    http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.6b.tar.bz2.sign

-- 
Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD

                 reply	other threads:[~2011-02-26 18:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4D69492B.CB694458@users.sourceforge.net \
    --to=jariruusu@users.sourceforge.net \
    --cc=linux-crypto@vger.kernel.org \
    --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