Well, I'm not sure. But after further analyse, I think that crypto creates some data on boot which are destroyed only when device is powering off, so it may be false positive. 2013/5/30 Matthias Brugger <matthias.bgg@gmail.com>
El 28/05/2013 19:16, "Michał Akaanonim" <michak.ny@gmail.com> va escriure:
Hi, I'm developing custom kernel for my Samsung Galaxy Ace 2 phone. First, I'd like to check if there are any bugs, so I built kernel with
kmemleak enabled and I get 10 entries, for example:
unreferenced object 0xce2a2000 (size 8192): comm "vold", pid 1855, jiffies 4294942835 (age 1394.240s) hex dump (first 32 bytes): 00 00 00 00 24 7e 50 c0 d0 7d 50 c0 7c 7d 50 c0 ....$~P..}P.|}P. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<c03f4a00>] create_object+0x10c/0x24c [<c08e99f0>] kmemleak_alloc+0x6c/0xd0 [<c03f1a54>] __kmalloc+0x178/0x27c [<c0507988>] __crypto_alloc_tfm+0x4c/0x140 [<c05086b8>] crypto_spawn_tfm+0x78/0xcc [<c0511dc0>] crypto_cbc_init_tfm+0x2c/0x44 [<c05079dc>] __crypto_alloc_tfm+0xa0/0x140 [<c05086b8>] crypto_spawn_tfm+0x78/0xcc [<c050b968>] skcipher_geniv_init+0x2c/0x54 [<c050cd68>] eseqiv_init+0x50/0x54 [<c05079dc>] __crypto_alloc_tfm+0xa0/0x140 [<c050aee0>] crypto_alloc_ablkcipher+0x68/0xa8 [<c06b82b0>] crypt_ctr+0x294/0x8a0 [<c06b08c8>] dm_table_add_target+0xf8/0x260 [<c06b3ffc>] table_load+0x114/0x2c4 [<c06b37d4>] dm_ctl_ioctl+0x1d0/0x2cc
I noticed that in 6 of 10 entries there are dm_ctl_ioctl, table_load and
dm_table_add_target functions. So I think something is wrong with MD driver but I compared source of this driver with other find on net and there aren't any differences.
Source code of my kernel can be found here: https://github.com/hckk/GT-I8160_Kernel
Thanks for any help.
Could it be false positives?
Regards, Matthias
Greetings, Michal.
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies