Unlock inode before calling xfs_idestroy()
Lock debugging reported the ilock was being destroyed without being
unlocked. We don't need to lock the inode until we are going to
insert it into the radix tree.
Date: Mon Sep 22 18:10:49 AEST 2008
Workarea: redback.melbourne.sgi.com:/home/lachlan/isms/2.6.x-tot
Inspected by: hch
Author: lachlan
The following file(s) were checked into:
longdrop.melbourne.sgi.com:/isms/linux/2.6.x-xfs-melb
Modid: xfs-linux-melb:xfs-kern:32159a
fs/xfs/xfs_iget.c - 1.246 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_iget.c.diff?r1=text&tr1=1.246&r2=text&tr2=1.245&f=h
- Unlock inode before calling xfs_idestroy()
|