kernfs: introduce kernfs_node_id
inode number and generation can identify a kernfs node. We are going to export the identification by exportfs operations, so put ino and generation into a separate structure. It's convenient when later patches use the identification. Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Shaohua Li <shli@fb.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
This commit is contained in:
@@ -895,7 +895,7 @@ repeat:
|
||||
* have the matching @file available. Look up the inodes
|
||||
* and generate the events manually.
|
||||
*/
|
||||
inode = ilookup(info->sb, kn->ino);
|
||||
inode = ilookup(info->sb, kn->id.ino);
|
||||
if (!inode)
|
||||
continue;
|
||||
|
||||
@@ -903,7 +903,7 @@ repeat:
|
||||
if (parent) {
|
||||
struct inode *p_inode;
|
||||
|
||||
p_inode = ilookup(info->sb, parent->ino);
|
||||
p_inode = ilookup(info->sb, parent->id.ino);
|
||||
if (p_inode) {
|
||||
fsnotify(p_inode, FS_MODIFY | FS_EVENT_ON_CHILD,
|
||||
inode, FSNOTIFY_EVENT_INODE, kn->name, 0);
|
||||
|
Reference in New Issue
Block a user