Additional info: reporter: libreport-2.2.3 general protection fault: 0000 [#1] SMP Modules linked in: uas usb_storage fuse ccm bnep 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 vfat fat arc4 snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_seq iwlmvm snd_seq_device mac80211 nfsd auth_rpcgss nfs_acl lockd sunrpc snd_pcm rtsx_pci_sdmmc ideapad_laptop rtsx_pci_ms mmc_core memstick x86_pkg_temp_thermal snd_timer snd iwlwifi rtsx_pci btusb iTCO_wdt iTCO_vendor_support bluetooth cfg80211 shpchp coretemp kvm soundcore crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sparse_keymap rfkill uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core microcode videodev joydev media hid_multitouch serio_raw i2c_i801 lpc_ich mei_me mfd_core mei i915 i2c_algo_bit drm_kms_helper drm r8169 i2c_core mii video CPU: 5 PID: 47 Comm: kdevtmpfs Not tainted 3.15.7-200.fc20.x86_64 #1 Hardware name: LENOVO 20349/Lenovo Y50-70 Touch, BIOS 9ECN21WW(V1.04) 03/29/2014 task: ffff880448b689e0 ti: ffff880448b90000 task.ti: ffff880448b90000 RIP: 0010:[<ffffffff8134e2cc>] [<ffffffff8134e2cc>] idr_find_slowpath+0x4c/0x80 RSP: 0018:ffff880448b93b98 EFLAGS: 00010206 RAX: 0065000000640000 RBX: ffff880445faff00 RCX: 0000000001980000 RDX: 0000000000000015 RSI: 0000000000000011 RDI: 000000007fffffff RBP: ffff880448b93b98 R08: ffff8804451c31e0 R09: ffff88044e803b00 R10: ffffffff8122a64f R11: 0000000000000400 R12: ffff8804441ce000 R13: ffff8804441ce070 R14: ffff880445efa278 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff88045f340000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fce63e7f740 CR3: 0000000001c11000 CR4: 00000000001407e0 Stack: ffff880448b93bb0 ffffffff8122af0d ffff880445faff00 ffff880448b93c08 ffffffff8122af88 0000000000008000 ffff880448b93c08 ffffffff8122a696 0000000000000000 ffff8804441ce000 ffff880445faff00 ffff8804441ce000 Call Trace: [<ffffffff8122af0d>] inotify_idr_find_locked+0x3d/0x80 [<ffffffff8122af88>] inotify_remove_from_idr+0x38/0x1f0 [<ffffffff8122a696>] ? inotify_handle_event+0xb6/0x180 [<ffffffff8122b191>] inotify_ignored_and_remove_idr+0x51/0x70 [<ffffffff8122a77e>] inotify_freeing_mark+0xe/0x10 [<ffffffff81229227>] fsnotify_destroy_mark_locked+0xe7/0x150 [<ffffffff812292bb>] fsnotify_destroy_mark+0x2b/0x40 [<ffffffff81228b5c>] fsnotify_clear_marks_by_inode+0xec/0x130 [<ffffffff81227dde>] __fsnotify_inode_delete+0xe/0x10 [<ffffffff811fdc53>] d_delete+0x183/0x190 [<ffffffff811f42bd>] vfs_unlink+0x13d/0x150 [<ffffffff814637ec>] handle_remove+0x18c/0x330 [<ffffffff81463cb8>] devtmpfsd+0x108/0x170 [<ffffffff81463bb0>] ? handle_create.isra.2+0x220/0x220 [<ffffffff810ac528>] kthread+0xd8/0xf0 [<ffffffff810ac450>] ? insert_kthread_work+0x40/0x40 [<ffffffff816ff8bc>] ret_from_fork+0x7c/0xb0 [<ffffffff810ac450>] ? insert_kthread_work+0x40/0x40 Code: 8d 14 d5 08 00 00 00 83 fa 1f 0f 4e ca d3 e7 83 ef 01 39 fe 7f 40 83 fa 00 74 41 7e 37 8d 4a f8 eb 1d 0f 1f 44 00 00 85 c9 7e 29 <8b> b8 2c 08 00 00 83 e9 08 8d 14 fd 00 00 00 00 39 d1 75 1b 89 RIP [<ffffffff8134e2cc>] idr_find_slowpath+0x4c/0x80
Created attachment 928024 [details] File: dmesg
*********** 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.
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.