From: Jan Kara <jack@suse.cz>
To: Ted Tso <tytso@mit.edu>
Cc: Dmitry Monakhov <dmonakhov@openvz.org>,
eunb.song@samsung.com, linux-ext4@vger.kernel.org,
Jan Kara <jack@suse.cz>
Subject: [PATCH] jbd2: Fix oops in jbd2_journal_put_journal_head()
Date: Mon, 13 May 2013 15:31:56 +0200 [thread overview]
Message-ID: <1368451916-16785-1-git-send-email-jack@suse.cz> (raw)
Commit ae4647fb (jbd2: reduce journal_head size.) introduced a
regression where we occasionally hit panic in
jbd2_journal_put_journal_head() because of wrong b_jcount. The bug is
caused by gcc making 64-bit access to 32-bit bitfield and thus
clobbering b_jcount.
At least for now, those 8 bytes saved in struct journal_head are not
worth the trouble with gcc bitfield handling so revert that part of the
patch.
Reported-by: EUNBONG SONG <eunb.song@samsung.com>
Signed-off-by: Jan Kara <jack@suse.cz>
---
include/linux/journal-head.h | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
Ted, this should fix the regression reported by EUNBONG SONG. Please apply.
diff --git a/include/linux/journal-head.h b/include/linux/journal-head.h
index 13a3da2..3594c74 100644
--- a/include/linux/journal-head.h
+++ b/include/linux/journal-head.h
@@ -30,15 +30,19 @@ struct journal_head {
/*
* Journalling list for this buffer [jbd_lock_bh_state()]
+ * NOTE: We *cannot* combine this with b_modified into a bitfield
+ * as gcc would then (correctly according to C++11) make 64-bit
+ * accesses to the bitfield and clobber b_jcount if its update
+ * races with bitfield modification.
*/
- unsigned b_jlist:4;
+ unsigned b_jlist;
/*
* This flag signals the buffer has been modified by
* the currently running transaction
* [jbd_lock_bh_state()]
*/
- unsigned b_modified:1;
+ unsigned b_modified;
/*
* Copy of the buffer data frozen for writing to the log.
--
1.8.1.4
next reply other threads:[~2013-05-13 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 13:31 Jan Kara [this message]
2013-05-13 13:49 ` [PATCH] jbd2: Fix oops in jbd2_journal_put_journal_head() Theodore 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=1368451916-16785-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=dmonakhov@openvz.org \
--cc=eunb.song@samsung.com \
--cc=linux-ext4@vger.kernel.org \
--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