From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 19362] New: WARNING: at fs/fs-writeback.c:87 __mark_inode_dirty+0x1f2/0x230()
Date: Thu, 30 Sep 2010 13:09:40 GMT [thread overview]
Message-ID: <bug-19362-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=19362
Summary: WARNING: at fs/fs-writeback.c:87
__mark_inode_dirty+0x1f2/0x230()
Product: File System
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: trenn@suse.de
Regression: No
Happens for some time already in latest mainline kernel.
I'll attach relevant dmesg and /etc/mtab parts.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2010-09-30 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 13:09 bugzilla-daemon [this message]
2010-09-30 13:10 ` [Bug 19362] WARNING: at fs/fs-writeback.c:87 __mark_inode_dirty+0x1f2/0x230() bugzilla-daemon
2010-09-30 13:12 ` bugzilla-daemon
2010-09-30 15:05 ` bugzilla-daemon
2010-10-08 12:44 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-19362-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox