Bug 1111995 - [abrt] WARNING: CPU: 0 PID: 3800 at fs/ext4/inode.c:353 ext4_da_update_reserve_space+0x1ed/0x260() [NEEDINFO]
Summary: [abrt] WARNING: CPU: 0 PID: 3800 at fs/ext4/inode.c:353 ext4_da_update_reserv...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: fedora-kernel-extfs
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:0749a18a5c7c635d22e6a53a26e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-22 15:01 UTC by Ravindra Patake
Modified: 2014-12-10 14:58 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-10 14:58:03 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (57.39 KB, text/plain)
2014-06-22 15:01 UTC, Ravindra Patake
no flags Details

Description Ravindra Patake 2014-06-22 15:01:26 UTC
Additional info:
reporter:       libreport-2.2.2
WARNING: CPU: 0 PID: 3800 at fs/ext4/inode.c:353 ext4_da_update_reserve_space+0x1ed/0x260()
Modules linked in: fuse 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 coretemp kvm_intel kvm iTCO_wdt snd_hda_codec_realtek iTCO_vendor_support snd_hda_codec_generic gpio_ich ppdev snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device microcode snd_pcm serio_raw i2c_i801 lpc_ich snd_timer snd soundcore parport_pc parport acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc i915 ata_generic pata_acpi video i2c_algo_bit drm_kms_helper
r8169 drm mii i2c_core
CPU: 0 PID: 3800 Comm: DOM Worker Not tainted 3.14.8-200.fc20.i686 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080015  02/03/2010
c0c69907 f47a5b05 00000000 ef29fa44 c09eaca5 00000000 ef29fa74 c044c9be
c0b8ff28 00000000 00000ed8 c0bb3617 00000161 c05e0a0d c05e0a0d 00000000
e835b148 ef29fd48 ef29fa84 c044cac2 00000009 00000000 ef29fac8 c05e0a0d
Call Trace:
[<c09eaca5>] dump_stack+0x41/0x52
[<c044c9be>] warn_slowpath_common+0x7e/0xa0
[<c05e0a0d>] ? ext4_da_update_reserve_space+0x1ed/0x260
[<c05e0a0d>] ? ext4_da_update_reserve_space+0x1ed/0x260
[<c044cac2>] warn_slowpath_null+0x22/0x30
[<c05e0a0d>] ext4_da_update_reserve_space+0x1ed/0x260
[<c060d99b>] ext4_ext_map_blocks+0xd9b/0x1bc0
[<c055c6c5>] ? __kmalloc+0x1a5/0x1f0
[<c0483236>] ? task_tick_fair+0x1e6/0x790
[<c0609cc9>] ? ext4_ext_find_extent+0x1d9/0x270
[<c0609cc9>] ? ext4_ext_find_extent+0x1d9/0x270
[<c0609cc9>] ? ext4_ext_find_extent+0x1d9/0x270
[<c047d81b>] ? __update_cpu_load+0xab/0xd0
[<c05e0d6d>] ext4_map_blocks+0x2ed/0x580
[<c05e3722>] mpage_map_and_submit_extent+0xb2/0x770
[<c05e4270>] ext4_writepages+0x490/0x670
[<c0594239>] ? __mark_inode_dirty+0x129/0x210
[<c05ea8bc>] ? ext4_find_entry+0x19c/0x5d0
[<c0523fda>] do_writepages+0x1a/0x40
[<c051a83d>] __filemap_fdatawrite_range+0x5d/0x80
[<c051a92b>] filemap_flush+0x2b/0x30
[<c05e15af>] ext4_alloc_da_blocks+0x2f/0x60
[<c05ed048>] ext4_rename+0x568/0x890
[<c065006c>] ? selinux_inode_rename+0x12c/0x180
[<c09ef750>] ? mutex_lock+0x10/0x28
[<c0579eca>] vfs_rename+0x53a/0x580
[<c05766a4>] ? lookup_dcache+0x24/0xa0
[<c057a166>] SYSC_renameat+0x256/0x380
[<c04b6697>] ? SyS_futex+0x97/0x160
[<c057cf52>] SyS_rename+0x42/0x60
[<c09f910d>] sysenter_do_call+0x12/0x28
[<c09f0000>] ? __mutex_lock_killable_slowpath+0x12b/0x18b

Comment 1 Ravindra Patake 2014-06-22 15:01:32 UTC
Created attachment 911157 [details]
File: dmesg

Comment 2 Justin M. Forbes 2014-11-13 15:56:54 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 14:58:03 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.


Note You need to log in before you can comment on or make changes to this bug.