From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 203169] crash at fs/f2fs/checkpoint.c:160 f2fs_is_valid_blkaddr
Date: Sat, 06 Apr 2019 01:53:35 +0000 [thread overview]
Message-ID: <bug-203169-202145-bSc0QFy9B5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203169-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203169
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chao@kernel.org
--- Comment #3 from Chao Yu (chao@kernel.org) ---
I don't think this is a bug.
[ 44.217508] F2FS-fs (sdb): access invalid blkaddr:56
[ 44.217529] WARNING: CPU: 0 PID: 1036 at fs/f2fs/checkpoint.c:160
fs/f2fs/checkpoint.c:160
f2fs_is_valid_blkaddr() {
...
f2fs_msg(sbi->sb, KERN_WARNING, "access invalid blkaddr:%u", blkaddr);
WARN_ON(1);
...
}
BTW, with your image, I just hit below dmesg during mount:
[34996.986845] F2FS-fs (loop0): Invalid segment count (555819297)
[34996.986845] F2FS-fs (loop0): Can't find valid F2FS filesystem in 2th
superblock
[34996.991449] F2FS-fs (loop0): Mismatch valid blocks 0 vs. 12
[34996.991449] F2FS-fs (loop0): Failed to initialize F2FS segment manager
Are you sure, you attached the right image?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-04-06 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 1:30 [Bug 203169] New: at fs/f2fs/checkpoint.c:160 f2fs_is_valid_blkaddr bugzilla-daemon
2019-04-06 1:31 ` [Bug 203169] crash " bugzilla-daemon
2019-04-06 1:35 ` bugzilla-daemon
2019-04-06 1:36 ` bugzilla-daemon
2019-04-06 1:53 ` bugzilla-daemon [this message]
2019-04-09 19:53 ` bugzilla-daemon
2019-04-12 11:31 ` bugzilla-daemon
2019-07-12 12:00 ` [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-203169-202145-bSc0QFy9B5@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).