From: Jan Kara <jack@suse.cz>
To: tytso@mit.edu
Cc: Tao Ma <tm@tao.ma>, linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: [PATCH] jbd2: Fix forever sleeping process in do_get_write_access()
Date: Thu, 5 May 2011 14:10:39 +0200 [thread overview]
Message-ID: <1304597439-7185-1-git-send-email-jack@suse.cz> (raw)
In do_get_write_access() we wait on BH_Unshadow bit for buffer to get
from shadow state. The waking code in journal_commit_transaction() has
a bug because it does not issue a memory barrier after the buffer is moved
from the shadow state and before wake_up_bit() is called. Thus a waitqueue
check can happen before the buffer is actually moved from the shadow state
and waiting process may never be woken. Fix the problem by issuing proper
barrier.
Reported-by: Tao Ma <boyu.mt@taobao.com>
Signed-off-by: Jan Kara <jack@suse.cz>
---
fs/jbd2/commit.c | 9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)
Analogous JBD fix has been queued in my tree...
diff --git a/fs/jbd2/commit.c b/fs/jbd2/commit.c
index 2e5d370..3a958c7 100644
--- a/fs/jbd2/commit.c
+++ b/fs/jbd2/commit.c
@@ -768,8 +768,13 @@ wait_for_iobuf:
required. */
JBUFFER_TRACE(jh, "file as BJ_Forget");
jbd2_journal_file_buffer(jh, commit_transaction, BJ_Forget);
- /* Wake up any transactions which were waiting for this
- IO to complete */
+ /*
+ * Wake up any transactions which were waiting for this IO to
+ * complete. The barrier must be here so that changes by
+ * jbd2_journal_file_buffer() take effect before wake_up_bit()
+ * does the waitqueue check.
+ */
+ smp_mb();
wake_up_bit(&bh->b_state, BH_Unshadow);
JBUFFER_TRACE(jh, "brelse shadowed buffer");
__brelse(bh);
--
1.7.1
next reply other threads:[~2011-05-05 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 12:10 Jan Kara [this message]
2011-05-05 13:49 ` [PATCH] jbd2: Fix forever sleeping process in do_get_write_access() Eric Sandeen
2011-05-05 14:11 ` Jan Kara
2011-05-05 14:28 ` Eric Sandeen
2011-05-08 23:14 ` Ted Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1304597439-7185-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tm@tao.ma \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).