On Sun 03-10-10 17:16:51, Tejun Heo wrote: > On 10/03/2010 04:27 AM, Ted Ts'o wrote: > > WARNING: at /usr/projects/linux/ext4/fs/fs-writeback.c:87 inode_to_bdi+0x4e/0x5c() > > Hardware name: > > Dirtiable inode bdi block != sb bdi block > > Modules linked in: > > Pid: 21649, comm: mkfs.ext4 Tainted: G W 2.6.36-rc6-00016-gcc25699 #735 > > Call Trace: > > [<c015a2e2>] warn_slowpath_common+0x6a/0x7f > > [<c020a762>] ? inode_to_bdi+0x4e/0x5c > > [<c015a36a>] warn_slowpath_fmt+0x2b/0x2f > > [<c020a762>] inode_to_bdi+0x4e/0x5c > > [<c020b6c3>] __mark_inode_dirty+0xaf/0x162 > > [<c0202305>] file_update_time+0xcc/0xe9 > > [<c01c68dd>] __generic_file_aio_write+0x136/0x28f > > [<c02145a4>] blkdev_aio_write+0x33/0x72 > > [<c01f20da>] do_sync_write+0x8f/0xca > > [<c0647678>] ? mutex_unlock+0xd/0xf > > [<c030d528>] ? security_file_permission+0x27/0x2b > > [<c01f227c>] ? rw_verify_area+0x9d/0xc0 > > [<c01f204b>] ? do_sync_write+0x0/0xca > > [<c01f2629>] vfs_write+0x85/0xe3 > > [<c01f2725>] sys_write+0x40/0x62 > > [<c064915d>] syscall_call+0x7/0xb > > ---[ end trace 1f39401760ab3a42 ]--- Yes, it's caused by one of my fixes. It's harmless (the warning I've added is just too strict). Christoph has a patch that also fixes this - http://lkml.org/lkml/2010/9/29/76. I hope he'll push it soon. Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
