Re: Apparmor memory leak reports
On 08/30/2017 06:28 PM, Jakub Kicinski wrote: > Hi! > > I'm seeing a lot of kmemleak reports like this on 4.13.0-rc6: > yep, thanks for the report. I have seen this one and am still trying to chase it down. > unreferenced object 0x88045e62ab08 (size 1024): > comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4794.692s) > hex dump (first 32 bytes): > 0c 1b 30 6b 04 88 ff ff 0c 1b 30 6b 04 88 ff ff ..0k..0k > 18 ab 62 5e 04 88 ff ff 18 ab 62 5e 04 88 ff ff ..b^..b^ > backtrace: > [] kmemleak_alloc+0x28/0x50 > [] kmem_cache_alloc_trace+0x1e6/0x550 > [] aa_alloc_profile+0x5d/0x220 > [] unpack_profile+0x449/0x2530 > [] aa_unpack+0x447/0x151c > [] aa_replace_profiles+0x254/0x3f00 > [] policy_update+0x433/0x720 > [] profile_replace+0x13a/0x210 > [] __vfs_write+0xf9/0xdb0 > [] vfs_write+0x189/0x640 > [] SyS_write+0xf7/0x240 > [] entry_SYSCALL_64_fastpath+0x1c/0xb1 > [] 0x > > unreferenced object 0x88046b301b08 (size 32): > comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4797.788s) > hex dump (first 32 bytes): > 01 00 00 00 2f 73 62 69 6e 2f 64 68 63 6c 69 65 /sbin/dhclie > 6e 74 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 nt.. > backtrace: > [] kmemleak_alloc+0x28/0x50 > [] __kmalloc+0x204/0x600 > [] aa_str_alloc+0x5e/0x120 > [] aa_policy_init+0x2a2/0x370 > [] aa_alloc_profile+0x88/0x220 > [] unpack_profile+0x449/0x2530 > [] aa_unpack+0x447/0x151c > [] aa_replace_profiles+0x254/0x3f00 > [] policy_update+0x433/0x720 > [] profile_replace+0x13a/0x210 > [] __vfs_write+0xf9/0xdb0 > [] vfs_write+0x189/0x640 > [] SyS_write+0xf7/0x240 > [] entry_SYSCALL_64_fastpath+0x1c/0xb1 > [] 0x > > unreferenced object 0x8803fdc50008 (size 8192): > comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4827.224s) > hex dump (first 32 bytes): > 06 00 04 00 00 00 00 00 b1 04 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > backtrace: > [] kmemleak_alloc+0x28/0x50 > [] __kmalloc_node+0x385/0x670 > [] kvmalloc_node+0x4b/0x80 > [] aa_dfa_unpack+0x41d/0x1de0 > [] unpack_dfa+0x14f/0x3d0 > [] unpack_profile+0xba9/0x2530 > [] aa_unpack+0x447/0x151c > [] aa_replace_profiles+0x254/0x3f00 > [] policy_update+0x433/0x720 > [] profile_replace+0x13a/0x210 > [] __vfs_write+0xf9/0xdb0 > [] vfs_write+0x189/0x640 > [] SyS_write+0xf7/0x240 > [] entry_SYSCALL_64_fastpath+0x1c/0xb1 > [] 0x > > I'm running Ubuntu 14.04 user space on that machine. >
Re: Apparmor memory leak reports
On 08/30/2017 06:28 PM, Jakub Kicinski wrote: > Hi! > > I'm seeing a lot of kmemleak reports like this on 4.13.0-rc6: > yep, thanks for the report. I have seen this one and am still trying to chase it down. > unreferenced object 0x88045e62ab08 (size 1024): > comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4794.692s) > hex dump (first 32 bytes): > 0c 1b 30 6b 04 88 ff ff 0c 1b 30 6b 04 88 ff ff ..0k..0k > 18 ab 62 5e 04 88 ff ff 18 ab 62 5e 04 88 ff ff ..b^..b^ > backtrace: > [] kmemleak_alloc+0x28/0x50 > [] kmem_cache_alloc_trace+0x1e6/0x550 > [] aa_alloc_profile+0x5d/0x220 > [] unpack_profile+0x449/0x2530 > [] aa_unpack+0x447/0x151c > [] aa_replace_profiles+0x254/0x3f00 > [] policy_update+0x433/0x720 > [] profile_replace+0x13a/0x210 > [] __vfs_write+0xf9/0xdb0 > [] vfs_write+0x189/0x640 > [] SyS_write+0xf7/0x240 > [] entry_SYSCALL_64_fastpath+0x1c/0xb1 > [] 0x > > unreferenced object 0x88046b301b08 (size 32): > comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4797.788s) > hex dump (first 32 bytes): > 01 00 00 00 2f 73 62 69 6e 2f 64 68 63 6c 69 65 /sbin/dhclie > 6e 74 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 nt.. > backtrace: > [] kmemleak_alloc+0x28/0x50 > [] __kmalloc+0x204/0x600 > [] aa_str_alloc+0x5e/0x120 > [] aa_policy_init+0x2a2/0x370 > [] aa_alloc_profile+0x88/0x220 > [] unpack_profile+0x449/0x2530 > [] aa_unpack+0x447/0x151c > [] aa_replace_profiles+0x254/0x3f00 > [] policy_update+0x433/0x720 > [] profile_replace+0x13a/0x210 > [] __vfs_write+0xf9/0xdb0 > [] vfs_write+0x189/0x640 > [] SyS_write+0xf7/0x240 > [] entry_SYSCALL_64_fastpath+0x1c/0xb1 > [] 0x > > unreferenced object 0x8803fdc50008 (size 8192): > comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4827.224s) > hex dump (first 32 bytes): > 06 00 04 00 00 00 00 00 b1 04 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > backtrace: > [] kmemleak_alloc+0x28/0x50 > [] __kmalloc_node+0x385/0x670 > [] kvmalloc_node+0x4b/0x80 > [] aa_dfa_unpack+0x41d/0x1de0 > [] unpack_dfa+0x14f/0x3d0 > [] unpack_profile+0xba9/0x2530 > [] aa_unpack+0x447/0x151c > [] aa_replace_profiles+0x254/0x3f00 > [] policy_update+0x433/0x720 > [] profile_replace+0x13a/0x210 > [] __vfs_write+0xf9/0xdb0 > [] vfs_write+0x189/0x640 > [] SyS_write+0xf7/0x240 > [] entry_SYSCALL_64_fastpath+0x1c/0xb1 > [] 0x > > I'm running Ubuntu 14.04 user space on that machine. >
Apparmor memory leak reports
Hi! I'm seeing a lot of kmemleak reports like this on 4.13.0-rc6: unreferenced object 0x88045e62ab08 (size 1024): comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4794.692s) hex dump (first 32 bytes): 0c 1b 30 6b 04 88 ff ff 0c 1b 30 6b 04 88 ff ff ..0k..0k 18 ab 62 5e 04 88 ff ff 18 ab 62 5e 04 88 ff ff ..b^..b^ backtrace: [] kmemleak_alloc+0x28/0x50 [] kmem_cache_alloc_trace+0x1e6/0x550 [] aa_alloc_profile+0x5d/0x220 [] unpack_profile+0x449/0x2530 [] aa_unpack+0x447/0x151c [] aa_replace_profiles+0x254/0x3f00 [] policy_update+0x433/0x720 [] profile_replace+0x13a/0x210 [] __vfs_write+0xf9/0xdb0 [] vfs_write+0x189/0x640 [] SyS_write+0xf7/0x240 [] entry_SYSCALL_64_fastpath+0x1c/0xb1 [] 0x unreferenced object 0x88046b301b08 (size 32): comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4797.788s) hex dump (first 32 bytes): 01 00 00 00 2f 73 62 69 6e 2f 64 68 63 6c 69 65 /sbin/dhclie 6e 74 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 nt.. backtrace: [] kmemleak_alloc+0x28/0x50 [] __kmalloc+0x204/0x600 [] aa_str_alloc+0x5e/0x120 [] aa_policy_init+0x2a2/0x370 [] aa_alloc_profile+0x88/0x220 [] unpack_profile+0x449/0x2530 [] aa_unpack+0x447/0x151c [] aa_replace_profiles+0x254/0x3f00 [] policy_update+0x433/0x720 [] profile_replace+0x13a/0x210 [] __vfs_write+0xf9/0xdb0 [] vfs_write+0x189/0x640 [] SyS_write+0xf7/0x240 [] entry_SYSCALL_64_fastpath+0x1c/0xb1 [] 0x unreferenced object 0x8803fdc50008 (size 8192): comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4827.224s) hex dump (first 32 bytes): 06 00 04 00 00 00 00 00 b1 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [] kmemleak_alloc+0x28/0x50 [] __kmalloc_node+0x385/0x670 [] kvmalloc_node+0x4b/0x80 [] aa_dfa_unpack+0x41d/0x1de0 [] unpack_dfa+0x14f/0x3d0 [] unpack_profile+0xba9/0x2530 [] aa_unpack+0x447/0x151c [] aa_replace_profiles+0x254/0x3f00 [] policy_update+0x433/0x720 [] profile_replace+0x13a/0x210 [] __vfs_write+0xf9/0xdb0 [] vfs_write+0x189/0x640 [] SyS_write+0xf7/0x240 [] entry_SYSCALL_64_fastpath+0x1c/0xb1 [] 0x I'm running Ubuntu 14.04 user space on that machine.
Apparmor memory leak reports
Hi! I'm seeing a lot of kmemleak reports like this on 4.13.0-rc6: unreferenced object 0x88045e62ab08 (size 1024): comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4794.692s) hex dump (first 32 bytes): 0c 1b 30 6b 04 88 ff ff 0c 1b 30 6b 04 88 ff ff ..0k..0k 18 ab 62 5e 04 88 ff ff 18 ab 62 5e 04 88 ff ff ..b^..b^ backtrace: [] kmemleak_alloc+0x28/0x50 [] kmem_cache_alloc_trace+0x1e6/0x550 [] aa_alloc_profile+0x5d/0x220 [] unpack_profile+0x449/0x2530 [] aa_unpack+0x447/0x151c [] aa_replace_profiles+0x254/0x3f00 [] policy_update+0x433/0x720 [] profile_replace+0x13a/0x210 [] __vfs_write+0xf9/0xdb0 [] vfs_write+0x189/0x640 [] SyS_write+0xf7/0x240 [] entry_SYSCALL_64_fastpath+0x1c/0xb1 [] 0x unreferenced object 0x88046b301b08 (size 32): comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4797.788s) hex dump (first 32 bytes): 01 00 00 00 2f 73 62 69 6e 2f 64 68 63 6c 69 65 /sbin/dhclie 6e 74 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 nt.. backtrace: [] kmemleak_alloc+0x28/0x50 [] __kmalloc+0x204/0x600 [] aa_str_alloc+0x5e/0x120 [] aa_policy_init+0x2a2/0x370 [] aa_alloc_profile+0x88/0x220 [] unpack_profile+0x449/0x2530 [] aa_unpack+0x447/0x151c [] aa_replace_profiles+0x254/0x3f00 [] policy_update+0x433/0x720 [] profile_replace+0x13a/0x210 [] __vfs_write+0xf9/0xdb0 [] vfs_write+0x189/0x640 [] SyS_write+0xf7/0x240 [] entry_SYSCALL_64_fastpath+0x1c/0xb1 [] 0x unreferenced object 0x8803fdc50008 (size 8192): comm "apparmor_parser", pid 802, jiffies 4294913386 (age 4827.224s) hex dump (first 32 bytes): 06 00 04 00 00 00 00 00 b1 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [] kmemleak_alloc+0x28/0x50 [] __kmalloc_node+0x385/0x670 [] kvmalloc_node+0x4b/0x80 [] aa_dfa_unpack+0x41d/0x1de0 [] unpack_dfa+0x14f/0x3d0 [] unpack_profile+0xba9/0x2530 [] aa_unpack+0x447/0x151c [] aa_replace_profiles+0x254/0x3f00 [] policy_update+0x433/0x720 [] profile_replace+0x13a/0x210 [] __vfs_write+0xf9/0xdb0 [] vfs_write+0x189/0x640 [] SyS_write+0xf7/0x240 [] entry_SYSCALL_64_fastpath+0x1c/0xb1 [] 0x I'm running Ubuntu 14.04 user space on that machine.
