linux-kernel - Re: HELP!!! SD and suspend damage i-node.

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: <200703222255.20167.rjw@sisk.pl>
Date:	Thu, 22 Mar 2007 22:55:19 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Sergey Smirnov <svs1957@...il.com>
Cc:	linux-kernel@...r.kernel.org, Pavel Machek <pavel@....cz>
Subject: Re: HELP!!! SD and suspend damage i-node.

On Thursday, 22 March 2007 13:35, Sergey Smirnov wrote:
> I use 2.6.20.2 kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750 (PXA255).
> After suspend/resume filesystem stay clean. But some i-nodes become broken.
> Some files looks like block device or pipe with strange permissions, owner etc.
> I'm sure that there is no bad blocks on SD.
> I'll send any additional information. Just say me what you need to help me.
> I had i lot of tries. Apply patches, remove its, change fstype etc.
> output of fsck -f

I assume this is the suspend to RAM?

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