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]
Date:	Wed, 10 Oct 2012 13:02:52 -0400
From:	Andrey Sidorov <>
To:	"Theodore Ts'o" <>
Subject: Re: A warning from 3.6+ with bigalloc and delalloc when running xfstest

On Tue, Oct 9, 2012 at 9:51 AM, Theodore Ts'o <> wrote:

> It is indeed, something we need to fix, and it's part of the problem
> where where the delayed allocation for bigalloc is completely screwed
> up.  Part of the problem is when we write into a cluster which has not
> yet been mapped in the extent tree, but which might (or might not)
> have had other blocks in the cluster that have already been subject to
> delayed allocation, we don't know whether to reserve clusters for the
> purposes of doing the the delayed allocation accounting.  Fixing this
> w/o the extent status tree means having to search the page cache and
> for other pages in the cluster, which is not only painful, but tricky
> from the perspective of lock ordering.
> Unfortunately, I didn't notice this problem originally because I
> hadn't been doing regular xfstests runs with bigalloc, and most of my
> testing had been with direct I/O, where these issues didn't come up.
>                                 - Ted

Hi Ted,

Does it mean I'd better turn off delalloc if I use bigalloc with linux 3.5.3?

To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists