From: bert hubert <ahu@ds9a.nl>
To: andries.brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: what is needed to test the in-kernel crypto loop?
Date: Fri, 11 Jul 2003 15:08:59 +0200 [thread overview]
Message-ID: <20030711130859.GA15013@outpost.ds9a.nl> (raw)
Andries,
You mentioned:
[util-linux is waiting for this; when 2.6 comes out, or the
first mount/losetup comes out that uses struct loop_info64,
whichever comes first, struct loop_info64 must be considered
frozen: a stable kernel must not change API and user space
ABI must remain constant. This means that if cryptoloop is
added later, some backwards compatibility is lost.]
Is a newer losetup/mount needed to test the in-kernel crypto loop driver?
The crypto-loop code is present in the bk repository, now.
Thanks.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next reply other threads:[~2003-07-11 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 13:08 bert hubert [this message]
2003-07-11 13:46 what is needed to test the in-kernel crypto loop? Andries.Brouwer
2003-07-15 18:29 ` Valdis.Kletnieks
2003-07-16 23:30 Andries.Brouwer
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=20030711130859.GA15013@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=andries.brouwer@cwi.nl \
--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).