linux-ext4 - Re: Regression with ext4 in kernel 2.6.39-rc7? (Was: testing ext4 master branch)

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 13 May 2011 10:56:08 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Amir Goldstein <amir73il@...il.com>
Cc:	Ext4 Developers List <linux-ext4@...r.kernel.org>,
	Jan Kara <jack@...e.cz>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: Regression with ext4 in kernel 2.6.39-rc7? (Was: testing ext4
 master branch)

On Fri, May 13, 2011 at 12:17:03PM +0300, Amir Goldstein wrote:
> 
> Can anyone try to reproduce the error with xfstest 005 and the crash
> with xfstest 232?

Xfstest #5 broke because of a change in the VFS, which now allows up
to 40 nested symlinks.  So that's a matter of your xfstests being too
old.

The version of xfstests I've been using on my KVM box is too old to
have test 232, so I haven't been able to test it.  I've been trying to
use a newer version of xfstests, but xfstests doesn't build on either
Ubuntu 10.04 (LTS), Debian stable, or Debian unstable, due to the use
of newer XFS ioctl's and xfsctl's that aren't defined in the system
header files.  The fact that it doesn't work on Ubuntu LTS and Stable
is not that surprising, I suppose, but I was a bit disappointed that
it doesn't work on Debian unstable.

Since I don't have a Fedora system handy --- which header file are
things like "struct xfs_flock64" supposed to be defined these days?

       	    	    		 	     - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html