lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 16 Nov 2020 10:50:18 -0300
From:   Mauricio Oliveira <>
To:     yangerkun <>
Cc:     "Theodore Y . Ts'o" <>,,
        Jan Kara <>,,
        "zhangyi (F)" <>, Hou Tao <>,, Ye Bin <>,
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 <> 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