All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 202495] oops in fs/f2fs/checkpoint.c:150 f2fs_is_valid_blkaddr
Date: Mon, 18 Feb 2019 18:56:11 +0000	[thread overview]
Message-ID: <bug-202495-202145-0p6BmvjuN1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202495-202145@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202495

--- Comment #4 from JWalker (jw7779@gmail.com) ---
Hi Chao,
I’ve applied all incremental patches up to, including 4.14.101. I can also
confirm that my build is a %100 match between the .xz file on kernel.org (
with respect to fs/* ).
Yes , totally repeatable. Actually it appears to panic about 8 times on
reboot.
Also the panic is not kernel version specific as I’ve tried multiple kernel
versions. Same result. I’ve also reformatted a new sdcard, tar’d up all the
data on the old card, and transferred to the new one, and all is fine.
One other separate issue, should the
/sys/fs/f2fs/mmcblkXpY/lifetime_write_kbytes work in 4.14? Mine doesn’t,
but I have seen it work in Ubuntu 18.4 with 4.15 kernel. On reboot values
return to 0.

Hope this helps
John

On Mon, 18 Feb 2019 at 01:30, <bugzilla-daemon@bugzilla.kernel.org> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=202495
>
> --- Comment #3 from Chao Yu (chao@kernel.org) ---
> (In reply to JWalker from comment #2)
> > Hi Chao,
> >
> > The kernal code was taken from the raspberry pi git repo, and then the
> > incremental patches applied.
>
> What patches do you applied? some fixing patches?
>
> >
> > Yes, fsck has been applied. Please see below the output of the both
> volumes.
> >
> > Please let me know if you require any more info.
>
> ...
>
> > [FSCK] Unreachable nat entries                        [Ok..] [0x0]
> > [FSCK] SIT valid block bitmap checking                [Ok..]
> > [FSCK] Hard link checking for regular file            [Ok..] [0x1]
> > [FSCK] valid_block_count matching with CP             [Ok..] [0x87a0]
> > [FSCK] valid_node_count matcing with CP (de lookup)   [Ok..] [0x107b]
> > [FSCK] valid_node_count matcing with CP (nat lookup)  [Ok..] [0x107b]
> > [FSCK] valid_inode_count matched with CP              [Ok..] [0x1073]
> > [FSCK] free segment_count matched with CP             [Ok..] [0x296]
> > [FSCK] next block offset is free                      [Ok..]
> > [FSCK] fixing SIT types
> > [FSCK] other corrupted bugs                           [Ok..]
>
> I didn't see any corruption there, does this image still panic your kernel?
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  parent reply	other threads:[~2019-02-18 18:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-02 15:48 [Bug 202495] New: oops in fs/f2fs/checkpoint.c:150 f2fs_is_valid_blkaddr bugzilla-daemon
2019-02-15  8:28 ` [Bug 202495] " bugzilla-daemon
2019-02-15 18:54 ` bugzilla-daemon
2019-02-18  1:30 ` bugzilla-daemon
2019-02-18 18:56 ` bugzilla-daemon [this message]
2019-03-18 23:26 ` bugzilla-daemon
2019-07-17  2:08 ` [f2fs-dev] " bugzilla-daemon
2019-07-17 20:56 ` bugzilla-daemon
2019-07-18  1:00 ` 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-202495-202145-0p6BmvjuN1@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.