public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-crypto@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: Announce loop-AES-v3.1c file/swap crypto package
Date: Sat, 21 Jan 2006 18:27:36 +0200	[thread overview]
Message-ID: <43D260F8.B82BCB9A@users.sourceforge.net> (raw)
In-Reply-To: 20060120195035.GA9685@mars.ravnborg.org

Sam Ravnborg wrote:
> Either something is missing in the support for external modules in the
> kernel or you are overdoing some stuff. If there is something missing in
> the kernel to support external modules then please say so, so it can be
> fixed.

Missing functionality:
1) "make M=/path/to/dir modules_install" does not run depmod. Pulling
   correct depmod info from kernel Makefile needs ugly hacks.
2) Try building external module A that exports some function, and then build
   another external module B (separate package, only knows function
   prototype) that uses said exported function. And I mean build it cleanly
   without puking error messages on me. 2.4 and older kernel got that right,
   but 2.6 is still FUBAR. Serious regression here.

Both above cases can be (and need to be) worked around using ugly hacks.

Sam,
Please understand that loop-AES needs to work with 2.0, 2.2, 2.4 and 2.6
kernels. Not just latest mainline, but all of them, including ones that you
cannot retroactively change.

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

  reply	other threads:[~2006-01-21 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 15:49 Announce loop-AES-v3.1c file/swap crypto package Jari Ruusu
2006-01-20 19:50 ` Sam Ravnborg
2006-01-21 16:27   ` Jari Ruusu [this message]
2006-01-21 22:10     ` Sam Ravnborg
2006-01-28 22:57     ` Sam Ravnborg
2006-01-29 14:47       ` Jari Ruusu

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=43D260F8.B82BCB9A@users.sourceforge.net \
    --to=jariruusu@users.sourceforge.net \
    --cc=linux-crypto@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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