xfs
[Top] [All Lists]

Re: the thing with the binary zeroes

To: linux-xfs@xxxxxxxxxxx
Subject: Re: the thing with the binary zeroes
From: martin f krafft <madduck@xxxxxxxxxxx>
Date: Sat, 12 Feb 2005 13:07:18 +0100
In-reply-to: <m1r7jmf0q7.fsf@muc.de>
Mail-followup-to: linux-xfs@xxxxxxxxxxx
References: <20050211121829.GA30049@localhost.localdomain> <m1sm43uu8h.fsf@muc.de> <20050211131546.GA32336@localhost.localdomain> <m1oeeruswr.fsf@muc.de> <20050211133558.GA32501@localhost.localdomain> <m1k6pfurpd.fsf@muc.de> <Pine.GSO.4.58.0502121642380.25840@jekyll.uws.edu.au> <m1r7jmf0q7.fsf@muc.de>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
also sprach Andi Kleen <ak@xxxxxx> [2005.02.12.1259 +0100]:
> Ordered data just guarantees that there is never a window where
> the machine crashes that you can see "raw" disk blocks after
> recovery. "Raw" means blocks that are not under control of the
> file system and can be arbitary old data. This can be
> a theoretical security hole (although in practice you usually only
> see some garbage) 
> 
> As far as I know XFS guarantees this already, so it supports
> "ordered data" in the JBD sense. 

But that would solve my problem. How does XFS guarantee this? Didn't
you just say it is impossible to get at the raw data again as XFS
nulls it?

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
spamtraps: madduck.bogus@xxxxxxxxxxx
 
"be the change you want to see in the world"
                                                     -- mahatma gandhi

Attachment: signature.asc
Description: Digital signature

<Prev in Thread] Current Thread [Next in Thread>