From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 203167] Kernel page fault with update_sit_entry+0x113/0x420
Date: Wed, 17 Apr 2019 02:34:00 +0000 [thread overview]
Message-ID: <bug-203167-202145-nDtY0EUndK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203167-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203167
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #3 from Chao Yu (chao@kernel.org) ---
I just enable valid block consistent check in check_block_count() by default,
which is enabled only CONFIG_F2FS_CHECK_FS is set previously.
f2fs: fix to do sanity check on valid block count of segment
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-04-17 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 0:50 [Bug 203167] New: Kernel page fault with update_sit_entry+0x113/0x420 bugzilla-daemon
2019-04-07 9:55 ` [Bug 203167] " bugzilla-daemon
2019-04-09 15:48 ` bugzilla-daemon
2019-04-17 2:34 ` bugzilla-daemon [this message]
2019-07-08 18:38 ` [f2fs-dev] " 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-203167-202145-nDtY0EUndK@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.