Description of problem: This issue occured when I tried to upload some files to google drive with the builtin nautilus integration (file copy) Additional info: reporter: libreport-2.8.0 WARNING: CPU: 3 PID: 2950 at lib/list_debug.c:59 __list_del_entry+0x9e/0xc0 list_del corruption. prev->next should be ffff97684000b000, but was ffff976800000000 Modules linked in: binfmt_misc rfcomm ccm fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables bnep vfat fat arc4 iwlmvm mac80211 joydev intel_rapl uvcvideo hid_multitouch videobuf2_vmalloc intel_soc_dts_thermal iwlwifi intel_powerclamp coretemp acer_wmi videobuf2_memops iTCO_wdt videobuf2_v4l2 kvm_intel sparse_keymap iTCO_vendor_support videobuf2_core kvm cfg80211 videodev btusb btrtl btbcm btintel irqbypass intel_cstate media bluetooth snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic rfkill snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device dw_dmac int3406_thermal snd_pcm int3400_thermal processor_thermal_device int3403_thermal acpi_thermal_rel int340x_thermal_zone intel_soc_dts_iosf snd_timer mei_txe snd mei pwm_lpss_platform spi_pxa2xx_platform tpm_tis pwm_lpss i2c_designware_platform wmi lpc_ich soundcore i2c_designware_core tpm_tis_core i2c_i801 tpm i2c_smbus shpchp nfsd auth_rpcgss nfs_acl lockd grace sunrpc btrfs xor raid6_pq dm_crypt i915 crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel 8021q garp stp llc mrp i2c_algo_bit drm_kms_helper r8169 serio_raw drm mii fjes video i2c_hid CPU: 3 PID: 2950 Comm: Chrome_CacheThr Not tainted 4.9.13-201.fc25.x86_64 #1 Hardware name: Acer TravelMate B115-M/Roxy, BIOS V1.26 09/12/2014 ffffb5f9c368ba60 ffffffffa43f48ed ffffb5f9c368bab0 0000000000000000 ffffb5f9c368baa0 ffffffffa40a306b 0000003bb447ac70 ffff9768ba22b0c8 0000000000000000 ffff9768ba22b0c0 ffff97684000b000 0000000000000000 Call Trace: [<ffffffffa43f48ed>] dump_stack+0x63/0x86 [<ffffffffa40a306b>] __warn+0xcb/0xf0 [<ffffffffa40a30ef>] warn_slowpath_fmt+0x5f/0x80 [<ffffffffa43f944f>] ? radix_tree_node_alloc+0x4f/0x90 [<ffffffffa44143ee>] __list_del_entry+0x9e/0xc0 [<ffffffffa41f6047>] list_lru_del+0xd7/0x120 [<ffffffffa41c17db>] page_cache_tree_insert+0xfb/0x1e0 [<ffffffffa41c2d8c>] __add_to_page_cache_locked+0x14c/0x2a0 [<ffffffffa41c2f4e>] add_to_page_cache_lru+0x4e/0xe0 [<ffffffffa41c30d5>] pagecache_get_page+0xf5/0x2f0 [<ffffffffc0470beb>] prepare_pages+0x8b/0x260 [btrfs] [<ffffffffc0471556>] __btrfs_buffered_write+0x1f6/0x6f0 [btrfs] [<ffffffffa4372f23>] ? security_inode_need_killpriv+0x33/0x50 [<ffffffffc04752d0>] btrfs_file_write_iter+0x170/0x4b0 [btrfs] [<ffffffffa42597f5>] __vfs_write+0xe5/0x160 [<ffffffffa425a085>] vfs_write+0xb5/0x1a0 [<ffffffffa425b695>] SyS_pwrite64+0x95/0xb0 [<ffffffffa4003c17>] do_syscall_64+0x67/0x180 [<ffffffffa481dd2b>] entry_SYSCALL64_slow_path+0x25/0x25
Created attachment 1262376 [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 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. 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 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 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.