mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Joseph Qi <jiangqi903@gmail.com>
Cc: Kai Li <li.kai4@h3c.com>,
	mark@fasheh.com, jlbec@evilplan.org, chge@linux.alibaba.com,
	linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH v3] ocfs2: call journal flush to mark journal as empty after journal recovery when mount
Date: Wed, 18 Dec 2019 12:56:01 +0800	[thread overview]
Message-ID: <b4bc5200-56bb-f8e4-4f9b-dfc2472a5af1@linux.alibaba.com> (raw)
In-Reply-To: <20191217182311.6696bbe6f03b5ea81bc96082@linux-foundation.org>



On 19/12/18 10:23, Andrew Morton wrote:
> On Tue, 17 Dec 2019 10:12:14 +0800 Joseph Qi <jiangqi903@gmail.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@h3c.com>
>>
>> Reviewed-by: Joseph Qi <joseph.qi@linux.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

  reply	other threads:[~2019-12-18  4:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17  2:01 Kai Li
2019-12-17  2:12 ` [Ocfs2-devel] " Joseph Qi
2019-12-18  2:23   ` Andrew Morton
2019-12-18  4:56     ` Joseph Qi [this message]
2019-12-17  2:42 ` Changwei Ge
2019-12-19 14:15 ` [Ocfs2-devel] " piaojun
2019-12-20  1:11   ` Joseph Qi
2019-12-20  9:13     ` piaojun
2019-12-20  9:33       ` Likai
2019-12-20 12:52         ` Jiangyiwen
2019-12-21  7:24           ` Changwei Ge
2019-12-23  1:54             ` Jiangyiwen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b4bc5200-56bb-f8e4-4f9b-dfc2472a5af1@linux.alibaba.com \
    --to=joseph.qi@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=chge@linux.alibaba.com \
    --cc=jiangqi903@gmail.com \
    --cc=jlbec@evilplan.org \
    --cc=li.kai4@h3c.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®