linux-ext4 - [Bug 194739] fallocate --collapse-range causes temporal data corruption on fragmented file

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]

Message-ID: <bug-194739-13602-8sHD4Telsc@https.bugzilla.kernel.org/>
Date:   Wed, 15 Mar 2017 17:48:30 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 194739] fallocate --collapse-range causes temporal data
 corruption on fragmented file

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

Ivan Kalvachev (iive@...oo.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

--- Comment #1 from Ivan Kalvachev (iive@...oo.com) ---
With kernel-4.10.2 I cannot reproduce the bug anymore.

The following commit looks like it might be the one fixing the issue:
---
commit 011fe6ade610c2ca5a609c83c509f1fc8e4c8b7f
Author: Roman Pen <roman.penyaev@...fitbricks.com>
Date:   Sun Jan 8 21:00:35 2017 -0500

    ext4: do not polute the extents cache while shifting extents

    commit 03e916fa8b5577d85471452a3d0c5738aa658dae upstream.

    Inside ext4_ext_shift_extents() function ext4_find_extent() is called
    without EXT4_EX_NOCACHE flag, which should prevent cache population.

    This leads to oudated offsets in the extents tree and wrong blocks
    afterwards.

    Patch fixes the problem providing EXT4_EX_NOCACHE flag for each
    ext4_find_extents() call inside ext4_ext_shift_extents function.

    Fixes: 331573febb6a2
---

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