From: Andrew W Elble <aweits@rit.edu>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: <linux-nfs@vger.kernel.org>
Subject: Re: list_del corruption / unhash_ol_stateid()
Date: Tue, 28 Jul 2015 11:01:59 -0400 [thread overview]
Message-ID: <m2wpxktjfc.fsf@discipline.rit.edu> (raw)
In-Reply-To: <20150728090206.1331e476@tlielax.poochiereds.net> (Jeff Layton's message of "Tue, 28 Jul 2015 09:02:06 -0400")
Still trying to develop some kind of test to reliably trigger this.
> My guess is that that may be collateral damage from the double
> unhashing of the stateid. It certainly doesn't look directly related to
> anything in knfsd -- it's a crash down deep in the POSIX ACL code,
> apparently.
Thinking that it's collateral - here's the backtrace from a similar
event.
(was preceded by both the WARN_ON_ONCE() and the list_del corruption messages)
running 3.18.9:
[846121.007040] general protection fault: 0000 [#1] SMP
[846121.013461] Modules linked in: nfnetlink_queue nfnetlink_log nfnetlink bluetooth gfs2 dlm sctp sg dm_service_time cts iscsi_tcp libiscsi_tcp libiscsi rpcsec_gss_
krb5 nfsv4 dns_resolver nfs scsi_transport_iscsi fscache 8021q nf_log_ipv4 nf_log_common garp xt_LOG mrp stp llc bonding xt_conntrack cfg80211 iptable_filter nf_conn
track_ftp nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack rfkill ip_tables dm_multipath x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32
c_intel ghash_clmulni_intel mei_me mei aesni_intel lrw gf128mul glue_helper nfsd ablk_helper sb_edac iTCO_wdt ipmi_devintf pcspkr acpi_power_meter iTCO_vendor_suppor
t dcdbas ipmi_si edac_core cryptd lpc_ich mfd_core wmi shpchp ipmi_msghandler acpi_pad auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc xfs sr_mod cdrom mgag200 sy
scopyarea sd_mod sysfillrect sysimgblt i2c_algo_bit ixgbe drm_kms_helper mdio tg3 ttm ahci dca drm libahci ptp libata megaraid_sas i2c_core pps_core dm_mirror dm_region_hash dm_log dm_mod
[846121.119250] CPU: 8 PID: 46216 Comm: nfsd Tainted: G W 3.18.9 #1
[846121.127982] Hardware name: Dell Inc. PowerEdge R720/0X3D66, BIOS 2.4.3 07/09/2014
[846121.137268] task: ffff881ecd854330 ti: ffff881ecebf4000 task.ti: ffff881ecebf4000
[846121.146540] RIP: 0010:[<ffffffff811c7595>] [<ffffffff811c7595>] kmem_cache_alloc+0x65/0x140
[846121.156839] RSP: 0018:ffff881ecebf7c28 EFLAGS: 00010286
[846121.163626] RAX: 0000000000000000 RBX: ffff8811bd0cf3e0 RCX: 0000000000003a0c
[846121.172438] RDX: 0000000000003a0b RSI: 00000000000080d0 RDI: ffff881fff489000
[846121.181267] RBP: ffff881ecebf7c68 R08: 0000000000016ae0 R09: 00000000b9acddf8
[846121.190049] R10: ffff883fe43df000 R11: ffff881856038437 R12: ff88185603834800
[846121.198826] R13: 00000000000080d0 R14: ffff881fff489000 R15: ffffffffa0517b79
[846121.207623] FS: 0000000000000000(0000) GS:ffff881fffa80000(0000) knlGS:0000000000000000
[846121.217475] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[846121.224720] CR2: 00000000006e8360 CR3: 00000000019bc000 CR4: 00000000001407e0
[846121.233525] Stack:
[846121.236601] 0000000000000014 ffff881fff403c00 ffff881ecebf7c88 ffff8811bd0cf3e0
[846121.245723] ffff883fe43df000 ffff8835d38afa80 0000000000000000 ffff881fff489000
[846121.254854] ffff881ecebf7ca8 ffffffffa0517b79 0000000000000000 ffff8811bd0cf3e0
[846121.263984] Call Trace:
[846121.267559] [<ffffffffa0517b79>] nfs4_alloc_stid+0x29/0xc0 [nfsd]
[846121.275355] [<ffffffffa051fcf8>] nfsd4_lock+0x6f8/0xda0 [nfsd]
[846121.282870] [<ffffffffa050cf07>] nfsd4_proc_compound+0x4d7/0x7f0 [nfsd]
[846121.291191] [<ffffffffa04f8e43>] nfsd_dispatch+0xc3/0x210 [nfsd]
[846121.298869] [<ffffffffa01c8e02>] ? svc_tcp_adjust_wspace+0x12/0x30 [sunrpc]
[846121.307590] [<ffffffffa01c7d23>] svc_process_common+0x453/0x6f0 [sunrpc]
[846121.316018] [<ffffffffa01c80c7>] svc_process+0x107/0x170 [sunrpc]
[846121.323764] [<ffffffffa04f87c7>] nfsd+0xf7/0x160 [nfsd]
[846121.330541] [<ffffffffa04f86d0>] ? nfsd_destroy+0x80/0x80 [nfsd]
[846121.338226] [<ffffffff81093861>] kthread+0xe1/0x100
[846121.344624] [<ffffffff81093780>] ? kthread_create_on_node+0x1b0/0x1b0
[846121.352776] [<ffffffff816912fc>] ret_from_fork+0x7c/0xb0
[846121.359661] [<ffffffff81093780>] ? kthread_create_on_node+0x1b0/0x1b0
[846121.367961] Code: cc 00 00 49 8b 50 08 4d 8b 20 49 8b 40 10 4d 85 e4 0f 84 a7 00 00 00 48 85 c0 0f 84 9e 00 00 00 49 63 46 20 48 8d 4a 01 4d 8b 06 <49> 8b 1c 04 4c 89 e0 65 49 0f c7 08 0f 94 c0 84 c0 74 b9 49 63
[846121.391248] RIP [<ffffffff811c7595>] kmem_cache_alloc+0x65/0x140
[846121.398936] RSP <ffff881ecebf7c28>
--
Andrew W. Elble
aweits@discipline.rit.edu
Infrastructure Engineer, Communications Technical Lead
Rochester Institute of Technology
PGP: BFAD 8461 4CCF DC95 DA2C B0EB 965B 082E 863E C912
next prev parent reply other threads:[~2015-07-28 15:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 15:13 list_del corruption / unhash_ol_stateid() Andrew W Elble
2015-07-27 18:06 ` Andrew W Elble
2015-07-27 20:40 ` J. Bruce Fields
2015-07-27 21:03 ` Andrew W Elble
2015-07-28 13:02 ` Jeff Layton
2015-07-28 15:01 ` Andrew W Elble [this message]
2015-07-28 15:49 ` Jeff Layton
2015-07-28 21:04 ` J. Bruce Fields
2015-07-29 15:17 ` Andrew W Elble
2015-07-29 19:52 ` Andrew W Elble
2015-07-30 11:11 ` Andrew W Elble
2015-07-30 12:57 ` Jeff Layton
2015-08-04 20:18 ` Andrew W Elble
2015-08-05 15:11 ` Jeff Layton
2015-08-05 16:33 ` Andrew W Elble
2015-08-05 17:12 ` Jeff Layton
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=m2wpxktjfc.fsf@discipline.rit.edu \
--to=aweits@rit.edu \
--cc=jlayton@poochiereds.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.