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: Thu, 13 Dec 2018 03:42:23 +0000 [thread overview]
Message-ID: <bug-201911-202145-RUWhOo2Qr4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201911-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201911
Jaegeuk Kim (jaegeuk@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jaegeuk@kernel.org
--- Comment #3 from Jaegeuk Kim (jaegeuk@kernel.org) ---
I suspect it's caused by HW encryption.
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git/commit/?h=linux-4.9.y&id=3d571474ab517bc05cd79e91735861c7e7918681
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev&id=9bf1a3f73927492c8be127b642197125e9d52be8
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2018-12-13 3:42 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 ` [Bug 201911] " bugzilla-daemon
2018-12-11 1:14 ` bugzilla-daemon
2018-12-13 3:42 ` bugzilla-daemon [this message]
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-RUWhOo2Qr4@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).