Bug 983682

Summary: [abrt] WARNING: at lib/list_debug.c:53 __list_del_entry+0x63/0xd0()
Product: [Fedora] Fedora Reporter: Matt Ellison <matthew.ellison>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, matthew.ellison, nioakeim
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:4e1122b95ae3783bed169cb5dcfae03382f7f5e8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-08 17:02:09 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 Matt Ellison 2013-07-11 17:21:51 UTC 
Description of problem:
I connected my iPhone 5 to the PC via USB. I can reproduce this problem consistently. 

Additional info:
reporter:       libreport-2.1.5
WARNING: at lib/list_debug.c:53 __list_del_entry+0x63/0xd0()
Hardware name: HP Compaq 8200 Elite CMT PC
list_del corruption, ffff880127224200->next is LIST_POISON1 (dead000000100100)
Modules linked in: nls_utf8 cifs dns_resolver fscache nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6table_nat nf_nat_ipv6 ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack bnep bluetooth ebtable_filter ebtables ip6table_filter ip6_tables snd_hda_codec_hdmi snd_hda_codec_realtek mperf coretemp snd_hda_intel snd_hda_codec kvm_intel e1000e iTCO_wdt iTCO_vendor_support kvm snd_hwdep snd_seq snd_seq_device snd_pcm crc32_pclmul crc32c_intel ppdev hp_wmi sparse_keymap ghash_clmulni_intel tpm_tis rfkill parport_pc tpm_infineon snd_page_alloc snd_timer snd ptp mei lpc_ich parport tpm i2c_i801 pps_core soundcore mfd_core wmi tpm_bios microcode uinput i915 video i2c_algo_bit drm_kms_helper drm i2c_core
Pid: 947, comm: mount.cifs Not tainted 3.9.9-301.fc19.x86_64 #1
Call Trace:
 [<ffffffff81306d00>] ? __list_add+0x30/0xc0
 [<ffffffff8105cc56>] warn_slowpath_common+0x66/0x80
 [<ffffffff8105ccbc>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffff81085ad8>] ? __blocking_notifier_call_chain+0x58/0x70
 [<ffffffff81306df3>] __list_del_entry+0x63/0xd0
 [<ffffffff81306e6d>] list_del+0xd/0x30
 [<ffffffff812adb51>] crypto_larval_kill+0x21/0x60
 [<ffffffff812adfbb>] crypto_alg_mod_lookup+0x8b/0xb0
 [<ffffffff812ae20d>] crypto_alloc_tfm+0x5d/0xf0
 [<ffffffff812b57a9>] crypto_alloc_shash+0x19/0x20
 [<ffffffffa04ab375>] cifs_crypto_shash_allocate+0x65/0x200 [cifs]
 [<ffffffffa0495d66>] cifs_mount+0x3a6/0xb10 [cifs]
 [<ffffffffa0484f49>] cifs_do_mount+0xa9/0x4d0 [cifs]
 [<ffffffff8119d859>] mount_fs+0x39/0x1b0
 [<ffffffff811b6a0f>] vfs_kern_mount+0x5f/0xf0
 [<ffffffff811b8cde>] do_mount+0x23e/0xa20
 [<ffffffff811b8926>] ? copy_mount_options+0x36/0x170
 [<ffffffff811b9543>] sys_mount+0x83/0xc0
 [<ffffffff8164f319>] system_call_fastpath+0x16/0x1b

Potential duplicate: bug 869569
Comment 1 Matt Ellison 2013-07-11 17:21:59 UTC 
Created attachment 772336 [details]
File: dmesg
Comment 2 Matt Ellison 2013-07-11 17:24:56 UTC 
Please let me know if you need more information.
Comment 3 Michal Jaegermann 2013-09-07 01:16:14 UTC 
See https://lkml.org/lkml/2013/9/6/454 "race condition in crypto larval handling"
Comment 4 Josh Boyer 2013-09-18 20:33:24 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 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.
Comment 5 Josh Boyer 2013-10-08 17:02:09 UTC 
This was fixed in a recent update.