public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: yangerkun <yangerkun@huawei.com>
To: Mauricio Oliveira <mauricio.oliveira@canonical.com>
Cc: "Theodore Y . Ts'o" <tytso@mit.edu>, <adilger.kernel@dilger.ca>,
	Jan Kara <jack@suse.cz>, <linux-ext4@vger.kernel.org>,
	"zhangyi (F)" <yi.zhang@huawei.com>, Hou Tao <houtao1@huawei.com>,
	<zhangxiaoxu5@huawei.com>, Ye Bin <yebin10@huawei.com>,
	<hejie3@huawei.com>
Subject: Re: [Bug report] journal data mode trigger panic in jbd2_journal_commit_transaction
Date: Thu, 19 Nov 2020 12:25:08 +0800	[thread overview]
Message-ID: <c4c16548-1f37-a63e-de38-de5812bcc97e@huawei.com> (raw)
In-Reply-To: <CAO9xwp12E1wjErfX-Ef6+OKnme_ENOx22Hh=44g9cLn7aBr3-w@mail.gmail.com>



在 2020/11/16 21:50, Mauricio Oliveira 写道:
> Hi Kun,
> 
> On Sat, Nov 14, 2020 at 5:18 AM yangerkun <yangerkun@huawei.com> wrote:
>> While using ext4 with data=journal(3.10 kernel), we meet a problem that
>> we think may never happend...
> [...]
> 
> Could you please confirm you mean 5.10-rc* kernel instead of 3.10?
> (It seems so as you mention a recent commit below.)  Thanks!
> 
>> For now, what I have seen that can dirty buffer directly is
>> ext4_page_mkwrite(64a9f1449950 ("ext4: data=journal: fixes for
>> ext4_page_mkwrite()")), and runing ext4_punch_hole with keep_size
>> /ext4_page_mkwrite parallel can trigger above warning easily.
> [...]
> 
> 

Hi,

Sorry for the long delay reply... And thanks a lot for your advise! The 
bug trigger with a very low probability. So won't trigger with 5.10 can 
not prove no bug exist in 5.10.

Google a lot and notice that someone before has report the same bug[1]. 
'3b136499e906 ("ext4: fix data corruption in data=journal mode")' seems 
fix the problem. I will try to understand this, and give a analysis 
about how to reproduce it!

Thanks,
Kun.

  reply	other threads:[~2020-11-19  4:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14  8:18 [Bug report] journal data mode trigger panic in jbd2_journal_commit_transaction yangerkun
2020-11-16 13:50 ` Mauricio Oliveira
2020-11-19  4:25   ` yangerkun [this message]
2020-11-19 13:12     ` Mauricio Oliveira
2020-11-20  2:54       ` yangerkun
2020-11-20  3:03         ` yangerkun
2020-11-20 13:14         ` Mauricio Oliveira

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=c4c16548-1f37-a63e-de38-de5812bcc97e@huawei.com \
    --to=yangerkun@huawei.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=hejie3@huawei.com \
    --cc=houtao1@huawei.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mauricio.oliveira@canonical.com \
    --cc=tytso@mit.edu \
    --cc=yebin10@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=zhangxiaoxu5@huawei.com \
    /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