* [Bug 200423] Out-of-bound access in f2fs_get_dnode_of_data() when operating file on an f2fs image [not found] <bug-200423-202145@https.bugzilla.kernel.org/> @ 2018-08-26 0:20 ` bugzilla-daemon 0 siblings, 0 replies; only message in thread From: bugzilla-daemon @ 2018-08-26 0:20 UTC (permalink / raw) To: linux-f2fs-devel 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 ^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-08-26 0:20 UTC | newest] Thread overview: (only message) (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <bug-200423-202145@https.bugzilla.kernel.org/> 2018-08-26 0:20 ` [Bug 200423] Out-of-bound access in f2fs_get_dnode_of_data() when operating file on an f2fs image bugzilla-daemon
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).