"Michael Lotz" <mmlr@xxxxxxxx> wrote: > So far I haven't encountered that situation, but I see what you are > getting at. How would the attribute_overlay be able to tell if a node > is in fact an attribute though? That won't easily be possible, I'm afraid - when you stat the attribute, it will have an inode number differing from its parent, but it's hard to tell on the fly, especially since this can change with any write to an attribute (the node's name can even push other attributes out of the small data space). Since there is no asynchronous I/O interface for userland, we could prevent attributes from being mmaped which should make sure that they aren't accessed like that for now. Bye, Axel.