Commit 5b45d96b authored by Al Viro's avatar Al Viro
Browse files

fix the treatment of jfs special inodes



We used to put them on a single list, without any locking.  Racy.
Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
parent d8e9650d
......@@ -58,9 +58,9 @@
/*
* __mark_inode_dirty expects inodes to be hashed. Since we don't want
* special inodes in the fileset inode space, we hash them to a dummy head
* special inodes in the fileset inode space, we make them appear hashed,
* but do not put on any lists.
*/
static HLIST_HEAD(aggregate_hash);
/*
* imap locks
......@@ -496,7 +496,11 @@ struct inode *diReadSpecial(struct super_block *sb, ino_t inum, int secondary)
/* release the page */
release_metapage(mp);
hlist_add_head(&ip->i_hash, &aggregate_hash);
/*
* that will look hashed, but won't be on any list; hlist_del()
* will work fine and require no locking.
*/
ip->i_hash.pprev = &ip->i_hash.next;
return (ip);
}
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment