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
| ||
|
Date: Mon, 25 May 2009 15:25:43 +0900 From: hooanon05@...oo.co.jp To: Jan Blunck <jblunck@...e.de> Cc: 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 Jan Blunck: > +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 handle this case anyway. Some applications do not expect EXDEV on > +rename operations within the same directory, but these applications will also > +be broken with bind mounts. Is renaming a regular file supported? Accrding to the change in "[PATCH 24/32] union-mount: in-kernel file copy between union mounted filesystems", every rename under union seems to be rejected. link(2) may be similar. When a "fileA" exists in the lower fs only, link("fileA", "new_file") will return EXDEV too. J. R. Okajima -- 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