Its a common misconception that a directory that to be empty to become a junction folder / symbolic link directory. Just make an alternative data stream on the directory a symbolic link and the entire directory transforms:pic.twitter.com/HzYvgtlo78
-
Junction folders with files inside rely on a design flaw in NTFS. When a file gets renamed this happes: Permission check, can we delete it from current dir. Permission check, can we create in destination dir. Yes: Then lock detination dir so its impossible to open with DELETE
If its already opened with DELETE then abort rename move operation. Then the source file, gets "deattached" from source dir, and created in destination dir. But what about junction folders? They only require FILE_WRITE_ATTRIBUTES. So if the reparse point gets applied
-
-
when the source file have lefts its source directory the move operation WILL happen regardless of the directory now being a junction folder :) By sending the rename through slow ntobj mgr lookups we get easily a multiply second window to race it.
-
I prefer to just create an oplocked file in destination dir with same name as the rename will create. On oplock trigger I rename the oplock file to another directory and make the directory into a junction folder- then I acknowledge the trigger.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.