From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Richard Tresidder <rtresidd@electromag.com.au>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Kernel warnings 6.3.1
Date: Wed, 17 May 2023 18:08:52 -0700 [thread overview]
Message-ID: <ZGV6pOc80ITHlxXG@google.com> (raw)
In-Reply-To: <8be01849-02ae-0829-b8f0-c9eb7f3f4065@electromag.com.au>
Hi,
Could you please consider v6.3.3 which has some fixes?
Thanks,
On 05/12, Richard Tresidder via Linux-f2fs-devel wrote:
> Hi
> We're upgrading our systems from using a 5.1.7 based kernel to a 6.3.1
> based kernel.
> I'm experiencing some warnings popping out occasionally from the f2fs driver
>
> ****************************************************************************************
> [ 137.225376] WARNING: CPU: 0 PID: 32 at fs/f2fs/extent_cache.c:755
> __update_extent_tree_range+0x424/0x760
> ****************************************************************************************
>
> and a trace:
> ****************************************************************************************
> [ 460.206016] ------------[ cut here ]------------
> [ 460.208340] WARNING: CPU: 0 PID: 154 at fs/f2fs/extent_cache.c:755
> __update_extent_tree_range+0x424/0x760
> [ 460.213183] Modules linked in:
> [ 460.213200] CPU: 0 PID: 154 Comm: kworker/u4:5 Tainted: G
> W 6.3.1-00256-g60164498d86b-dirty #7
> [ 460.213216] Hardware name: Altera SOCFPGA
> [ 460.213226] Workqueue: writeback wb_workfn (flush-179:0)
> [ 460.213271] unwind_backtrace from show_stack+0x18/0x1c
> [ 460.213306] show_stack from dump_stack_lvl+0x40/0x4c
> [ 460.213335] dump_stack_lvl from __warn+0x84/0x15c
> [ 460.213365] __warn from warn_slowpath_fmt+0xc4/0x1c0
> [ 460.213391] warn_slowpath_fmt from
> __update_extent_tree_range+0x424/0x760
> [ 460.213418] __update_extent_tree_range from
> __update_extent_cache+0x244/0x444
> [ 460.213440] __update_extent_cache from
> f2fs_outplace_write_data+0x80/0xec
> [ 460.213461] f2fs_outplace_write_data from
> f2fs_do_write_data_page+0x4e4/0x700
> [ 460.213487] f2fs_do_write_data_page from
> f2fs_write_single_data_page+0x524/0x720
> [ 460.213513] f2fs_write_single_data_page from
> f2fs_write_cache_pages+0x24c/0x590
> [ 460.213539] f2fs_write_cache_pages from
> f2fs_write_data_pages+0x238/0x388
> [ 460.213563] f2fs_write_data_pages from do_writepages+0x80/0x1a4
> [ 460.213597] do_writepages from __writeback_single_inode+0x4c/0x4cc
> [ 460.213629] __writeback_single_inode from
> writeback_sb_inodes+0x1f8/0x4cc
> [ 460.213658] writeback_sb_inodes from __writeback_inodes_wb+0x40/0xe0
> [ 460.213686] __writeback_inodes_wb from wb_writeback+0x250/0x3ac
> [ 460.213713] wb_writeback from wb_workfn+0x2d4/0x5ac
> [ 460.213741] wb_workfn from process_one_work+0x1e0/0x51c
> [ 460.213776] process_one_work from worker_thread+0x60/0x518
> [ 460.213806] worker_thread from kthread+0xf4/0x124
> [ 460.213836] kthread from ret_from_fork+0x14/0x2c
> [ 460.213856] Exception stack(0xf0cc5fb0 to 0xf0cc5ff8)
> [ 460.213868] 5fa0: 00000000 00000000
> 00000000 00000000
> [ 460.213879] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000 00000000
> [ 460.213890] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
> [ 460.213899] ---[ end trace 0000000000000000 ]---
> ****************************************************************************************
>
> This is after performing a format on the device in system to make sure the
> filesystem was up to the same kernel revision.
> How concerned should we be?
>
> Note prior to the format we were getting a LOT or errors, some like above
> and others with a different signature:
>
> ****************************************************************************************
> [ 167.675107] WARNING: CPU: 0 PID: 32 at fs/f2fs/extent_cache.c:248
> __insert_extent_tree+0x15c/0x174
> ****************************************************************************************
>
> That one resulted in the entire system coming to a a halt..
>
> Cheers
> Richard T
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
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:[~2023-05-18 1:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 6:42 [f2fs-dev] Kernel warnings 6.3.1 Richard Tresidder via Linux-f2fs-devel
2023-05-18 1:08 ` Jaegeuk Kim [this message]
2023-05-25 4:44 ` Richard Tresidder via Linux-f2fs-devel
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=ZGV6pOc80ITHlxXG@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=rtresidd@electromag.com.au \
/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).