linux-kernel - Re: I give up

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:	Wed, 11 Apr 2007 18:43:38 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	"John Anthony Kazos Jr." <jakj@...-k-j.com>
Cc:	Phillip Susi <psusi@....rr.com>,
	Gene Heskett <gene.heskett@...il.com>,
	linux-kernel@...r.kernel.org, Olaf Hering <olaf@...fle.de>,
	Dave Dillow <dave@...dillows.org>,
	Dave Jones <davej@...hat.com>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	"H. Peter Anvin" <hpa@...or.com>, Jeff Garzik <jeff@...zik.org>
Subject: Re: I give up

"John Anthony Kazos Jr." <jakj@...-k-j.com> writes:

> I think that's especially true. If a user begins with a single full disk 
> for their entire filesystem, uses tar to backup, and then later adds a 
> second disk, copies everything from /usr and /home onto partitions there 
> (making sure to preserve all interesting bits like ctime/mtime), and 
> mounts them over the original directories, tar should not decide that 
> every file in /usr and /home was deleted and recreated.

That wouldn't work, even if you managed to copy ctime, the target
inode number will be different than the original and backup has
to assume it's a different file.

For filesystems with no stable inode numbers my backup scheme
assumes that the same file = the same name and times but it's
really fragile.

An option to ignore block device number does make sense, of course.
Especially when backing up only one filesystem (-xdev etc).
-- 
Krzysztof Halasa
-
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/