]> www.pilppa.org Git - linux-2.6-omap-h63xx.git/commit
projects / linux-2.6-omap-h63xx.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c40c202) | patch
JFS: Don't set log_SYNCBARRIER when log->active == 0
authorDave Kleikamp <shaggy@austin.ibm.com>
Mon, 25 Jul 2005 13:58:54 +0000 (08:58 -0500)
committerDave Kleikamp <shaggy@austin.ibm.com>
Mon, 25 Jul 2005 13:58:54 +0000 (08:58 -0500)
commitc2783f3a625b2aba943ef94623e277557a91a448
treee262b750f4e8cd5785417a55dd68b427e31bd86ftree | snapshot
parentc40c202493d18de42fcd0b8b5d68c22aefb70f03commit | diff
JFS: Don't set log_SYNCBARRIER when log->active == 0

If a metadata page is kept active, it is possible that the sync barrier logic
continues to trigger, even if all active transactions have been phyically
written to the journal.  This can cause a hang, since the completion of the
journal I/O is what unsets the sync barrier flag to allow new transactions
to be created.

Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
fs/jfs/jfs_logmgr.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.