[XFS] Use KM_NOFS for debug trace buffers
authorLachlan McIlroy <lachlan@sgi.com>
Wed, 13 Aug 2008 06:51:57 +0000 (16:51 +1000)
committerLachlan McIlroy <lachlan@redback.melbourne.sgi.com>
Wed, 13 Aug 2008 06:51:57 +0000 (16:51 +1000)
commit5695ef46ef02ba1c6658daa46e6879a2d4f52f5f
tree885687ac9cdbba4717f01eef26195fd4eef2ee90
parentd62c251fe4a06144255291cffd68cbadf3bf002f
[XFS] Use KM_NOFS for debug trace buffers

Use KM_NOFS to prevent recursion back into the filesystem which can cause
deadlocks.

In the case of xfs_iread() we hold the lock on the inode cluster buffer
while allocating memory for the trace buffers. If we recurse back into XFS
to flush data that may require a transaction to allocate extents which
needs log space. This can deadlock with the xfsaild thread which can't
push the tail of the log because it is trying to get the inode cluster
buffer lock.

SGI-PV: 981498

SGI-Modid: xfs-linux-melb:xfs-kern:31838a

Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
Signed-off-by: David Chinner <david@fromorbit.com>
fs/xfs/linux-2.6/xfs_buf.c
fs/xfs/quota/xfs_dquot.c
fs/xfs/xfs_buf_item.c
fs/xfs/xfs_filestream.c
fs/xfs/xfs_inode.c
fs/xfs/xfs_log.c