From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 216262] New: KASAN: invalid-access in f2fs_lookup_rb_tree+0xac/0x144
Date: Wed, 20 Jul 2022 09:37:33 +0000 [thread overview]
Message-ID: <bug-216262-202145@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216262
Bug ID: 216262
Summary: KASAN: invalid-access in
f2fs_lookup_rb_tree+0xac/0x144
Product: File System
Version: 2.5
Kernel Version: 5.4.190
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: f2fs
Assignee: filesystem_f2fs@kernel-bugs.kernel.org
Reporter: lecopzer.chen@mediatek.com
Regression: No
kernel is from
https://android.googlesource.com/kernel/common/+log/refs/heads/android12-5.4
996a4638b6190fe369f1347c093c26762babd223
and this was from a stress test for 20hr and only happened for once.
I guess it's an abnormal value (race condition?) which wasn't catch by any
checking.
I couldn't find any exist commit that may solve this (if it had already fixed
please tell me, thanks).
[Wed Jul 20 00:10:57.331 2022] [ 2795.615407]
==================================================================
[Wed Jul 20 00:10:57.331 2022] [ 2795.631096] BUG: KASAN: invalid-access in
f2fs_lookup_rb_tree+0xac/0x144
[Wed Jul 20 00:10:57.331 2022] [ 2795.638520] Read of size 4 at addr
400008aa1603e211 by task f2fs_ckpt-259:1/181
[Wed Jul 20 00:10:57.331 2022] [ 2795.646529]
[Wed Jul 20 00:10:57.331 2022] [ 2795.648748] CPU: 2 PID: 181 Comm:
f2fs_ckpt-259:1 Tainted: P WC O 5.4.190-gad047c3d9ea5-dirty #1
[Wed Jul 20 00:10:57.331 2022] [ 2795.659275] Hardware name: MediaTek (DT)
[Wed Jul 20 00:10:57.331 2022] [ 2795.664513] Call trace:
[Wed Jul 20 00:10:57.331 2022] [ 2795.667688] dump_backtrace+0x0/0x220
[Wed Jul 20 00:10:57.331 2022] [ 2795.672075] show_stack+0x24/0x34
[Wed Jul 20 00:10:57.331 2022] [ 2795.676113] dump_stack+0x138/0x1b8
[Wed Jul 20 00:10:57.331 2022] [ 2795.680321] __kasan_report+0x1d8/0x320
[Wed Jul 20 00:10:57.331 2022] [ 2795.684871] kasan_report+0x14/0x20
[Wed Jul 20 00:10:57.331 2022] [ 2795.689115] __hwasan_load4_noabort+0x88/0x94
[Wed Jul 20 00:10:57.331 2022] [ 2795.694214] f2fs_lookup_rb_tree+0xac/0x144
[Wed Jul 20 00:10:57.331 2022] [ 2795.699122] f2fs_wait_discard_bio+0x7c/0x6d4
[Wed Jul 20 00:10:57.331 2022] [ 2795.704202]
f2fs_allocate_data_block+0x3dc/0x1314
[Wed Jul 20 00:10:57.331 2022] [ 2795.709712] do_write_page+0xf0/0x398
[Wed Jul 20 00:10:57.331 2022] [ 2795.714098]
f2fs_outplace_write_data+0xc8/0x2bc
[Wed Jul 20 00:10:57.331 2022] [ 2795.719440]
f2fs_do_write_data_page+0x9fc/0xe60
[Wed Jul 20 00:10:57.331 2022] [ 2795.724784]
f2fs_write_single_data_page+0x748/0xd2c
[Wed Jul 20 00:10:57.335 2022] [ 2795.730472]
f2fs_write_cache_pages+0x904/0xf78
[Wed Jul 20 00:10:57.335 2022] [ 2795.735726]
__f2fs_write_data_pages+0x558/0x91c
[Wed Jul 20 00:10:57.335 2022] [ 2795.741066] f2fs_write_data_pages+0x58/0x6c
[Wed Jul 20 00:10:57.335 2022] [ 2795.746058] do_writepages+0x9c/0x1a0
[Wed Jul 20 00:10:57.335 2022] [ 2795.750446]
__filemap_fdatawrite_range+0x1d4/0x218
[Wed Jul 20 00:10:57.335 2022] [ 2795.756045] filemap_fdatawrite+0x2c/0x3c
[Wed Jul 20 00:10:57.335 2022] [ 2795.760780] f2fs_quota_sync_file+0x94/0x1dc
[Wed Jul 20 00:10:57.335 2022] [ 2795.765775] f2fs_quota_sync+0x1a8/0x300
[Wed Jul 20 00:10:57.335 2022] [ 2795.770421] block_operations+0xcc/0x4ec
[Wed Jul 20 00:10:57.335 2022] [ 2795.775066] f2fs_write_checkpoint+0x234/0xa34
[Wed Jul 20 00:10:57.335 2022] [ 2795.780232]
__checkpoint_and_complete_reqs+0xa0/0x700
[Wed Jul 20 00:10:57.335 2022] [ 2795.786089]
issue_checkpoint_thread+0x78/0x1c4
[Wed Jul 20 00:10:57.335 2022] [ 2795.791341] kthread+0x240/0x268
[Wed Jul 20 00:10:57.335 2022] [ 2795.795295] ret_from_fork+0x10/0x18
[Wed Jul 20 00:10:57.335 2022] [ 2795.799586]
==================================================================
[Wed Jul 20 00:10:57.335 2022] [ 2795.807741] Mem abort info:
[Wed Jul 20 00:10:57.335 2022] [ 2795.807948] Unable to handle kernel paging
request at virtual address 000008aa1603e211
[Wed Jul 20 00:10:57.335 2022] [ 2795.811307] ESR = 0x96000004
[Wed Jul 20 00:10:57.335 2022] [ 2795.811323] EC = 0x25: DABT (current EL), IL
= 32 bits
--
You may reply to this email to add a comment.
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
reply other threads:[~2022-07-20 9:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-216262-202145@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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).