From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Announce loop-AES-v3.6a file/swap crypto package
Date: Tue, 25 Jan 2011 08:46:18 +0200 [thread overview]
Message-ID: <4D3E71BA.6CAA2BE8@users.sourceforge.net> (raw)
loop-AES changes since previous release:
- Worked around block layer interface breakage on 2.6.32.x, 2.6.36.x, and
2.6.37-rc kernels.
- Queue code removal/rewrite for all 2.6.x kernels. This fixes a SMP race
when more than one helper thread (per loop device) was used. Default
was/is one helper thread. This race could leave backing device in
"plugged" state when it should have been "unplugged". This race was
introduced in loop-AES-v3.5a, and affected only 2.6.37 and later kernels.
- Merged two loop kernel 2.6.x code bases back into one. This unfortunately
re-introduces lots of #ifdef spaghetti.
bzip2 compressed tarball is here:
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.6a.tar.bz2
md5sum 196d082506f2b3d94528f9e8f5b9074f
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.6a.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-01-25 6:53 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=4D3E71BA.6CAA2BE8@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