From 4aa0d230c2cfc1ac4bcf7c5466f9943cf14233a9 Mon Sep 17 00:00:00 2001 From: Dave Kleikamp Date: Wed, 17 Jan 2007 21:18:35 -0600 Subject: JFS: call io_schedule() instead of schedule() to avoid deadlock The introduction of Jens Axboe's explicit i/o plugging patches introduced a deadlock in jfs. This was caused by the process initiating I/O not unplugging the queue before waiting on the commit thread. The commit thread itself was waiting for that I/O to complete. Calling io_schedule() rather than schedule() unplugs the I/O queue avoiding the deadlock, and it appears to be the right function to call in any case. Signed-off-by: Dave Kleikamp --- fs/jfs/jfs_lock.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'fs/jfs/jfs_lock.h') diff --git a/fs/jfs/jfs_lock.h b/fs/jfs/jfs_lock.h index 7d78e83d7c4..df48ece4b7a 100644 --- a/fs/jfs/jfs_lock.h +++ b/fs/jfs/jfs_lock.h @@ -42,7 +42,7 @@ do { \ if (cond) \ break; \ unlock_cmd; \ - schedule(); \ + io_schedule(); \ lock_cmd; \ } \ current->state = TASK_RUNNING; \ -- cgit v1.2.3