Therefore, in my inode installation routine, I do a d_alloc and get a
new dentry and adds this to the dcache by calling d_add(dentry,
inode). If the inode installation has been triggered by a lookup, that
process will be woken up.
The problem is, when lookup wakes up, I have to get the information
(the inode) from the installed dentry (i get the dentry from
d_lookup), kill that dentry and install my own (since lookup has to
fill in a preallocated dentry). I have experimented alot with
different ways to kill that dentry, but I have not found any way that
works. The same problem arises in create.
Is there a good way to kill this dentry? It should not be visible when
doing a cached lookup, and it shouldn't be on the directory's hash
table.
/Magnus
map@stacken.kth.se
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html