linux-ext4 - Re: [PATCH v2 2/2] ext4: Do not populate extents tree with outdated offsets while shifting extents

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJrWOzDLhjdX=FV18Wty7bOkzD7rn_rcBUT2610O4XYqxgqpQg@mail.gmail.com>
Date:   Mon, 9 Jan 2017 13:36:50 +0100
From:   Roman Penyaev <roman.penyaev@...fitbricks.com>
To:     "Theodore Ts'o" <tytso@....edu>,
        Roman Pen <roman.penyaev@...fitbricks.com>,
        Namjae Jeon <namjae.jeon@...sung.com>,
        Andreas Dilger <adilger.kernel@...ger.ca>,
        linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] ext4: Do not populate extents tree with outdated
 offsets while shifting extents

On Sat, Jan 7, 2017 at 10:27 PM, Theodore Ts'o <tytso@....edu> wrote:
> On Fri, Jan 06, 2017 at 09:26:01PM +0100, Roman Pen wrote:
>> 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.
>>
>> Signed-off-by: Roman Pen <roman.penyaev@...fitbricks.com>
>
> Thanks, applied.

Could you please provide with the SHA1 of the patch in your branch?
I want to make an exact reference in a new test of the xfstest which
covers that bug.

--
Roman
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html