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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 12 Jun 2013 22:39:11 -0400
From:	Theodore Ts'o <>
To:	Dmitry Monakhov <>
Subject: Re: [PATCH 3/3] ext4: Fix fsync error handling after filesystem

On Mon, Jun 10, 2013 at 08:41:01PM +0400, Dmitry Monakhov wrote:
> If filesystem was aborted after inode's write back is complete
> but before its metadata was updated we may return success
> results in data loss.
> In order to handle fs abort correctly we have to check
> fs state once we discover that it is in MS_RDONLY state
> Test case:
> Changes from V2:
>  - more spelling fixes
> Changes from V1:
>  - fix spelling
> Reviewed-by: Jan Kara <>
> Signed-off-by: Dmitry Monakhov <>

Thanks, applied with Darrick's further suggested spelling fixes.

		     	       	       		 - Ted
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