From: Ritesh Harjani <riteshh@codeaurora.org>
To: Jeff Chua <jeff.chua.linux@gmail.com>, Chao Yu <yuchao0@huawei.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: f2fs issue on linux-5.0.0-rc2
Date: Fri, 18 Jan 2019 07:40:37 +0530 [thread overview]
Message-ID: <1ecee05b-4e6e-f916-514b-94d885670f39@codeaurora.org> (raw)
In-Reply-To: <CAAJw_Zsp2HuwuchdkjTmmh2=e+PbEeG4b7DQG47LO0mwVK8ucA@mail.gmail.com>
On 1/17/2019 5:04 PM, Jeff Chua wrote:
> On Thu, Jan 17, 2019 at 7:33 PM Jeff Chua <jeff.chua.linux@gmail.com> wrote:
>> On Thu, Jan 17, 2019 at 10:00 AM Chao Yu <yuchao0@huawei.com> wrote:
>>> On 2019/1/16 20:57, Jeff Chua wrote:
>>>> This is on rpi3b+ running latest linux git pull, and root filesystem
>>>> is "read-only" ...
>>> Did you hit this issue after you upgrade kernel from lower one to 5.0?
>> No, it was ok. Works perfectly.
>>
>>> Why there are dirty data/node in readonly filesystem?
>> No idea. It's fresh boot up.
>>
>>> Could you try below commands to make sure where it actually crash?
>>> gdb f2fs.ko
>>> l *(f2fs_balance_fs_bg+0x26c/0x2a8)
>>> l *(f2fs_build_free_nids+0x394/0x510)
>> Ok, that will take a while. I'll need to revert back to pre-5.0 and
>> install gdb first and try to debug it.
> Oh, btw, there's no "f2fs.ko" ... f2fs is compiled as built-in instead
> of a module.
you could also try using below script in kernel dir.
./scripts/faddr2line <vmlinux path> f2fs_balance_fs_bg+0x26c
./scripts/faddr2line <vmlinux path> f2fs_build_free_nids+0x394
>
> My best.,
> Jeff
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-01-18 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 12:57 f2fs issue on linux-5.0.0-rc2 Jeff Chua
2019-01-17 2:00 ` Chao Yu
2019-01-17 11:33 ` Jeff Chua
2019-01-17 11:34 ` Jeff Chua
2019-01-18 2:10 ` Ritesh Harjani [this message]
2019-01-18 8:56 ` Chao Yu
2019-01-18 14:21 ` Jeff Chua
2019-01-18 14:47 ` Jeff Chua
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=1ecee05b-4e6e-f916-514b-94d885670f39@codeaurora.org \
--to=riteshh@codeaurora.org \
--cc=jaegeuk@kernel.org \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.com \
/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).