linux-ext4 - Re: Ext4 test failures -- COLLAPSE_RANGE and ZERO

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: <CAKYAXd-iCCYTqvKNSytpM0z_3=KnV+=LwQKS6e=kBf5T2wQ-0A@mail.gmail.com>
Date:	Fri, 4 Apr 2014 23:46:21 +0900
From:	Namjae Jeon <linkinjeon@...il.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	Lukas Czerner <lczerner@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: Ext4 test failures -- COLLAPSE_RANGE and ZERO_RANGE

2014-04-04 3:47 GMT+09:00, Theodore Ts'o <tytso@....edu>:
> Hi Lukas, Namjae,
>
> During final testing, I found two problems.  One is that the mount
> option dioread_nolock is causing a test failure for ext4/001, which is
> a ZERO_RANGE test.
>
> The other is that the mount option data=journal is cuasing a test
> failure for shared/002 and shared/004, which are COLLAPSE_RANGE bugs.
>
> Since these aren't regressions, and I don't think these new fallocate
> modes will probably be widely used at least initially, I don't think
> it's worth it to drop these two patches, especialy since we've done
> all of our testing for this merge window with the tests present.
> However, I'd really appreicate it if you take a look at them.
Hi Ted.
Sorry about this bug.
I will look into collapse range issue with data=journal.
And I'll also check more carefully insert range patch with the way you guided.

Thanks!
>
--
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