Description of problem: running dd ? Additional info: reporter: libreport-2.2.2 WARNING: CPU: 0 PID: 5257 at fs/fs-writeback.c:1197 __mark_inode_dirty+0x26d/0x270() bdi-block not registered Modules linked in: nls_utf8 isofs vfat fat rfcomm ccm ip6t_rpfilter ip6t_REJECT xt_conntrack bnep 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 fuse arc4 mmc_block powernow_k8 kvm_amd kvm edac_core edac_mce_amd ath5k ath mac80211 tifm_sd cfg80211 k8temp snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep sdhci_pci sdhci mmc_core btusb joydev serio_raw toshiba_acpi tifm_7xx1 tifm_core snd_seq sp5100_tco i2c_piix4 snd_seq_device snd_pcm sparse_keymap nfsd snd_timer snd soundcore toshiba_bluetooth video bluetooth 6lowpan_iphc rfkill wmi shpchp auth_rpcgss nfs_acl lockd binfmt_misc sunrpc ata_generic pata_acpi radeon firewire_ohci yenta_socket firewire_core crc_itu_t i2c_algo_bit usb_storage pata_atiixp drm_kms_helper ttm drm r8169 mii i2c_core CPU: 0 PID: 5257 Comm: dd Not tainted 3.14.4-200.fc20.x86_64 #1 Hardware name: TOSHIBA Satellite A215/IALAA, BIOS V2.30 01/15/2010 0000000000000000 0000000022e27405 ffff8800b24a9ae8 ffffffff816ef1d2 ffff8800b24a9b30 ffff8800b24a9b20 ffffffff8108a1bd ffff88011b167830 ffff880036232e08 ffff880036233028 ffff880119e30800 0000000000000000 Call Trace: [<ffffffff816ef1d2>] dump_stack+0x45/0x56 [<ffffffff8108a1bd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8108a23c>] warn_slowpath_fmt+0x5c/0x80 [<ffffffff81215d9d>] __mark_inode_dirty+0x26d/0x270 [<ffffffff8121bc84>] __set_page_dirty+0x74/0xc0 [<ffffffff8121bde1>] mark_buffer_dirty+0x61/0xd0 [<ffffffff8121c501>] __block_commit_write.isra.20+0x81/0xb0 [<ffffffff8121e126>] block_write_end+0x36/0x70 [<ffffffff8121f056>] ? block_write_begin+0x46/0x90 [<ffffffff81223740>] blkdev_write_end+0x20/0x40 [<ffffffff81174496>] generic_file_buffered_write+0x166/0x270 [<ffffffff81175e85>] __generic_file_aio_write+0x1d5/0x3e0 [<ffffffff81224099>] blkdev_aio_write+0x59/0xe0 [<ffffffff811e8ed7>] do_sync_write+0x67/0xa0 [<ffffffff811e969a>] vfs_write+0xba/0x1e0 [<ffffffff811e9574>] ? vfs_read+0xf4/0x160 [<ffffffff811ea0f5>] SyS_write+0x55/0xd0 [<ffffffff816ff569>] system_call_fastpath+0x16/0x1b
Created attachment 908710 [details] File: dmesg
Description of problem: trying to access and fdisk a bad disk mounted in an USB enclosure Version-Release number of selected component: kernel Additional info: reporter: libreport-2.2.3 cmdline: BOOT_IMAGE=/vmlinuz-3.15.6-200.fc20.x86_64 root=UUID=97dea9d2-fbf6-425e-aef3-168df7e6f83e ro vconsole.font=latarcyrheb-sun16 LANG=fr_FR.UTF-8 kernel: 3.15.6-200.fc20.x86_64 runlevel: N 5 type: Kerneloops Truncated backtrace: WARNING: CPU: 0 PID: 12121 at fs/fs-writeback.c:1199 __mark_inode_dirty+0x26d/0x270() bdi-block not registered Modules linked in: md4 nls_utf8 cifs dns_resolver fscache 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 binfmt_misc rtsx_pci_sdmmc iTCO_wdt mmc_core rtsx_pci_ms iTCO_vendor_support memstick x86_pkg_temp_thermal coretemp kvm_intel kvm snd_hda_codec_hdmi crct10dif_pclmul snd_hda_codec_via crc32_pclmul arc4 crc32c_intel snd_hda_codec_generic snd_hda_intel snd_hda_controller iwldvm snd_hda_codec snd_hwdep mac80211 snd_seq ghash_clmulni_intel snd_seq_device snd_pcm microcode iwlwifi serio_raw cfg80211 rtsx_pci i2c_i801 lpc_ich mfd_core rfkill wmi snd_timer snd mei_me shpchp mei soundcore nfsd auth_rpcgss nfs_acl lockd sunrpc uas usb_storage i915 i2c_algo_bit drm_kms_helper drm r8169 mii i2c_core video CPU: 0 PID: 12121 Comm: fdisk Not tainted 3.15.6-200.fc20.x86_64 #1 Hardware name: CLEVO CO. W55xEU /W55xEU , BIOS 4.6.5 03/05/2013 0000000000000000 0000000016015fe8 ffff880101293b00 ffffffff816ef48e ffff880101293b48 ffff880101293b38 ffffffff8108933d ffff8802154297b0 ffff880102608900 ffff880102608b20 ffff8802128d8800 0000000000000000 Call Trace: [<ffffffff816ef48e>] dump_stack+0x45/0x56 [<ffffffff8108933d>] warn_slowpath_common+0x7d/0xa0 [<ffffffff810893bc>] warn_slowpath_fmt+0x5c/0x80 [<ffffffff81211fdd>] __mark_inode_dirty+0x26d/0x270 [<ffffffff81217d04>] __set_page_dirty+0x74/0xc0 [<ffffffff81217e61>] mark_buffer_dirty+0x61/0xd0 [<ffffffff81218581>] __block_commit_write.isra.21+0x81/0xb0 [<ffffffff8121a1b6>] block_write_end+0x36/0x70 [<ffffffff8121b0e6>] ? block_write_begin+0x46/0x90 [<ffffffff8121f770>] blkdev_write_end+0x20/0x40 [<ffffffff8120125a>] ? file_update_time+0xaa/0xf0 [<ffffffff8117199b>] generic_perform_write+0x11b/0x1d0 [<ffffffff8120125a>] ? file_update_time+0xaa/0xf0 [<ffffffff8120125a>] ? file_update_time+0xaa/0xf0 [<ffffffff81173d7d>] __generic_file_aio_write+0x1dd/0x400 [<ffffffff812200b5>] blkdev_aio_write+0x55/0xe0 [<ffffffff811e5d27>] do_sync_write+0x67/0xa0 [<ffffffff811e64ea>] vfs_write+0xba/0x1e0 [<ffffffff811e5f6d>] ? fixed_size_llseek+0x1d/0x20 [<ffffffff811e70a5>] SyS_write+0x55/0xd0 [<ffffffff816ff4e9>] system_call_fastpath+0x16/0x1b
*********** 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.