Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

fix the treatment of jfs special inodes

Browse source 
We used to put them on a single list, without any locking.  Racy.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
This commit is contained in:
Al Viro 2008-12-29 07:40:31 -05:00
parent d8e9650dff
commit 5b45d96bf9
1 changed files with 7 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
fs/jfs/jfs_imap.c
View file

@ -58,9 +58,9 @@
/* /*
* __mark_inode_dirty expects inodes to be hashed. Since we don't want * __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 * imap locks
@ -496,7 +496,11 @@ struct inode *diReadSpecial(struct super_block *sb, ino_t inum, int secondary)
/* release the page */ /* release the page */
release_metapage(mp); 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); return (ip);
} }