From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 214895] F2FS BUG: KASAN: stack-out-of-bounds in d_shrink_add+0x17f/0x1c0
Date: Sat, 11 Dec 2021 02:14:03 +0000 [thread overview]
Message-ID: <bug-214895-202145-wU765Ypjg6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214895-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214895
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #4 from Chao Yu (chao@kernel.org) ---
Oh, sorry, I guess this is a known issue which has been reported in below link
[1], please apply fixing patch [2] to see whether it can fix your problem.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=204135
[2]
https://lore.kernel.org/linux-f2fs-devel/20190712085700.4239-1-yuchao0@huawei.com/T/#u
I can't reproduce this issue due to the "runner" test program crashed in 733
line.
(gdb) r
> Make dir /root/mnt
> Begin testing syscall...
> To mount root ...
MOUNT ROOT f2fs on /root/mnt: with
[nouser_xattr,active_logs=6,inline_data,fastboot,extent_cache]
> Mount root done...
[Detaching after vfork from child process 14904]
mount(dev: /dev/loop11, g_workspace: /root/mnt, fs: f2fs, 0, option:
nouser_xattr,active_logs=6,inline_data,fastboot,extent_cache)REMOUNT ROOT f2fs
on /root/mnt: with
[discard,no_heap,active_logs=6,inline_data,flush_merge,fastboot,extent_cache,mode=adaptive]
munmap_chunk(): invalid pointer
Program received signal SIGABRT, Aborted.
0x00000000004cc56b in raise ()
(gdb) bt
#0 0x00000000004cc56b in raise ()
#1 0x0000000000403ae3 in abort ()
#2 0x00000000004e6556 in __libc_message ()
#3 0x00000000004ecaec in malloc_printerr ()
#4 0x00000000004ecd1c in munmap_chunk ()
#5 0x0000000000405943 in m_deepen (curr_path=0x5855a8
"/root/mnt/fONyUHhUjtamPfvodyYSGfoo_318/gLCxIfoo_576/tFawtTrTsddGXmDCrYIvnOmEJPwiSUPkLfMfpHlZwOnItTpnEDfoo_663/biCedwbdHbfFfoo_884",
depth=665)
at 214895.c:212
#6 0x0000000000408681 in test_syscall () at 214895.c:733
#7 0x000000000040b48c in main (argc=1, argv=0x7fffffffe388) at 214895.c:1260
(gdb) quit
A debugging session is active.
Inferior 1 [process 14896] will be killed.
--
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
next prev parent reply other threads:[~2021-12-11 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 9:03 [f2fs-dev] [Bug 214895] New: F2FS BUG: KASAN: stack-out-of-bounds in d_shrink_add+0x17f/0x1c0 bugzilla-daemon
2021-10-31 9:57 ` [f2fs-dev] [Bug 214895] " bugzilla-daemon
2021-11-01 9:41 ` bugzilla-daemon
2021-11-01 10:01 ` bugzilla-daemon
2021-12-11 2:14 ` bugzilla-daemon [this message]
2021-12-12 4:10 ` bugzilla-daemon
2021-12-12 4:11 ` bugzilla-daemon
2021-12-12 4:11 ` 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-214895-202145-wU765Ypjg6@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).