From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 201911] High frequency of gc cause application database corrupt
Date: Mon, 10 Dec 2018 02:55:32 +0000 [thread overview]
Message-ID: <bug-201911-202145-5jkmqb4rwE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201911-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201911
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chao@kernel.org
--- Comment #1 from Chao Yu (chao@kernel.org) ---
Sounds like that the problem was caused by GC, so could you merge below two
commits and retry the test?
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git/commit/?h=linux-4.9.y&id=1d8aac3a98acaeb102083074b67da08ec9e9d440
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git/commit/?h=linux-4.9.y&id=787485b8082e2271a01fab6f0bf267680e381bac
Or in order to make sure whether there is the same issue in last 4.9 version
kernel of AOSP, it will be better to use last f2fs codes in below branch:
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git/log/?h=linux-4.9.y
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-12-10 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 2:38 [Bug 201911] New: High frequency of gc cause application database corrupt bugzilla-daemon
2018-12-10 2:55 ` bugzilla-daemon [this message]
2018-12-11 1:14 ` [Bug 201911] " bugzilla-daemon
2018-12-13 3:42 ` bugzilla-daemon
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=bug-201911-202145-5jkmqb4rwE@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).