Re: [cryptoapi/sysfs] display cipher details in sysfs

[Michal Ludvig]

On Mon, 27 Sep 2004, Andreas Happe wrote:

> Andreas Happe <andreashappe@xxxxxxxxxxxxxxx> [040910 12:55]:
> > [class - based sysfs patch]
>
> hi,
> just wanted to know if there's any feedback regarding this patch. It
> still applies to -rc2 without problems.

I have it compiled in my kernel and ... yes, it works ;-)

One thing that I noticed is that it doesn't complain when loading a second
module for the same cipher. Say that you have both aes.ko and aes-i586.ko.
You load one of them and it is registered for AES algorithm. Then you
modprobe the other one and it doesn't make an error, but the module is not
loaded. I'm not 100% sure that it is a fault in your patch, though. I
haven't tested it with a clean vanilla+your-patch kernel to avoid other
possible culprits.

BTW In http://lists.logix.cz/pipermail/cryptoapi/2004/000088.html I
described a concept of "preferences" that was done for the current
cryptoapi. How to do something similar with your patch applied?

If I'd finally have two or more modules for the same algorithm loaded, how
should the /sys subtree look like?

Michal Ludvig
-- 
* A mouse is a device used to point at the xterm you want to type in.
* Personal homepage - http://www.logix.cz/michal
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/