linux-ext4 - Re: [PATCH v3] jbd2: Fix potential data lost in recovering journal raced with synchronizing fs bdev

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,  6 Oct 2023 14:06:17 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     jack@...e.com, Zhihao Cheng <chengzhihao1@...wei.com>
Cc:     "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org,
        linux-kernel@...r.kernel.org, yi.zhang@...wei.com
Subject: Re: [PATCH v3] jbd2: Fix potential data lost in recovering journal raced with synchronizing fs bdev


On Tue, 19 Sep 2023 09:25:25 +0800, Zhihao Cheng wrote:
> JBD2 makes sure journal data is fallen on fs device by sync_blockdev(),
> however, other process could intercept the EIO information from bdev's
> mapping, which leads journal recovering successful even EIO occurs during
> data written back to fs device.
> 
> We found this problem in our product, iscsi + multipath is chosen for block
> device of ext4. Unstable network may trigger kpartx to rescan partitions in
> device mapper layer. Detailed process is shown as following:
> 
> [...]

Applied, thanks!

[1/1] jbd2: Fix potential data lost in recovering journal raced with synchronizing fs bdev
      commit: 61187fce8600e8ef90e601be84f9d0f3222c1206

Best regards,
-- 
Theodore Ts'o <tytso@....edu>