linux-ext4 - Re: ext3 warnings from LTP rename14

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]

Message-ID: <20071018060850.GN8122@schatzie.adilger.int>
Date:	Thu, 18 Oct 2007 00:08:50 -0600
From:	Andreas Dilger <adilger@...sterfs.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: ext3 warnings from LTP rename14

On Oct 16, 2007  21:17 -0500, Eric Sandeen wrote:
> Eric Sandeen wrote:
> > Martin Habets wrote:
> >> I ran the ltp-full-20070930 tests on 2.6.23-rc9-mph4 (sparc32 SMP), and am
> >> seeing the following warnings:
> > 
> > This makes me a little nervous about my change
> > ef2b02d3e617cb0400eedf2668f86215e1b0e6af
> > (ext34: ensure do_split leaves enough free space in both blocks)
> > 
> > Do you know when this first showed up?  Could you test -rc6?
> > 
> > You say you can reproduce it; have you checked (fsck'd) the filesystem
> > in between, and is it in good shape?
> > 
> > -Eric
> 
> FWIW, I ran rename14 "standalone" a few times on 2.6.23.1 with no
> problems...
> 
> [root@...r-05 ltp-full-20070930]#
> ./testcases/kernel/syscalls/rename/rename14
> rename14    1  PASS  :  Test Passed
> [root@...r-05 ltp-full-20070930]#
> ./testcases/kernel/syscalls/rename/rename14
> rename14    1  PASS  :  Test Passed
> [root@...r-05 ltp-full-20070930]#
> ./testcases/kernel/syscalls/rename/rename14
> rename14    1  PASS  :  Test Passed
> [root@...r-05 ~]# uname -a
> Linux bear-05.lab.msp.redhat.com 2.6.23.1 #1 SMP Mon Oct 15 15:28:08 CDT
> 2007 i686 athlon i386 GNU/Linux

It is probably significant that the original machine is a sparc32 (big
endian).  I'd suspect you can reproduce this on a PPC system also.  You
might also consider running sparse on it ext3/ext4 in case you missed an
le32_to_cpu() or something.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

-
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