Closed jaysim closed 1 year ago
when using inode cache(nidata cache) and openning multiple same inode, it may have the potential to memory leak, and it can lead to corruption.
first calling ntfs_inode_close() will put inode to cache, but second calling ntfs_inode_close() will not anything. memory leak occurred here.
when second calling ntfs_inode_close(), ie, already inode is in cache, should call do_free() which is registered in cache initialization.
Applied, Thanks!
when using inode cache(nidata cache) and openning multiple same inode, it may have the potential to memory leak, and it can lead to corruption.
first calling ntfs_inode_close() will put inode to cache, but second calling ntfs_inode_close() will not anything. memory leak occurred here.
when second calling ntfs_inode_close(), ie, already inode is in cache, should call do_free() which is registered in cache initialization.