From: syzbot <syzbot+6087eafb76a94c4ac9eb@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: slab-out-of-bounds Write in dbgfs_rm_context_write
Date: Sun, 30 Oct 2022 22:29:22 -0700 [thread overview]
Message-ID: <000000000000d4bc4d05ec4de3e3@google.com> (raw)
In-Reply-To: <20221031044301.3651-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in dbgfs_rm_context_write
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4167 at mm/damon/dbgfs.c:928 dbgfs_rm_context mm/damon/dbgfs.c:928 [inline]
WARNING: CPU: 0 PID: 4167 at mm/damon/dbgfs.c:928 dbgfs_rm_context_write+0x40a/0x4d0 mm/damon/dbgfs.c:972
Modules linked in:
CPU: 0 PID: 4167 Comm: syz-executor.0 Not tainted 6.1.0-rc2-syzkaller-00078-g98555239e4c3-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
RIP: 0010:dbgfs_rm_context mm/damon/dbgfs.c:928 [inline]
RIP: 0010:dbgfs_rm_context_write+0x40a/0x4d0 mm/damon/dbgfs.c:972
Code: 03 42 80 3c 30 00 0f 85 d6 00 00 00 48 8b 3b e8 4c 19 ff ff 48 8b 05 a5 83 52 0f 48 89 44 24 08 e9 40 ff ff ff e8 f6 c1 a7 ff <0f> 0b e9 d0 fe ff ff e8 ea c1 a7 ff 48 8b 3c 24 49 c7 c5 f4 ff ff
RSP: 0018:ffffc900049bfcb0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff8880745d0000 RSI: ffffffff81d4da8a RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000004 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000000000 R14: dffffc0000000000 R15: ffff888144cb2000
FS: 00007f5b5b5ac700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002000f000 CR3: 000000006f407000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
full_proxy_write+0x118/0x180 fs/debugfs/file.c:236
vfs_write+0x2d7/0xdd0 fs/read_write.c:582
ksys_write+0x127/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f5b5a88b5a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5b5b5ac168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f5b5a9abf80 RCX: 00007f5b5a88b5a9
RDX: 000000000000fe6c RSI: 0000000020000080 RDI: 0000000000000003
RBP: 00007f5b5a8e67b0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe981eb0df R14: 00007f5b5b5ac300 R15: 0000000000022000
</TASK>
Tested on:
commit: 98555239 Merge tag 'arc-6.1-fixes' of git://git.kernel..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1258d3ce880000
kernel config: https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
dashboard link: https://syzkaller.appspot.com/bug?extid=6087eafb76a94c4ac9eb
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=112688a6880000
next parent reply other threads:[~2022-10-31 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221031044301.3651-1-hdanton@sina.com>
2022-10-31 5:29 ` syzbot [this message]
[not found] <20221031071038.3704-1-hdanton@sina.com>
2022-10-31 13:54 ` [syzbot] KASAN: slab-out-of-bounds Write in dbgfs_rm_context_write syzbot
2022-10-31 1:44 syzbot
2022-10-31 18:30 ` SeongJae Park
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=000000000000d4bc4d05ec4de3e3@google.com \
--to=syzbot+6087eafb76a94c4ac9eb@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 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.