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:	Sat, 14 Aug 2010 18:48:31 +0200
From:	Cyril Hrubis <metan@....cz>
To:	Marek Vasut <marek.vasut@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	Robert Hancock <hancockrwd@...il.com>,
	Kristoffer Ericson <kristoffer.ericson@...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, utx@...guin.cz,
	zaurus-devel@...ts.linuxtogo.org
Subject: Re: zaurus pata_pcmcia corrupted filesystem

Hi!
> > Marek Vasut ported deprecated zaurus pcmcia disk driver to the pata_pcmcia
> > interface, sources are here:
> > 
> > http://git.kernel.org/?p=linux/kernel/git/marex/pxa-linux-2.6.git;a=shortlo
> > g;h=refs/heads/zaurus-haxing
> > 
> > Everythig seems to be fine at the first look but sometimes the filesystem
> > gets unconsistent. Typical example is extracting tar archive with big
> > number of files and directories (I used ltp-full archive from
> > http://www.sf.net/projects/ltp/). After doing that, some files or
> > directories are present in the filesystem, eg. you can see them in
> > directory listing but open or fstat returns ENOENT.
> > 
> > Extracting to SD card seems to work without any problems.
> > 
> > Anybody has idea what went wrong?
> 
> I use the pcmcia on a few devices and was unable to replicate it (and I use git 
> and do some heavy compiling on them too). I'll do some further testing.
> 
> Cyril, do you have the PCMCIA timing fix for PXA applied?

Well git log says so:

...
    pxa2xx/cpufreq: Fix PCMCIA frequency scaling
    
    The MCxx values must be based off memory clock, not CPU core clock.
    
    This also fixes the bug where on some machines the LCD went crazy while using
    PCMCIA.
    
...


At least it's your tree that I've been testing ;).

-- 
Cyril Hrubis
--
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