| Summary: | [abrt] kernel: WARNING: at fs/ext3/inode.c:1571 ext3_ordered_writepage+0x4e/0x1ae(): TAINTED Warning Issued | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Arnulfo Jose Suarez Gaekel <ajose> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | esandeen, frank.mehnert, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:2854f56f304e1314685a90466791bdb44676170d | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-06 22:11:17 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Arnulfo Jose Suarez Gaekel
2011-06-16 19:44:57 UTC
fs/ext3/inode.c:1571:
WARN_ON_ONCE(IS_RDONLY(inode));
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? 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. Can you recreate this on the latest F15 kernel without the vbox modules loaded? pretty sure this is vbox, given all the other similar bugs we've seen the last few months. 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? |