linux-ext4 - Re: [Bug report] journal data mode trigger panic in jbd2_journal_commit

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 20 Nov 2020 10:14:05 -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 Thu, Nov 19, 2020 at 11:54 PM yangerkun <yangerkun@...wei.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