From: Anthony Messina <amessina@messinet.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Kernel warning: net/sunrpc/clnt.c:2161 call_decode+0x269/0x8a0 [sunrpc]()
Date: Tue, 10 Mar 2015 20:29:49 -0500 [thread overview]
Message-ID: <2905412.OH09VlPNMp@linux-ws1.messinet.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2676 bytes --]
While this may be unrelated, it is one of the errors that seems to occur
around the same time as the issues detailed in "soft lockup in the laundromat"
[1] and "NMI/soft lockup in nfs_delegation_need_return()" [2]. This is on an
NFSv4.2/KRB5 client using kernel-3.18.9-200.fc21.x86_64 with the patch from
thread "[PATCH] NFS: fix clp->cl_revoked list deletion causing softlock in
nfsd" applied at the Fedora kernel packaging level.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6545 at net/sunrpc/clnt.c:2161 call_decode+0x269/0x8a0
[sunrpc]()
Modules linked in: dm_crypt bnep bluetooth rfkill veth cts rpcsec_gss_krb5
nfsv4 dns_resolver nfs fscache ip6t_rpfilter ip6t_REJECT nf_reject_ipv6
xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables
ip6table_na
shpchp i2c_i801 crc32c_intel serio_raw dcdbas ghash_clmulni_intel nfsd
auth_rpcgss nfs_acl lockd grace sunrpc uas usb_storage nouveau video mxm_wmi
broadcom wmi i2c_algo_bit drm_kms_helper ttm drm tg3 ptp pps_core
CPU: 0 PID: 6545 Comm: kworker/0:1 Not tainted 3.18.9-200.fc21.x86_64 #1
Hardware name: Dell Inc. XPS 8300 /0Y2MRG, BIOS A06 10/17/2011
Workqueue: rpciod rpc_async_schedule [sunrpc]
0000000000000000 0000000089b51bad ffff88015d23fcc8 ffffffff8175b71c
0000000000000000 0000000000000000 ffff88015d23fd08 ffffffff81098eb1
0000000000000000 ffff8801572f1218 ffff880017369000 ffff8802060f1000
Call Trace:
[<ffffffff8175b71c>] dump_stack+0x46/0x58
[<ffffffff81098eb1>] warn_slowpath_common+0x81/0xa0
[<ffffffffa0641810>] ? nfs4_xdr_dec_readdir+0xf0/0xf0 [nfsv4]
[<ffffffff81098fca>] warn_slowpath_null+0x1a/0x20
[<ffffffffa02810a9>] call_decode+0x269/0x8a0 [sunrpc]
[<ffffffffa0280e40>] ? call_refreshresult+0x150/0x150 [sunrpc]
[<ffffffffa0280e40>] ? call_refreshresult+0x150/0x150 [sunrpc]
[<ffffffffa028b6e4>] __rpc_execute+0x94/0x450 [sunrpc]
[<ffffffffa028bab5>] rpc_async_schedule+0x15/0x20 [sunrpc]
[<ffffffff810b1a6d>] process_one_work+0x14d/0x3f0
[<ffffffff810b23c3>] worker_thread+0x53/0x470
[<ffffffff810b2370>] ? rescuer_thread+0x290/0x290
[<ffffffff810b75b8>] kthread+0xd8/0xf0
[<ffffffff810b74e0>] ? kthread_create_on_node+0x1b0/0x1b0
[<ffffffff8176207c>] ret_from_fork+0x7c/0xb0
[<ffffffff810b74e0>] ? kthread_create_on_node+0x1b0/0x1b0
---[ end trace aa1a2fd825fce8b1 ]---
[1] http://www.spinics.net/lists/linux-nfs/msg49735.html
[2] http://www.spinics.net/lists/linux-nfs/msg47059.html
[3] http://www.spinics.net/lists/linux-nfs/msg49798.html
--
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2015-03-11 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 1:29 Anthony Messina [this message]
2015-03-17 3:03 ` Kernel warning: net/sunrpc/clnt.c:2161 call_decode+0x269/0x8a0 [sunrpc]() Anthony Messina
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=2905412.OH09VlPNMp@linux-ws1.messinet.com \
--to=amessina@messinet.com \
--cc=linux-nfs@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