linux-kernel - Re: Immutable biovecs, dio rewrite

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130612203002.GD6151@google.com>
Date:	Wed, 12 Jun 2013 13:30:02 -0700
From:	Kent Overstreet <koverstreet@...gle.com>
To:	Dave Chinner <david@...morbit.com>
Cc:	axboe@...nel.dk, tytso@....edu, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: Immutable biovecs, dio rewrite

On Tue, Jun 11, 2013 at 03:20:12PM +1000, Dave Chinner wrote:
> Please test with XFS and CONFIG_XFS_DEBUG=y - xfstests will stress
> the dio subsystem a lot more when it is run on XFS. Indeed, xfstests
> generic/013 assert fails almost immediately with:

Thanks - I haven't used xfstests much before. This one turned out to be
an easy fix, but once I turned on CONFIG_XFS_DEBUG I hit something else
I hadn't seen before:

[ 1343.482366] XFS (sdb2): Corruption detected. Unmount and run xfs_repair
[ 1343.482425] XFS (sdb2): bad inode magic/vsn daddr 64 #8 (magic=5858)
[ 1343.482482] XFS: Assertion failed: 0, file: /home/kent/linux/fs/xfs/xfs_inode.c, line: 417
[ 1343.482558] ------------[ cut here ]------------
[ 1343.482611] kernel BUG at /home/kent/linux/fs/xfs/xfs_message.c:108!

This one looks weirder - any thoughts on what might cause _that_?

(Don't spend any time on it, I haven't tried to debug it besides glancing at
the relevant xfs code - just curious if you have any pointers)
--
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/