[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191217182311.6696bbe6f03b5ea81bc96082@linux-foundation.org>
Date: Tue, 17 Dec 2019 18:23:11 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Joseph Qi <jiangqi903@...il.com>
Cc: Kai Li <li.kai4@....com>, mark@...heh.com, jlbec@...lplan.org,
joseph.qi@...ux.alibaba.com, chge@...ux.alibaba.com,
linux-kernel@...r.kernel.org, ocfs2-devel@....oracle.com
Subject: Re: [Ocfs2-devel] [PATCH v3] ocfs2: call journal flush to mark
journal as empty after journal recovery when mount
On Tue, 17 Dec 2019 10:12:14 +0800 Joseph Qi <jiangqi903@...il.com> wrote:
> > Due to first commit seq 13 recorded in journal super is not consistent
> > with the value recorded in block 1(seq is 14), journal recovery will be
> > terminated before seq 15 even though it is an unbroken commit, inode
> > 8257802 is a new file and it will be lost.
> >
> > Signed-off-by: Kai Li <li.kai4@....com>
>
> Reviewed-by: Joseph Qi <joseph.qi@...ux.alibaba.com>
Do we think this fix should be backported into -stable kernels?
Powered by blists - more mailing lists