Bug 713931 - [abrt] kernel: WARNING: at fs/ext3/inode.c:1571 ext3_ordered_writepage+0x4e/0x1ae(): TAINTED Warning Issued
Summary: [abrt] kernel: WARNING: at fs/ext3/inode.c:1571 ext3_ordered_writepage+0x4e/0...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2854f56f304e1314685a9046679...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-16 19:44 UTC by Arnulfo Jose Suarez Gaekel
Modified: 2011-10-12 09:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-06 22:11:17 UTC
Type: ---


Attachments (Terms of Use)

Description Arnulfo Jose Suarez Gaekel 2011-06-16 19:44:57 UTC
abrt version: 2.0.1
architecture:   x86_64
cmdline:        ro root=/dev/mapper/vg_ajosesfedora-ajosesfedora_root rd_LVM_LV=vg_ajosesfedora/ajosesfedora_root rd_LVM_LV=vg_ajosesfedora/ajosesfedora_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=es_ES.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=es rhgb quiet
component:      kernel
kernel:         2.6.38.7-30.fc15.x86_64
kernel_tainted: 512
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         WARNING: at fs/ext3/inode.c:1571 ext3_ordered_writepage+0x4e/0x1ae()
reported_to:    kerneloops: URL=http://submit.kerneloops.org/submitoops.php
time:           Thu Jun 16 11:43:09 2011

backtrace:
:WARNING: at fs/ext3/inode.c:1571 ext3_ordered_writepage+0x4e/0x1ae()
:Hardware name: HP 2230s 
:Modules linked in: fuse vboxnetadp vboxnetflt vboxdrv sunrpc cpufreq_ondemand acpi_cpufreq freq_table mperf usb_storage snd_hda_codec_hdmi uas snd_hda_codec_analog uvcvideo btusb bluetooth snd_hda_intel videodev v4l2_compat_ioctl32 snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm arc4 iwlagn iwlcore hp_wmi sparse_keymap mac80211 snd_timer microcode cfg80211 joydev snd serio_raw iTCO_wdt iTCO_vendor_support soundcore sky2 rfkill snd_page_alloc wmi hp_accel lis3lv02d input_polldev ipv6 i915 drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: scsi_wait_scan]
:Pid: 18000, comm: flush-8:16 Tainted: G        W   2.6.38.7-30.fc15.x86_64 #1
:Call Trace:
: [<ffffffff8105511a>] warn_slowpath_common+0x83/0x9b
: [<ffffffff8105514c>] warn_slowpath_null+0x1a/0x1c
: [<ffffffff81181235>] ext3_ordered_writepage+0x4e/0x1ae
: [<ffffffff810dfc5b>] __writepage+0x15/0x2e
: [<ffffffff810dfac4>] write_cache_pages+0x232/0x332
: [<ffffffff810dfc46>] ? __writepage+0x0/0x2e
: [<ffffffff810dfbe8>] generic_writepages+0x24/0x26
: [<ffffffff810e0758>] do_writepages+0x28/0x2a
: [<ffffffff8113e506>] writeback_single_inode+0x96/0x194
: [<ffffffff8113e85b>] writeback_sb_inodes+0xa1/0x12b
: [<ffffffff8113f670>] writeback_inodes_wb+0x163/0x175
: [<ffffffff8113f8c1>] wb_writeback+0x23f/0x35a
: [<ffffffff81080b9f>] ? arch_local_irq_save+0x15/0x1b
: [<ffffffff8113fb1f>] wb_do_writeback+0x143/0x19d
: [<ffffffff8147457b>] ? schedule_timeout+0xb0/0xde
: [<ffffffff8113fc01>] bdi_writeback_thread+0x88/0x1e5
: [<ffffffff8113fb79>] ? bdi_writeback_thread+0x0/0x1e5
: [<ffffffff8106ebaf>] kthread+0x84/0x8c
: [<ffffffff8100a9e4>] kernel_thread_helper+0x4/0x10
: [<ffffffff8106eb2b>] ? kthread+0x0/0x8c
: [<ffffffff8100a9e0>] ? kernel_thread_helper+0x0/0x10

event_log:
:2011-06-16-12:44:53> Submitting oops report to http://submit.kerneloops.org/submitoops.php
:2011-06-16-12:44:54  Kernel oops report was uploaded

Comment 1 Chuck Ebbert 2011-06-27 05:52:38 UTC
fs/ext3/inode.c:1571:
        WARN_ON_ONCE(IS_RDONLY(inode));

Comment 2 Eric Sandeen 2011-06-27 15:28:48 UTC
Couple things:

> Tainted: G        W

 10: 'W' if a warning has previously been issued by the kernel.

So you got a warning before this.  Do you know what it was?


>         WARN_ON_ONCE(IS_RDONLY(inode));

so it's tryin to write back an inode on a filesystem marked readonly:

#define IS_RDONLY(inode) ((inode)->i_sb->s_flags & MS_RDONLY)

Did the fs hit an error and go readonly prior to this?

Comment 3 Dave Jones 2011-06-27 16:04:02 UTC
It's worth noting that virtualbox was loaded. we're seeing a lot of fs/io related bugs with that loaded lately.  It might be that it's causing latent bugs to show in ways that bare-metal isn't, but I'm more inclined to believe it's part of the problem based on what we've seen so far.

Comment 4 Josh Boyer 2011-09-26 18:15:17 UTC
Can you recreate this on the latest F15 kernel without the vbox modules loaded?

Comment 5 Dave Jones 2011-10-06 22:11:17 UTC
pretty sure this is vbox, given all the other similar bugs we've seen the last few months.

Comment 6 Frank Mehnert 2011-10-12 09:29:54 UTC
Changing both things (VirtualBox modules and Fedora) at the same time will not give us any evidence.

Which version of VirtualBox did you have installed at the time this bug was triggered? Can you still reproduce it? If so, also without the VirtualBox modules loaded?


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