From: Oleg G. <ol...@in...> - 2005-07-08 12:28:32
|
Hello! I've encountered a glitch preventing CryptoAPI AES module from building when compiling UML version 2.6.12. Also, bs1 patch and patch fixing errno problem mentioned earlier was applied, but they are irrelevant to the problem I describe now. New configuration option CRYPTO_AES_586 first appeared in 2.6.12 kernel. This option can be activated when architecture is 32-bit X86 and it results in building X86-opitmised code for AES encryption. On the other hand, old CRYPTO_AES option is disabled when architectire is 32-bit X86. The code for X86-optimised AES module is located in "arch/i386/crypto" subdirectory and, hence, is built only if the value of the ARCH variable is equal to "i386". But for unknown reason, CRYPTO_AES_586 option is enabled also if building UML for X86 architecture, and CRYPTO_AES option is unavailable in this case. There is no way to enable CRYPTO_AES option, but CRYPTO_AES_586 option does nothing, because there is no module for CRYPTO_AES_586 in "arch/um" subdirectory, only in "arch/i386", which is irrelevant for ARCH=um. The patch is trivial. [-- Begin of Patch --] --- linux-2.6.12/crypto/Kconfig.orig 2005-06-17 22:48:29.000000000 +0300 +++ linux-2.6.12/crypto/Kconfig 2005-07-07 17:56:18.000000000 +0300 @@ -146,7 +146,7 @@ config CRYPTO_AES tristate "AES cipher algorithms" - depends on CRYPTO && !((X86 || UML_X86) && !64BIT) + depends on CRYPTO && !(X86 && !64BIT) help AES cipher algorithms (FIPS-197). AES uses the Rijndael algorithm. @@ -166,7 +166,7 @@ config CRYPTO_AES_586 tristate "AES cipher algorithms (i586)" - depends on CRYPTO && ((X86 || UML_X86) && !64BIT) + depends on CRYPTO && (X86 && !64BIT) help AES cipher algorithms (FIPS-197). AES uses the Rijndael algorithm. [-- End of Patch --] -- Oleg Girko, http://www.infoserver.ru/~ol/ |
From: Blaisorblade <bla...@ya...> - 2005-07-09 10:44:04
|
On Friday 08 July 2005 14:28, Oleg Girko wrote: > Hello! > New configuration option CRYPTO_AES_586 first appeared in 2.6.12 kernel. > This option can be activated when architecture is 32-bit X86 and it results > in building X86-opitmised code for AES encryption. On the other hand, old > CRYPTO_AES option is disabled when architectire is 32-bit X86. The code for > X86-optimised AES module is located in "arch/i386/crypto" subdirectory and, > hence, is built only if the value of the ARCH variable is equal to "i386". No, UML build descend in that folder too, if needed. So your reasoning is wrong. > But for unknown reason, CRYPTO_AES_586 option is enabled also if building > UML for X86 architecture, and CRYPTO_AES option is unavailable in this > case. > There is no way to enable CRYPTO_AES option, but CRYPTO_AES_586 > option does nothing, How did you verify this? Hmm, wait a moment. I understand the patch, but the current behaviour was done in order to allow using CRYPTO_AES_586 with UML, and it worked when I checked last time; and indeed, it was compiled and linked in (I checked this only). > because there is no module for CRYPTO_AES_586 in > "arch/um" subdirectory, only in "arch/i386", which is irrelevant for > ARCH=um. No, it should be installed anyway. The module list is taken from the content of .tmp_versions. However, I'm going to test this too. -- Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!". Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894) http://www.user-mode-linux.org/~blaisorblade ___________________________________ Yahoo! Messenger: chiamate gratuite in tutto il mondo http://it.beta.messenger.yahoo.com |
From: Blaisorblade <bla...@ya...> - 2005-07-11 21:14:14
|
On Saturday 09 July 2005 12:50, Blaisorblade wrote: > On Friday 08 July 2005 14:28, Oleg Girko wrote: > > Hello! > > But for unknown reason, CRYPTO_AES_586 option is enabled also if building > > UML for X86 architecture, and CRYPTO_AES option is unavailable in this > > case. > > > > There is no way to enable CRYPTO_AES option, but CRYPTO_AES_586 > > option does nothing, > How did you verify this? > > because there is no module for CRYPTO_AES_586 in > > "arch/um" subdirectory, only in "arch/i386", which is irrelevant for > > ARCH=um. > No, it should be installed anyway. The module list is taken from the > content of .tmp_versions. > However, I'm going to test this too. I've verified that: *) it gets installed *) it can be loaded *) I've also compiled the crypto test module and it reports success when using aes. I'll consider this closed unless I've missed something, ok? If I'm wrong, explain me how to make it happen. Thanks for the report anyway. -- Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!". Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894) http://www.user-mode-linux.org/~blaisorblade ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it |
From: Oleg G. <ol...@in...> - 2005-07-12 07:03:42
|
On Sunday 10 July 2005 19:30, Blaisorblade wrote: > On Saturday 09 July 2005 12:50, Blaisorblade wrote: > > On Friday 08 July 2005 14:28, Oleg Girko wrote: > > > Hello! > > > > > > But for unknown reason, CRYPTO_AES_586 option is enabled also if > > > building UML for X86 architecture, and CRYPTO_AES option is unavailable > > > in this case. > > > > > > There is no way to enable CRYPTO_AES option, but CRYPTO_AES_586 > > > option does nothing, > > > > How did you verify this? > > > > > because there is no module for CRYPTO_AES_586 in > > > "arch/um" subdirectory, only in "arch/i386", which is irrelevant for > > > ARCH=um. > > > > No, it should be installed anyway. The module list is taken from the > > content of .tmp_versions. > > > > However, I'm going to test this too. > > I've verified that: > *) it gets installed > *) it can be loaded > *) I've also compiled the crypto test module and it reports success when > using aes. > > I'll consider this closed unless I've missed something, ok? If I'm wrong, > explain me how to make it happen. > Thanks for the report anyway. Sorry, this is a false alarm. I've got confused because after transition to 2.6.12 kernel, AES module was installed with different name ("aes-i586" instead of "aes"), and my scripts which build UML root filesystem missed it. -- Oleg Girko, http://www.infoserver.ru/~ol/ |