From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 200423] Out-of-bound access in f2fs_get_dnode_of_data() when operating file on an f2fs image
Date: Sun, 26 Aug 2018 00:20:25 +0000 [thread overview]
Message-ID: <bug-200423-202145-IBHdPbIFnB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200423-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200423
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |chao@kernel.org
Component|Other |f2fs
Resolution|--- |CODE_FIX
Assignee|fs_other@kernel-bugs.osdl.o |linux-f2fs-devel@lists.sour
|rg |ceforge.net
--- Comment #4 from Chao Yu (chao@kernel.org) ---
After disableing CONFIG_F2FS_CHECK_FS and do retest, below dmesg was printed:
[ 2549.717979] F2FS-fs (loop0): Invalid log blocks per segment (8)
[ 2549.717987] F2FS-fs (loop0): Can't find valid F2FS filesystem in 2th
superblock
[ 2549.718721] F2FS-fs (loop0): invalid crc_offset: 30716
[ 2549.718729] F2FS-fs (loop0): Wrong cp_pack_start_sum: 4194305
[ 2549.718738] F2FS-fs (loop0): Failed to get valid F2FS checkpoint
So I think it has been fixed by below commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e494c2f995d6181d6e29c4927d68e0f295ecf75b
--
You are receiving this mail because:
You are the assignee for the bug.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
parent reply other threads:[~2018-08-26 0:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-200423-202145@https.bugzilla.kernel.org/>]
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-200423-202145-IBHdPbIFnB@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.