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: <20071024150302.GD2652@duck.suse.cz>
Date:	Wed, 24 Oct 2007 17:03:03 +0200
From:	Jan Kara <jack@...e.cz>
To:	Andy Whitcroft <andyw@...ibm.com>
Cc:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
Subject: Re: 2.6.23-git18: ext2_check_page: bad entry in directory

On Wed 24-10-07 15:33:08, Andy Whitcroft wrote:
> On Wed, Oct 24, 2007 at 03:59:00PM +0200, Jan Kara wrote:
> >   Hello,
> > 
> > On Wed 24-10-07 14:15:40, Andy Whitcroft wrote:
> > > Seems that we are now getting strange errors mounting an ext2 root
> > > filesystem under 2.6.23-git18:
> > > 
> > >   EXT2-fs error (device sda1): ext2_check_page: bad entry in directory #2:
> > >   rec_len is smaller than minimal - offset=0, inode=0, rec_len=0,
> > >   name_len=0
> >   Hmm, zero length entry in a root directory. Not nice.
> > 
> > > This seems to be occuring consistently since 2.6.23-git18.  I have been
> > > back and rerun a -git17 job to confirm its not visible at that level.
> > > This bug is expressing itself in 2.6.23-rc1 also.
> > > 
> > > I am suspicious of this commit in the -git17 -> -git18 block:
> > > 
> > >   commit 89910cccb8fec0c1140d33a743e72a712efd4f05
> > >   Author: Jan Kara <jack@...e.cz>
> > >   Date:   Sun Oct 21 16:41:40 2007 -0700
> > > 
> > >       ext2: avoid rec_len overflow with 64KB block size
> > > 
> > > /me goes debug this a bit more.
> >   Hmm, I'd suspect that too ;) But I swear I actually tested the code ;)
> > So what are you using the filesystem for (or do you get the error
> > immediately when mounting)? How large is the filesystem?
> 
> Its the root filesystem, so thats all she wrote.  The kernel fails to
> mount it and the world ends.  Its pretty small in now world terms.
> 
> /dev/sda1              17G   10G  6.0G  63% /
  OK, could you send me the metadata from the filesystem?

e2image -r /dev/sda1 - | gzip -dc root-image.gz

  Thanks.
								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ