virtiofsd: Set up posix_lock hash table for root inode
We setup per inode hash table ->posix_lock to support remote posix locks. But we forgot to initialize this table for root inode. Laszlo managed to trigger an issue where he sent a FUSE_FLUSH request for root inode and lo_flush() found inode with inode->posix_lock NULL and accessing this table crashed virtiofsd. May be we can get rid of initializing this hash table for directory objects completely. But that optimization is for another day. Reported-by: Laszlo Ersek <lersek@redhat.com> Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Message-Id: <20201207195539.GB3107@redhat.com> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
This commit is contained in:
parent
bebc3c24aa
commit
ad3bfe1bd6
@ -3380,6 +3380,9 @@ static void setup_root(struct lo_data *lo, struct lo_inode *root)
|
||||
root->key.mnt_id = mnt_id;
|
||||
root->nlookup = 2;
|
||||
g_atomic_int_set(&root->refcount, 2);
|
||||
pthread_mutex_init(&root->plock_mutex, NULL);
|
||||
root->posix_locks = g_hash_table_new_full(
|
||||
g_direct_hash, g_direct_equal, NULL, posix_locks_value_destroy);
|
||||
}
|
||||
|
||||
static guint lo_key_hash(gconstpointer key)
|
||||
@ -3402,6 +3405,10 @@ static void fuse_lo_data_cleanup(struct lo_data *lo)
|
||||
if (lo->inodes) {
|
||||
g_hash_table_destroy(lo->inodes);
|
||||
}
|
||||
|
||||
if (lo->root.posix_locks) {
|
||||
g_hash_table_destroy(lo->root.posix_locks);
|
||||
}
|
||||
lo_map_destroy(&lo->fd_map);
|
||||
lo_map_destroy(&lo->dirp_map);
|
||||
lo_map_destroy(&lo->ino_map);
|
||||
|
Loading…
Reference in New Issue
Block a user