linux-kernel - Re: 2.6.33-rc4-mmotm0113

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100118233352.GA6352@atrey.karlin.mff.cuni.cz>
Date:	Tue, 19 Jan 2010 00:33:52 +0100
From:	Jan Kara <jack@...e.cz>
To:	Valdis.Kletnieks@...edu
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Andreas Dilger <adilger@....com>,
	Theodore Ts'o <tytso@....edu>, linux-kernel@...r.kernel.org,
	linux-ext4@...r.kernel.org
Subject: Re: 2.6.33-rc4-mmotm0113 - ext3 throws warning..

  Hi,

> Took a power hit earlier in the day, laptop rode it out, external 500G SUB
> drive didn't. Several hours later I finally do something that references
> the filesystem on the external drive, and I get:
> 
> [312252.610201] EXT3-fs error (device sdb2): ext3_get_inode_loc: unable to read inode block - inode=5964029, block=23855121
> [312252.610740] ------------[ cut here ]------------
> [312252.610759] WARNING: at fs/buffer.c:1181 mark_buffer_dirty+0x65/0xdd()
> [312252.610768] Hardware name: Latitude E6500                  
> [312252.610776] Modules linked in: ppp_async sunrpc usb_storage [last unloaded: microcode]
> [312252.610808] Pid: 2256, comm: ls Not tainted 2.6.33-rc4-mmotm0113 #1
> [312252.610816] Call Trace:
> [312252.610836]  [<ffffffff81038ac1>] warn_slowpath_common+0x77/0x8f
> [312252.610849]  [<ffffffff81038ae8>] warn_slowpath_null+0xf/0x11
> [312252.610862]  [<ffffffff810fdb40>] mark_buffer_dirty+0x65/0xdd
> [312252.610875]  [<ffffffff81147997>] ext3_commit_super.clone.0+0x54/0x64
> [312252.610889]  [<ffffffff81147a37>] ext3_handle_error+0x90/0xb7
> [312252.610902]  [<ffffffff81147dd7>] ext3_error+0x76/0x81
> [312252.610918]  [<ffffffff8113e9e4>] __ext3_get_inode_loc+0x261/0x287
> [312252.610932]  [<ffffffff8113ea24>] ext3_get_inode_loc+0x1a/0x1c
> [312252.610945]  [<ffffffff8113ea4e>] ext3_reserve_inode_write+0x28/0x82
> [312252.610958]  [<ffffffff8113eae0>] ext3_mark_inode_dirty+0x38/0x55
> [312252.610971]  [<ffffffff8113ec40>] ext3_dirty_inode+0x6a/0x81
> [312252.610986]  [<ffffffff810f7b04>] __mark_inode_dirty+0x2f/0x14c
> [312252.610999]  [<ffffffff810ede7b>] touch_atime+0x102/0x125
> [312252.611014]  [<ffffffff810e902c>] ? filldir+0x0/0xcb
> [312252.611027]  [<ffffffff810e9270>] vfs_readdir+0x8a/0xb1
> [312252.611040]  [<ffffffff810e9427>] sys_getdents+0xa6/0xf8
> [312252.611057]  [<ffffffff810023ab>] system_call_fastpath+0x16/0x1b
> [312252.611067] ---[ end trace e506d3eb52cbaab0 ]---
> [312252.611138] EXT3-fs (sdb2): error in ext3_reserve_inode_write: IO failure
> [312257.701924] journal_bmap: journal block not found at offset 84 on sdb2
> [312257.701937] Aborting journal on device sdb2.
> 
> It was totally in its rights to abort the journal. The WARNING, not so much?
  Yeah, this is a known problem that buffer_uptodate flag gets cleared
on IO error and so if we ever try to mark that buffer dirty again, we
get this warning... It's harmless but annoying I agree.

								Honza
-- 
Jan Kara <jack@...e.cz>
SuSE CR Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/