Commit 3f31fddf authored by Mingming Cao's avatar Mingming Cao Committed by Linus Torvalds

jbd: fix race between free buffer and commit transaction

journal_try_to_free_buffers() could race with jbd commit transaction when
the later is holding the buffer reference while waiting for the data
buffer to flush to disk.  If the caller of journal_try_to_free_buffers()
request tries hard to release the buffers, it will treat the failure as
error and return back to the caller.  We have seen the directo IO failed
due to this race.  Some of the caller of releasepage() also expecting the
buffer to be dropped when passed with GFP_KERNEL mask to the

With this patch, if the caller is passing the __GFP_WAIT and __GFP_FS to
indicating this call could wait, in case of try_to_free_buffers() failed,
let's waiting for journal_commit_transaction() to finish commit the
current committing transaction, then try to free those buffers again.

[ coding-style fixes]
Signed-off-by: default avatarMingming Cao <>
Reviewed-by: default avatarBadari Pulavarty <>
Acked-by: default avatarJan Kara <>
Signed-off-by: default avatarAndrew Morton <>
Signed-off-by: default avatarLinus Torvalds <>
parent 9ebfbe9f
......@@ -1648,12 +1648,42 @@ out:
* journal_try_to_free_buffers() could race with journal_commit_transaction()
* The latter might still hold the a count on buffers when inspecting
* them on t_syncdata_list or t_locked_list.
* journal_try_to_free_buffers() will call this function to
* wait for the current transaction to finish syncing data buffers, before
* tryinf to free that buffer.
* Called with journal->j_state_lock held.
static void journal_wait_for_transaction_sync_data(journal_t *journal)
transaction_t *transaction = NULL;
tid_t tid;
transaction = journal->j_committing_transaction;
if (!transaction) {
tid = transaction->t_tid;
log_wait_commit(journal, tid);
* int journal_try_to_free_buffers() - try to free page buffers.
* @journal: journal for operation
* @page: to try and free
* @unused_gfp_mask: unused
* @gfp_mask: we use the mask to detect how hard should we try to release
* buffers. If __GFP_WAIT and __GFP_FS is set, we wait for commit code to
* release the buffers.
* For all the buffers on this page,
......@@ -1682,9 +1712,11 @@ out:
* journal_try_to_free_buffer() is changing its state. But that
* cannot happen because we never reallocate freed data as metadata
* while the data is part of a transaction. Yes?
* Return 0 on failure, 1 on success
int journal_try_to_free_buffers(journal_t *journal,
struct page *page, gfp_t unused_gfp_mask)
struct page *page, gfp_t gfp_mask)
struct buffer_head *head;
struct buffer_head *bh;
......@@ -1713,7 +1745,28 @@ int journal_try_to_free_buffers(journal_t *journal,
if (buffer_jbd(bh))
goto busy;
} while ((bh = bh->b_this_page) != head);
ret = try_to_free_buffers(page);
* There are a number of places where journal_try_to_free_buffers()
* could race with journal_commit_transaction(), the later still
* holds the reference to the buffers to free while processing them.
* try_to_free_buffers() failed to free those buffers. Some of the
* caller of releasepage() request page buffers to be dropped, otherwise
* treat the fail-to-free as errors (such as generic_file_direct_IO())
* So, if the caller of try_to_release_page() wants the synchronous
* behaviour(i.e make sure buffers are dropped upon return),
* let's wait for the current transaction to finish flush of
* dirty data buffers, then try to free those buffers again,
* with the journal locked.
if (ret == 0 && (gfp_mask & __GFP_WAIT) && (gfp_mask & __GFP_FS)) {
ret = try_to_free_buffers(page);
return ret;
......@@ -2563,9 +2563,8 @@ EXPORT_SYMBOL(generic_file_aio_write);
* Otherwise return zero.
* The @gfp_mask argument specifies whether I/O may be performed to release
* this page (__GFP_IO), and whether the call may block (__GFP_WAIT).
* this page (__GFP_IO), and whether the call may block (__GFP_WAIT & __GFP_FS).
* NOTE: @gfp_mask may go away, and this function may become non-blocking.
int try_to_release_page(struct page *page, gfp_t gfp_mask)
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment