From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 200635] Oops error in refresh_sit_entry() while unmounting a crafted F2FS image
Date: Sun, 26 Aug 2018 01:54:00 +0000 [thread overview]
Message-ID: <bug-200635-202145-xArlskvARY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200635-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200635
--- Comment #4 from Chao Yu (chao@kernel.org) ---
Thanks for reminding that, IMO, yes, after we enable superblock checksum
feature, we can know which sb is corrupted, and try to recovery corrupted sb
with another good one.
Although, for your case, I guess the only corrupted field is
f2fs_super_block.cp_payload, which should be 0 instead of 1, as it can be
correctly hinted from checkpoint package fields that are under checksum
protection already.
So, w/o sb checksum feature, do you wish that we can have a try with recovering
sb fields from checkpoint pack?
--
You are receiving this mail because:
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-08-26 2:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-200635-202145@https.bugzilla.kernel.org/>
2018-08-23 15:26 ` [Bug 200635] Oops error in refresh_sit_entry() while unmounting a crafted F2FS image bugzilla-daemon
2018-08-24 10:21 ` bugzilla-daemon
2018-08-24 18:42 ` bugzilla-daemon
2018-08-24 18:55 ` bugzilla-daemon
2018-08-26 1:54 ` bugzilla-daemon [this message]
2018-08-26 23:22 ` bugzilla-daemon
2018-08-28 14:11 ` bugzilla-daemon
2018-09-05 16:44 ` bugzilla-daemon
2018-09-06 2:11 ` 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-200635-202145-xArlskvARY@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).