All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauricio Oliveira <mauricio.oliveira@canonical.com>
To: yangerkun <yangerkun@huawei.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: Fri, 20 Nov 2020 10:14:05 -0300	[thread overview]
Message-ID: <CAO9xwp1=BGpZtt4yeVicqCwascMxoJ3khG_JC9V3tpjXjOstPQ@mail.gmail.com> (raw)
In-Reply-To: <17d7ecde-5fda-cd03-6fef-e7b8250489f9@huawei.com>

Hi Kun,

On Thu, Nov 19, 2020 at 11:54 PM yangerkun <yangerkun@huawei.com> wrote:
> Hi,
>
> The follow step can reproduce the bug[1] reported before easily. And the
> bug we meet seems same. Following patch will fix the bug.
>
> 3b136499e906 ext4: fix data corruption in data=journal mode
> b90197b65518 ext4: use private version of page_zero_new_buffers() for
> data=journal mode

Since this issue is apparently on a 3.10 kernel, which is no longer
maintained upstream [see 2],
I guess you have to talk to the distro vendor about including such
patches in their kernel.

[2] https://www.kernel.org/

cheers,

-- 
Mauricio Faria de Oliveira

      parent reply	other threads:[~2020-11-20 13:14 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
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 [this message]

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='CAO9xwp1=BGpZtt4yeVicqCwascMxoJ3khG_JC9V3tpjXjOstPQ@mail.gmail.com' \
    --to=mauricio.oliveira@canonical.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=tytso@mit.edu \
    --cc=yangerkun@huawei.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.