[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAO9xwp12E1wjErfX-Ef6+OKnme_ENOx22Hh=44g9cLn7aBr3-w@mail.gmail.com>
Date: Mon, 16 Nov 2020 10:50:18 -0300
From: Mauricio Oliveira <mauricio.oliveira@...onical.com>
To: yangerkun <yangerkun@...wei.com>
Cc: "Theodore Y . Ts'o" <tytso@....edu>, adilger.kernel@...ger.ca,
Jan Kara <jack@...e.cz>, linux-ext4@...r.kernel.org,
"zhangyi (F)" <yi.zhang@...wei.com>, Hou Tao <houtao1@...wei.com>,
zhangxiaoxu5@...wei.com, Ye Bin <yebin10@...wei.com>,
hejie3@...wei.com
Subject: Re: [Bug report] journal data mode trigger panic in jbd2_journal_commit_transaction
Hi Kun,
On Sat, Nov 14, 2020 at 5:18 AM yangerkun <yangerkun@...wei.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.
[...]
--
Mauricio Faria de Oliveira
Powered by blists - more mailing lists