Bug 1106438

Summary: [abrt] WARNING: CPU: 1 PID: 13720 at lib/list_debug.c:59 __list_del_entry+0xa1/0xd0()
Product: [Fedora] Fedora Reporter: Maxim Galamay <maxim.galamay>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/85ab87619e010aba827c082820d374a7184e8e86
Whiteboard: abrt_hash:587811cd064e8db0fa747f572691eae560c06532
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-10 15:02:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg none

Description Maxim Galamay 2014-06-09 11:09:33 UTC 
Additional info:
reporter:       libreport-2.2.2
WARNING: CPU: 1 PID: 13720 at lib/list_debug.c:59 __list_del_entry+0xa1/0xd0()
list_del corruption. prev->next should be ffff880388e10c80, but was ffff8803ad2def00
Modules linked in: tcp_lp fuse ipt_MASQUERADE xt_CHECKSUM tun bnep bluetooth 6lowpan_iphc cfg80211 rfkill ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw x86_pkg_temp_thermal coretemp serio_raw iTCO_wdt iTCO_vendor_support ppdev kvm_intel kvm snd_hda_codec_realtek crct10dif_pclmul joydev crc32_pclmul crc32c_intel ghash_clmulni_intel snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd microcode soundcore i2c_i801 lpc_ich mfd_core
mei_me mei shpchp parport_pc parport binfmt_misc nfsd auth_rpcgss nfs_acl lockd sunrpc i915 i2c_algo_bit drm_kms_helper drm r8169 i2c_core mii video
CPU: 1 PID: 13720 Comm: chrome-sandbox Not tainted 3.14.5-200.fc20.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./H61M-S2PV REV 2.2, BIOS FB 02/25/2013
0000000000000000 0000000096c7b52a ffff88009047dbf0 ffffffff816efa42
ffff88009047dc38 ffff88009047dc28 ffffffff8108a1cd ffff880388e10c00
ffff880388e10c80 ffff8803357a2340 ffff880388e10c90 0000000000000000
Call Trace:
[<ffffffff816efa42>] dump_stack+0x45/0x56
[<ffffffff8108a1cd>] warn_slowpath_common+0x7d/0xa0
[<ffffffff8108a24c>] warn_slowpath_fmt+0x5c/0x80
[<ffffffff8136d8c1>] __list_del_entry+0xa1/0xd0
[<ffffffff811ff67c>] d_shrink_del+0x2c/0x80
[<ffffffff811ffd35>] dentry_lru_del+0x25/0x30
[<ffffffff8120069c>] dentry_kill+0x9c/0x210
[<ffffffff81200874>] dput+0x64/0x100
[<ffffffff811f47a5>] lookup_fast+0x285/0x2f0
[<ffffffff811f5391>] ? path_init+0xd1/0x400
[<ffffffff811f608a>] path_lookupat+0x16a/0x7a0
[<ffffffff8125c320>] ? tid_fd_revalidate+0x190/0x190
[<ffffffff81202aaa>] ? d_lookup+0x2a/0x50
[<ffffffff811cca65>] ? kmem_cache_alloc+0x35/0x1f0
[<ffffffff811f4f7f>] ? getname_flags+0x4f/0x1a0
[<ffffffff811f66eb>] filename_lookup+0x2b/0xc0
[<ffffffff811fa667>] user_path_at_empty+0x67/0xc0
[<ffffffff810c7f3c>] ? update_curr+0xcc/0x160
[<ffffffff810c3e26>] ? __dequeue_entity+0x26/0x40
[<ffffffff81013619>] ? __switch_to+0x169/0x4c0
[<ffffffff811eefbb>] SyS_readlinkat+0x5b/0x140
[<ffffffff816ffe29>] system_call_fastpath+0x16/0x1b
Comment 1 Maxim Galamay 2014-06-09 11:09:37 UTC 
Created attachment 904612 [details]
File: dmesg
Comment 2 Justin M. Forbes 2014-11-13 16:03:46 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.
Comment 3 Justin M. Forbes 2014-12-10 15:02:39 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.