From: William Dauchy <william@gandi.net>
To: Linux NFS mailing list <linux-nfs@vger.kernel.org>,
netdev@vger.kernel.org
Subject: kmemleak report with nfs3/4 activity on v4.1.x
Date: Wed, 25 Nov 2015 13:57:23 +0100 [thread overview]
Message-ID: <20151125125723.GY21147@gandi.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
reply other threads:[~2015-11-25 12:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151125125723.GY21147@gandi.net \
--to=william@gandi.net \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox