public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jari Ruusu <jari.ruusu@pp.inet.fi>
To: L Larssen <rescue_disk_13@usa.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: international patches from kerneli far behind
Date: Sat, 02 Jun 2001 03:25:59 +0300	[thread overview]
Message-ID: <3B183297.4D8F77F0@pp.inet.fi> (raw)
In-Reply-To: <20010601201659.9930.qmail@nwcst337.netaddress.usa.net>

L Larssen wrote:
> Sorry if this subject does not fit in this list.
> I am a bit worried about the development of the international kernel patches
> from kerneli.org.
> 
> These patches are getting far behind on the real kernel distributions.
> At this moment the latest patches are 2.2.18.3 and 2.4.3.1 while the kernel at
> now is at 2.2.19 and 2.4.5.
> 
> There is now news to the public why these patches are falling behind.
> 
> I hope more people are consirned about this.

International crypto patch is misdesigned and broken, period. Block device
drivers are supposed handle varying transfer sizes, international crypto
patch doesn't. Loop device transfers are supposed to be re-entrant,
international crypto patch transfers are not. Summary: international crypto
patch will corrupt your data. Avoid using it.

If you don't want to play russian roulette with your data, you should
consider using loop-AES package. loop-AES announcement is here:

    http://mail.nl.linux.org/linux-crypto/2001-05/msg00003.html
    http://marc.theaimsgroup.com/?l=linux-crypto&m=98923954103730&w=2

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

  reply	other threads:[~2001-06-02  0:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-01 20:16 international patches from kerneli far behind L Larssen
2001-06-02  0:25 ` Jari Ruusu [this message]
2001-06-02  5:56 ` Danny ter Haar

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=3B183297.4D8F77F0@pp.inet.fi \
    --to=jari.ruusu@pp.inet.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rescue_disk_13@usa.net \
    /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