linux-kernel - unionfs, cow, and whiteout

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-next>] [day] [month] [year] [list]

Date:	Wed, 16 Jan 2008 10:27:13 -0600
From:	Paul Albrecht <albrecht@...1.com>
To:	linux-kernel@...r.kernel.org
Subject: unionfs, cow, and whiteout

Hi,

I have a question about how unionfs handles file deletion when a write
enabled file system is union mounted over a read only file system. For
example, I do something like the following:

mount -t unionfs -o dirs=/cow=rw:/rofs=ro unionfs /mnt

If I create and delete a file in /mnt which is not present in /rofs it
persists as whiteout in the cow file system which is not what I would
have expected.

Why does the deleted file persist as whiteout in the /cow file system of
the union mount?

Please cc me in your response as I'm not subscribed to the lkml.

-- 

Paul Albrecht
--
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/