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  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:	Tue, 04 Jun 2013 09:26:28 -0500
From:	Eric Sandeen <>
To:	宋柏翰 <>
Subject: Re: Question on delalloc

On 6/3/13 2:00 PM, 宋柏翰 wrote:
> Hi everybody,
> I am new to ext4 and doing research on Android with ext4 as file
> system. These days, I have a question on ext4's delayed allocation
> against ext4_sync_file.
> I have learned that delalloc won't guarantee file data's integrity on
> power failure, since those delayed allocated buffer heads won't be
> handled by jbd2.

I just want to address your first assertion regarding delalloc:

> In order to protect data, user programs need to fsync
> those files to be secured.

This is true with or without delayed allocation.

With delayed allocation, the blocks are chosen a the time of the IO.
Without delayed allocation, the blocks are chosen at the write syscall time.

But in both cases, data is only in memory after the write(), and is not
guaranteed to be on disk until an fsync or similar data integrity syscall.

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