From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-kernel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org
Subject: 2.6.35-rc6 REGRESSION: Dirtiable inode bdi default != sb bdi ext2/ext3/ext4
Date: Fri, 01 Oct 2010 17:35:54 -0400 [thread overview]
Message-ID: <E1P1nGk-00023P-3d@tytso-glaptop> (raw)
I'm not sure this is related to:
http://bugzilla.kernel.org/show_bug.cgi?id=19062
(2.6.35-rc6 REGRESSION: Dirtiable inode bdi default != sb bdi btrfs)
or not, but this is a problem that did not exist in 2.6.36-rc3 and
showed up when I tried going to 2.6.36-rc6.
The symptoms are that if I mount a filesystem, whether it be ext2, ext3,
or ext4, modify it slightly (say, create a file or a directory), then
umount the filesystem, and run "e2fsck -f" on that filesystem, I get the
warning:
[ 866.543173] WARNING: at /usr/projects/linux/ext4/fs/fs-writeback.c:87 ino_bdi+0x4e/0x5c()
[ 866.546156] Hardware name:
[ 866.547415] Dirtiable inode bdi block != sb bdi block
[ 866.556113] Modules linked in:
[ 866.557522] Pid: 1993, comm: e2fsck Tainted: G W 2.6.36-rc6-0004aa513 #722
[ 866.560365] Call Trace:
[ 866.561475] [<c015a2e2>] warn_slowpath_common+0x6a/0x7f
[ 866.563312] [<c020a762>] ? inode_to_bdi+0x4e/0x5c
[ 866.565047] [<c015a36a>] warn_slowpath_fmt+0x2b/0x2f
[ 866.566852] [<c020a762>] inode_to_bdi+0x4e/0x5c
[ 866.568457] [<c020b6c3>] __mark_inode_dirty+0xaf/0x162
[ 866.570242] [<c0202305>] file_update_time+0xcc/0xe9
[ 866.571924] [<c01c68dd>] __generic_file_aio_write+0x136/0x28f
[ 866.573770] [<c02145a4>] blkdev_aio_write+0x33/0x72
[ 866.575480] [<c01f20da>] do_sync_write+0x8f/0xca
[ 866.577145] [<c0646db8>] ? mutex_unlock+0xd/0xf
[ 866.578760] [<c030cc70>] ? security_file_permission+0x27/0x2b
[ 866.583696] [<c01f227c>] ? rw_verify_area+0x9d/0xc0
[ 866.585906] [<c01f204b>] ? do_sync_write+0x0/0xca
[ 866.587735] [<c01f2629>] vfs_write+0x85/0xe3
[ 866.589575] [<c01f2725>] sys_write+0x40/0x62
[ 866.591435] [<c064889d>] syscall_call+0x7/0xb
[ 866.593240] [<c0640000>] ? init_amd+0x158/0x532
[ 866.594129] ---[ end trace 4cd5bce2135538d2 ]---
This is rather blatent and obvious, so I'm wondering how this got
missed?
- Ted
reply other threads:[~2010-10-01 21:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1P1nGk-00023P-3d@tytso-glaptop \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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