linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zheng Liu <gnehzuil.liu@gmail.com>
To: EUNBONG SONG <eunb.song@samsung.com>
Cc: Tony Luck <tony.luck@gmail.com>,
	Dmitry Monakhov <dmonakhov@openvz.org>,
	Theodore Ts'o <tytso@mit.edu>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Re: Re: EXT4 panic at jbd2_journal_put_journal_head() in 3.9+
Date: Mon, 13 May 2013 19:26:34 +0800	[thread overview]
Message-ID: <20130513112633.GA3168@gmail.com> (raw)
In-Reply-To: <12945098.35291368438804981.JavaMail.weblogic@epv6ml07>

On Mon, May 13, 2013 at 09:53:25AM +0000, EUNBONG SONG wrote:
> 
> 
> > Hi all,
> 
> > First of all I couldn't reproduce this regression in my sand box.  So
> > the following speculation is only my guess.  I suspect that the commit
> > (ae4647fb) isn't root cause.  It just uncover a potential bug that has
> > been there for a long time.  I look at the code, and found two
> > suspicious stuff in jbd2.  The first one is in do_get_write_access().
> > In this function we forgot to lock bh state when we check b_jlist ==
> > BJ_Shadow.  I generate a patch to fix it, and I really think it is the
> > root cause.  Further, in __journal_remove_journal_head() we check
> > b_jlist == BJ_None.  But, when this function is called, bh state won't
> > be locked sometimes.  So I suspect this is why we hit a BUG in
> > jbd2_journal_put_journal_head().  But I don't have a good solution to
> > fix this until now because I don't know whether we need to lock bh state
> > here, or maybe we should remove this assertation.
> >
> > So, generally, Tony, Eunbong, could you please try the following patch?
> >
> > Thanks in advance,
> >                                                 - Zheng
> 
> 
> Hi, I tested your patch. Unfortunately, the same problem was reproduced.
> Thanks.

Thanks for trying this patch.  Could you please repost the dmesg log for
me?  I want to make sure whether the second suspicious stuff causes this
regression or not.  Further, that would be great if you could try to
comment this line as the following?

diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
index 886ec2f..a9e3779 100644
--- a/fs/jbd2/journal.c
+++ b/fs/jbd2/journal.c
@@ -2453,7 +2453,7 @@ static void __journal_remove_journal_head(struct
buffer_head *bh)
        J_ASSERT_JH(jh, jh->b_transaction == NULL);
        J_ASSERT_JH(jh, jh->b_next_transaction == NULL);
        J_ASSERT_JH(jh, jh->b_cp_transaction == NULL);
-       J_ASSERT_JH(jh, jh->b_jlist == BJ_None);
+       /*J_ASSERT_JH(jh, jh->b_jlist == BJ_None);*/
        J_ASSERT_BH(bh, buffer_jbd(bh));
        J_ASSERT_BH(bh, jh2bh(jh) == bh);
        BUFFER_TRACE(bh, "remove journal_head");

Really thanks,
                                                - Zheng

  reply	other threads:[~2013-05-13 11:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13  9:53 Re: Re: EXT4 panic at jbd2_journal_put_journal_head() in 3.9+ EUNBONG SONG
2013-05-13 11:26 ` Zheng Liu [this message]
2013-05-13 12:07   ` Dmitry Monakhov
2013-05-13 12:54     ` Eunbong Song
  -- strict thread matches above, loose matches on Subject: below --
2013-05-13  2:21 EUNBONG SONG
2013-05-13  3:11 ` Tony Luck

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=20130513112633.GA3168@gmail.com \
    --to=gnehzuil.liu@gmail.com \
    --cc=dmonakhov@openvz.org \
    --cc=eunb.song@samsung.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@gmail.com \
    --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).