mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kasprzak <kas@fi.muni.cz>
To: linux-kernel@vger.kernel.org
Subject: XFS information leak during crash
Date: Wed, 2 Nov 2005 22:27:22 +0100	[thread overview]
Message-ID: <20051102212722.GC6759@fi.muni.cz> (raw)

	Hello, world!\n

I have found that after the system crash (e.h. a hard reset or a power
failure) XFS corrupts files which have been written to just before the crash:
The result is that those files contain data from random blocks on the
disk (e.g. from previously deleted files). This can have security/privacy
implications - users can see the contents of other users' old files.

	I have even written a test program, which creates/rewrites
files with known contents in a given directory. After the hard
reset while running this program some of the files contain blocks
with "random" data (i.e. not the original data and not the new data
either). Does XFS support a something like ext3's "data=ordered" mount
option? Otherwise it is pretty unusable on multi-user systems.

	This is on 2.6.11.10 and 2.6.14 running on x86_64 and i386 SMP
configurations. I may test it on UP if there is an interest.

	The quick-hack-style test program can be found at
http://www.fi.muni.cz/~kas/progs/xfsrewrite.c

-Yenya

-- 
| Jan "Yenya" Kasprzak  <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839      Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/    Journal: http://www.fi.muni.cz/~kas/blog/ |
> Specs are a basis for _talking_about_ things. But they are _not_ a basis <
> for implementing software.                              --Linus Torvalds <

             reply	other threads:[~2005-11-02 21:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 21:27 Jan Kasprzak [this message]
2005-11-02 23:11 ` Nathan Scott
2005-11-02 23:36   ` Jan Kasprzak
2005-11-02 23:49     ` Nathan Scott
2005-11-03  0:03       ` Jan Kasprzak
2005-11-03  0:11         ` Nathan Scott
2005-11-03 12:45           ` Alan Cox
2005-11-03 17:05             ` Theodore Ts'o
2005-11-09 16:55     ` Jan Kasprzak
2005-11-03  0:19   ` Mikulas Patocka
2005-11-03  0:38     ` Nathan Scott
2005-11-03  0:41     ` Glen Overby

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=20051102212722.GC6759@fi.muni.cz \
    --to=kas@fi.muni.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®