linux-kernel - Re: [2.6.30 and later] file corruption on ext3 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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 9 Jan 2010 11:53:03 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:	david@...morbit.com
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [2.6.30 and later] file corruption on ext3 filesystem.

Dave Chinner wrote:
> I agree that it is very wrong, but it's a known problem with writeback
> mode in ext3:
> 
> http://thread.gmane.org/gmane.linux.kernel/818044/focus=819977
> 
> More info as to how this change came about and the proposed but not
> yet realised fixes:
> 
> http://lwn.net/Articles/328363/

Thank you for the pointer.

Indeed, most Linux boxes are used by single user.
But implicitly importing other deleted file's data is still annoying
even if the box is used by only one user.

When I was trying to identify the steps to reproduce, I got ./a.out replaced
by the deleted .bash_history due to power failure. I executed ./a.out as root
without knowing that the file contains deleted .bash_history , and many
commands listed in deleted .bash_history are executed as root.
I thought my box was cracked and trojaned. :-(
--
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/