linux-kernel - Re: zaurus pata_pcmcia corrupted filesystem

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: <20100821095137.GA22301@atrey.karlin.mff.cuni.cz>
Date:	Sat, 21 Aug 2010 11:51:37 +0200
From:	Cyril Hrubis <metan@....cz>
To:	Stanislav Brabec <utx@...guin.cz>
Cc:	Kristoffer Ericson <kristoffer.ericson@...il.com>,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	Robert Hancock <hancockrwd@...il.com>,
	Tejun Heo <tj@...nel.org>,
	Dominik Brodowski <linux@...inikbrodowski.net>,
	Jeff Garzik <jgarzik@...ox.com>, pavel@....cz,
	rpurdie@...ys.net, lenz@...wisc.edu, arminlitzel@....de,
	thommycheck@...il.com, dbaryshkov@...il.com, omegamoon@...il.com,
	eric.y.miao@...il.com, zaurus-devel@...ts.linuxtogo.org,
	Marek Vasut <marek.vasut@...il.com>
Subject: Re: zaurus pata_pcmcia corrupted filesystem

Hi!
> > These seems to be different, at least it newer occured so often to me. Now
> > installing debian packages often fails because it cannot remove temporary
> > files, the filesystem worked reasonably good before.
> > 
> > The usecase is to unpack archive with a lot rather small files somewhere deeper
> > to the filesystem tree. Eg. installing gtk2-devel failed miserably when trying
> > to move all the header files from *.h.dpkg-new to *.h, this works rather good
> > with old driver.
> 
> Well, I remember opkg crashes while installing emacs (many small files)
> and file system corruption as well. Both with kernel 2.6.26.
>

The main difference is that now it's 100% reproducible and I've never seen
corruption bad enough so I could not delete files without doing fsck first.

Here is pseudo output from fsck on ext3 filesystem after these problems
appeared:

Pass 2:

Bunch of these:

Invalid HTREE directory inode $NUMBER
$PATH/$FILE
Clear HTree index<y>?

and these:

Problem in HTree directory inode $NUMBER: block #$NR has bad max hash

Pass 3:

Bunch of:

Entry '$FILE in $PATH ($NUMBER) has a non-unique filename.
Rename to $FILE~0<y>?

Happily the files/directories affected was only the recently written from the
kernel from marex tree.  I haven't seen file content to be corrupted (that
doesn't mean there weren't any corruptions) but it seems they are not so likely
as directory tree corruption.

-- 
metan
--
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/