Comment # 21 on bug 907692 from grant k

(In reply to Bernhard Wiedemann from comment #20)
> if you are curious, you can have a look at
> grep "sha1" /proc/kallsyms

thanks.

here,

egrep "sha1|sha256|sha512|aes" /proc/kallsyms
    ffffffff812ea4e0 t sha1_init
    ffffffff812ea520 t sha1_import
    ffffffff812ea590 t sha1_export
    ffffffff812ea600 T crypto_sha1_update
    ffffffff812ea6d0 t sha1_final
    ffffffff812ea850 t sha256_init
    ffffffff812ea8a0 t sha256_import
    ffffffff812ea910 t sha256_export
    ffffffff812ea980 t sha256_transform
    ffffffff812ec520 T crypto_sha256_update
    ffffffff812ec5c0 t sha256_final
    ffffffff812ec780 T crypto_aes_expand_key
    ffffffff812ecb70 T crypto_aes_set_key
    ffffffff812ecba0 t aes_encrypt
    ffffffff812ed990 t aes_decrypt
    ffffffff81ac2070 R __ksymtab_crypto_sha1_update
    ffffffff81ac2080 R __ksymtab_crypto_sha256_update
    ffffffff81ad09b0 R __ksymtab_crypto_aes_expand_key
    ffffffff81ad09c0 R __ksymtab_crypto_aes_set_key
    ffffffff81adb190 r __kcrctab_crypto_sha1_update
    ffffffff81adb198 r __kcrctab_crypto_sha256_update
    ffffffff81ae2630 r __kcrctab_crypto_aes_expand_key
    ffffffff81ae2638 r __kcrctab_crypto_aes_set_key
    ffffffff81af1c52 r __kstrtab_crypto_sha1_update
    ffffffff81af1c65 r __kstrtab_crypto_sha256_update
    ffffffff81af1c7a r __kstrtab_crypto_aes_set_key
    ffffffff81af1c8d r __kstrtab_crypto_aes_expand_key
    ffffffff81e98b80 d sha256_algs
    ffffffff81e98e60 d aes_alg
    ffffffff81f5444b t sha1_generic_mod_init
    ffffffff81f54457 t sha256_generic_mod_init
    ffffffff81f54468 t aes_init
    ffffffff8207ac58 t __initcall_sha1_generic_mod_init6
    ffffffff8207ac60 t __initcall_sha256_generic_mod_init6
    ffffffff8207ac68 t __initcall_aes_init6
    ffffffff8208d0b9 t sha1_generic_mod_fini
    ffffffff8208d0c5 t sha256_generic_mod_fini
    ffffffff8208d0d6 t aes_fini
    ffffffffa11f5720 t aes_encrypt  [aes_x86_64]
    ffffffffa11f5740 t aes_decrypt  [aes_x86_64]
    ffffffffa11f7000 d aes_alg      [aes_x86_64]
    ffffffffa11f574e t aes_fini     [aes_x86_64]
    ffffffffa11f6060 r __kstrtab_crypto_aes_decrypt_x86     [aes_x86_64]
    ffffffffa11f6050 r __kcrctab_crypto_aes_decrypt_x86     [aes_x86_64]
    ffffffffa11f6077 r __kstrtab_crypto_aes_encrypt_x86     [aes_x86_64]
    ffffffffa11f6058 r __kcrctab_crypto_aes_encrypt_x86     [aes_x86_64]
    ffffffffa11f6040 r __ksymtab_crypto_aes_encrypt_x86     [aes_x86_64]
    ffffffffa11f7120 d __this_module        [aes_x86_64]
    ffffffffa11f574e t cleanup_module       [aes_x86_64]
    ffffffffa11f4b80 t aes_dec_blk  [aes_x86_64]
    ffffffffa11f6030 r __ksymtab_crypto_aes_decrypt_x86     [aes_x86_64]
    ffffffffa11f4000 t aes_enc_blk  [aes_x86_64]
    ffffffffa11f5710 t crypto_aes_encrypt_x86       [aes_x86_64]
    ffffffffa11f5730 t crypto_aes_decrypt_x86       [aes_x86_64]
    ffffffffa12df9f0 t gss_krb5_aes_make_key        [rpcsec_gss_krb5]
    ffffffffa12de910 t gss_krb5_aes_encrypt [rpcsec_gss_krb5]
    ffffffffa12debf0 t gss_krb5_aes_decrypt [rpcsec_gss_krb5]
    ffffffffa0f88b90 t hmac_sha256.constprop.1      [bluetooth]
    ffffffffa0d55000 t sha512_init  [sha512_generic]
    ffffffffa0d55090 t sha384_init  [sha512_generic]
    ffffffffa0d55120 t sha512_transform     [sha512_generic]
    ffffffffa0d56060 r sha512_K     [sha512_generic]
    ffffffffa0d557d0 t sha512_final [sha512_generic]
    ffffffffa0d57000 d padding.28600        [sha512_generic]
    ffffffffa0d55920 t sha384_final [sha512_generic]
    ffffffffa0d57080 d sha512_algs  [sha512_generic]
    ffffffffa0d559a3 t sha512_generic_mod_fini      [sha512_generic]
    ffffffffa0d56048 r __kstrtab_crypto_sha512_update       [sha512_generic]
    ffffffffa0d56040 r __kcrctab_crypto_sha512_update       [sha512_generic]
    ffffffffa0d57360 d __this_module        [sha512_generic]
    ffffffffa0d559a3 t cleanup_module       [sha512_generic]
    ffffffffa0d556e0 T crypto_sha512_update [sha512_generic]
    ffffffffa0d56030 r __ksymtab_crypto_sha512_update       [sha512_generic]

which is not completely 'uniform' for the sha1/sha256/sha512 variants.

no idea yet, whether that's a problem or not.  also, no clear why they're
treated differently.

als no idea what effect that has on LUKS ... getting there.