linux-kernel - Re: [PATCH 15/32] union-mount: Documentation

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:	Mon, 25 May 2009 17:43:10 +0900
From:	hooanon05@...oo.co.jp
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Jan Blunck <jblunck@...e.de>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, viro@...iv.linux.org.uk,
	bharata@...ibm.com, dwmw2@...radead.org, mszeredi@...e.cz,
	vaurora@...hat.com
Subject: Re: [PATCH 15/32] union-mount: Documentation 


Arnd Bergmann:
> Right, but that is consistent with how the kernel would treat a
> rename from one mount point to another, and tools like 'mv'
> can handle this in user space.

Yes, that is the description in the union mount document.
While it says to rename a regular file is implemented, the code differs
actually.
----------------------------------------
+Rename across different levels of the union is implemented as a copy-up
+operation for regular files. Rename of directories simply returns EXDEV, the
+same as if we tried to rename across different mounts. Most applications have
	:::
----------------------------------------
--
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/