From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <Alexander.Levin@microsoft.com>
Cc: stable <stable@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
Chao Yu <yuchao0@huawei.com>
Subject: [4.9-stable] Revert "f2fs: do not recover from previous remained wrong dnodes"
Date: Thu, 17 Jan 2019 19:31:14 +0000 [thread overview]
Message-ID: <1547753474.3229.184.camel@codethink.co.uk> (raw)
This fix went into 4.10 and looks like it is needed for the 4.9-stable
branch:
commit d47b8715953ad0cf82bb0a9d30d7b11d83bc9c11
Author: Chao Yu <yuchao0@huawei.com>
Date: Sat Nov 5 11:12:40 2016 +0800
Revert "f2fs: do not recover from previous remained wrong dnodes"
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next reply other threads:[~2019-01-17 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 19:31 Ben Hutchings [this message]
2019-01-18 8:15 ` [4.9-stable] Revert "f2fs: do not recover from previous remained wrong dnodes" Greg Kroah-Hartman
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=1547753474.3229.184.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=Alexander.Levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=stable@vger.kernel.org \
--cc=yuchao0@huawei.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;
as well as URLs for NNTP newsgroup(s).