Thread (12 messages) 12 messages, 5 authors, 2003-05-25

Re: inode->i_op->rename semantics .

From: Nir Tzachar <hidden>
Date: 2003-05-15 07:33:50

first, thanks for your help ;)

now, i still haver some problems:
Leave association between dentries and inodes alone; VFS will call
d_move() afterwards and it will do the right thing.
im not messing with dentry<->inode associations .
anyway, i tried to read the d_move() code, but some explanations will be 
appreciated. 
All you need to do in ->rename() is
	a) modify on-disk structures
im doing this.
	b) update ->i_nlink for inodes that need it.
which inodes need it? wont the vfs update ->i_nlink for them?
if i need to update ->i_nlink, should i also iput/iget them?? or will the 
vfs do this also?? (im asking, because i didnt see this kind of code 
anywhere in the vfs code. )


-- 
========================================================================
nir.


Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help