TAKE 987246 - Unlock inode before calling xfs

To:	sgi.bugs.xfs@xxxxxxxxxxxx, xfs@xxxxxxxxxxx
Subject:	TAKE 987246 - Unlock inode before calling xfs_idestroy()
From:	lachlan@xxxxxxx (Lachlan McIlroy)
Date:	Mon, 22 Sep 2008 18:11:40 +1000 (EST)
Sender:	xfs-bounce@xxxxxxxxxxx

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()

<Prev in Thread]	Current Thread	[Next in Thread>
TAKE 987246 - Unlock inode before calling xfs_idestroy(), Lachlan McIlroy <=

Previous by Date:	Re: [PATCH V2] Unlock inode before calling xfs_idestroy(), Christoph Hellwig
Next by Date:	[PATCH 0/10] freeze feature ver 1.12, Takashi Sato
Previous by Thread:	[PATCH] Fix race in xfs_write() between direct and buffered I/O with DMAPI, Lachlan McIlroy
Next by Thread:	[PATCH 0/10] freeze feature ver 1.12, Takashi Sato
Indexes:	[Date] [Thread] [Top] [All Lists]

TAKE 987246 - Unlock inode before calling xfs_idestroy()