| 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
| ||
|
Message-Id: <200708020724.40623.philipp.marek@bmlv.gv.at> Date: Thu, 2 Aug 2007 07:24:39 +0200 From: "Ph. Marek" <philipp.marek@...v.gv.at> To: Josef Sipek <jsipek@....cs.sunysb.edu> Cc: Dave Kleikamp <shaggy@...ux.vnet.ibm.com>, Jan Blunck <jblunck@...e.de>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, Bharata B Rao <bharata@...ux.vnet.ibm.com>, hch@...radead.org Subject: Re: [RFC 12/26] ext2 white-out support On Mittwoch, 1. August 2007, Josef Sipek wrote: > Alright not the greatest of examples, there is something to be said about > symmetry, so...let me try again :) ... > Oops! There's a whiteout in /b that hides the directory in /c -- rename(2) > shouldn't make directory subtrees disappear. > > There are two ways to solve this: > > 1) "cp -r" the entire subtree ... > > 2) Don't store whiteouts within branches ... Sorry for making uninformed guesses, but if there are already special nodes (whiteout), why not extending them to some more general format - specifying a (source, destination) pair at the topmost level? - A delete is a (source, NULL) pair - A rename is a (source, destination) pair, which causes lookups on source to use the string destination in the lower branches. Would that work? Regards, Phil - 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/
Powered by blists - more mailing lists