[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4bc5200-56bb-f8e4-4f9b-dfc2472a5af1@linux.alibaba.com>
Date: Wed, 18 Dec 2019 12:56:01 +0800
From: Joseph Qi <joseph.qi@...ux.alibaba.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Joseph Qi <jiangqi903@...il.com>
Cc: Kai Li <li.kai4@....com>, mark@...heh.com, jlbec@...lplan.org,
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 19/12/18 10:23, Andrew Morton wrote:
> 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?
>
Since this is not an usual usecase, we don't have to.
It is enough to let it go into upstream.
Thanks,
Joseph
Powered by blists - more mailing lists