From: Pavel Machek <pavel@ucw.cz>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
david@fromorbit.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [2.6.30 and later] file corruption on ext3 filesystem.
Date: Fri, 15 Jan 2010 21:01:36 +0100 [thread overview]
Message-ID: <20100115200136.GD1345@ucw.cz> (raw)
In-Reply-To: <4B4B8664.6000200@redhat.com>
Hi!
>>> 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. :-(
>
> Fedora and some other distributions changed the default back to data
> ordered mode in order to avoid exactly this kind of mess. Even if you
> are on a single user system, this behavior is certainly unexpected for
> most users :-)
Also there's config option to get back the old behaviour.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2010-01-15 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 2:54 [2.6.30 and later] file corruption on ext3 filesystem Tetsuo Handa
2010-01-08 4:07 ` Jamie Lokier
2010-01-08 12:36 ` Dave Chinner
2010-01-08 13:15 ` Tetsuo Handa
2010-01-08 15:19 ` Dave Chinner
2010-01-09 2:53 ` Tetsuo Handa
2010-01-11 20:13 ` Ric Wheeler
2010-01-15 20:01 ` Pavel Machek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100115200136.GD1345@ucw.cz \
--to=pavel@ucw.cz \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rwheeler@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.