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  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, 27 Jul 2020 20:41:21 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 207729] Mounting EXT4 with data_err=abort does not abort
 journal on data block write failure

https://bugzilla.kernel.org/show_bug.cgi?id=207729

--- Comment #3 from Anthony Rebello (rebello.anthony@...il.com) ---
Hi Jan,

Thank you for your reply.

I've changed the workload to perform appends rather than in-place updates.

Appending sufficient data will cause a new block to be allocated.

On fsync, this newly allocated data block will be written out and in ordered
mode,
the journal entry will contain the block bitmap (with the bit set for the newly
allocated block) and the inode table that maps the offset to this block.

In this particular case, if `data_err=abort` is enabled, the journal should
abort when it fails to write the newly allocated data block.

However, that doesn't seem to be the case. I've attached an updated TGZ
containing the append workload.

The bitmap has the block set, the inode table still points to the block, but
the block has not been overwritten with the intended data. It still contains
it's old contents.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

Powered by blists - more mailing lists