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:	Mon, 15 Jun 2015 14:47:31 -0400
From:	Theodore Ts'o <>
To:	Joseph Qi <>
	"" <>,
	Jan Kara <>,
	Andrew Morton <>,
	Mark Fasheh <>,
	Joel Becker <>,
	Junxiao Bi <>,
	jiangyiwen <>,
Subject: Re: [PATCH RESEND] jbd2: fix ocfs2 corrupt when updating journal
 superblock fails

On Mon, Jun 15, 2015 at 02:27:09PM +0800, Joseph Qi wrote:
> If updating journal superblock fails after journal data has been flushed,
> the error is omitted and this will mislead the caller as a normal case.
> In ocfs2, the checkpoint will be treated successfully and the other node
> can get the lock to update. Since the sb_start is still pointing to the
> old log block, it will rewrite the journal data during journal recovery
> by the other node. Thus the new updates will be overwritten and ocfs2
> corrupts.
> So in above case we have to return the error, and ocfs2_commit_cache will
> take care of the error and prevent the other node to do update first.
> And only after recovering journal it can do the new updates.
> The issue discussion mail can be found at:
> Reported-by: Yiwen Jiang <>
> Signed-off-by: Joseph Qi <>
> Tested-by: Yiwen Jiang <>
> Cc: Junxiao Bi <>
> Cc: <>

Thanks, applied.

					- 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