Hello, I'm seeing some kmemleak reports while I'm using nfsv3/4 as a client on linux v4.1.13; unreferenced object 0xffff880c22a97ad0 (size 16): comm "softirq", pid 0, jiffies 4294896089 (age 43927.436s) hex dump (first 16 bytes): 00 00 00 00 00 00 00 00 00 45 1e 24 06 88 ff ff .........E.$.... backtrace: [<ffffffff811255fd>] create_object+0x152/0x280 [<ffffffff81529c04>] kmemleak_alloc+0x20/0x42 [<ffffffff811136dd>] slab_post_alloc_hook+0x2a/0x45 [<ffffffff81115c48>] kmem_cache_alloc+0xbc/0xd1 [<ffffffff81254cef>] gr_update_task_in_ip_table+0x2e/0xc3 [<ffffffff814701bc>] __inet_hash_connect+0x241/0x30e [<ffffffff814702b8>] inet_hash_connect+0x2f/0x3a [<ffffffff81484c41>] tcp_v4_connect+0x31f/0x470 [<ffffffff81499a2b>] __inet_stream_connect+0x9f/0x2c3 [<ffffffff81499c80>] inet_stream_connect+0x31/0x4d [<ffffffff8140d870>] kernel_connect+0x18/0x20 [<ffffffff81503cb6>] xs_tcp_setup_socket+0x25c/0x37f [<ffffffff810724c3>] process_one_work+0x1d0/0x30f [<ffffffff81072822>] worker_thread+0x1f0/0x2aa [<ffffffff81077cdc>] kthread+0xcd/0xd5 [<ffffffff8153443e>] ret_from_fork+0x3e/0x70 What can I do to help resolve this issue? Thanks, -- William
Attachment:
signature.asc
Description: PGP signature
