summaryrefslogtreecommitdiffstats
path: root/fs/lockd
diff options
context:
space:
mode:
authorAlex Elder <aelder@sgi.com>2011-07-11 09:51:44 -0500
committerAlex Elder <aelder@sgi.com>2011-07-11 10:21:03 -0500
commitb2ce39740066604288876c752d8170b3b17a21aa (patch)
treefd51670cea52d4c4421ce98a65e8b4979535fb97 /fs/lockd
parent81463b1ca8dbd2f4f180feac3f49c7640e2b5f79 (diff)
downloadop-kernel-dev-b2ce39740066604288876c752d8170b3b17a21aa.zip
op-kernel-dev-b2ce39740066604288876c752d8170b3b17a21aa.tar.gz
Revert "xfs: fix filesystsem freeze race in xfs_trans_alloc"
This reverts commit 7a249cf83da1813cfa71cfe1e265b40045eceb47. That commit created a situation that could lead to a filesystem hang. As Dave Chinner pointed out, xfs_trans_alloc() could hold a reference to m_active_trans (i.e., keep it non-zero) and then wait for SB_FREEZE_TRANS to complete. Meanwhile a filesystem freeze request could set SB_FREEZE_TRANS and then wait for m_active_trans to drop to zero. Nobody benefits from this sequence of events... Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Alex Elder <aelder@sgi.com>
Diffstat (limited to 'fs/lockd')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud