In reply to tytso@ATHENA.MIT.EDU: You can let the system call rename() do the trick for you, and forbid linking of directories - correct. If you forbid linking of directories, you see if one directoy is an ancestor of the other *by looking at the names*. That will take away your race condition for free. We do however still have to avoid concurrent directory moves from the same source directory - and into the old tree. open()'s etc. are ok (I think), they must be atomic, and will fail or succeed depending on how far the rename() operation has come. Kind regards Kurt \/\/achmann, M.Sc. EE/SE
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| James Bottomley | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| Andrew Morton | echo mem > /sys/power/state |
| Peter Zijlstra | [PATCH 00/23] per device dirty throttling -v8 |
git: | |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
| Michael S. Tsirkin | Re: [RFC PATCH v2 03/19] vbus: add connection-client helper infrastructure |
| NeilBrown | [PATCH 00/18] Assorted md patches headed for 2.6.30 |
| Justin Piszcz | General question (scheduler) with SSDs? |
| Neil Brown | Re: Any hope for a 27 disk RAID6+1HS array with four disks reporting "No md superb... |
| Ryan Wagoner | High IO Wait with RAID 1 |
