general protection fault in free_percpu

6 views
Skip to first unread message

syzbot

unread,
Jan 10, 2021, 10:02:15 PM1/10/21
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c9951e5d Merge 5.4.88 into android12-5.4
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=139ee4cf500000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3cb352affb0dbcb
dashboard link: https://syzkaller.appspot.com/bug?extid=fac18df4349878ea258e
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+fac18d...@syzkaller.appspotmail.com

R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 0000000020000200 R15: 0000000020000080
kobject_add_internal failed for f2fs_xattr_entry-7:0 (error: -12 parent: slab)
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 13850 Comm: syz-executor.0 Not tainted 5.4.88-syzkaller-00116-gc9951e5d80dd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:pcpu_get_page_chunk mm/percpu.c:253 [inline]
RIP: 0010:pcpu_chunk_addr_search mm/percpu.c:1568 [inline]
RIP: 0010:free_percpu+0x265/0x900 mm/percpu.c:1972
Code: 3c 30 00 48 8b 2c 24 74 08 48 89 df e8 84 c1 0b 00 48 8b 3b 48 01 ef e8 d9 a1 06 00 48 89 c3 48 83 c3 20 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 df e8 5c c1 0b 00 4c 8b 23 4d 8d 7c 24
RSP: 0018:ffff8881e513f6c0 EFLAGS: 00010002
RAX: 0000000000000004 RBX: 0000000000000020 RCX: 0000000000040000
RDX: ffffc90001cfd000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffff1103da44c600 R08: ffffffff818e6986 R09: 0000000000000003
R10: ffffed103ca27ec5 R11: 0000000000000004 R12: ffff88823feaf7c0
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000246
FS: 00007f4b3a1fa700(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2183f76000 CR3: 00000001afed0000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__kmem_cache_release mm/slub.c:3473 [inline]
__kmem_cache_create+0x693/0x6f0 mm/slub.c:4377
create_cache+0x156/0x1f0 mm/slab_common.c:415
kmem_cache_create_usercopy+0x145/0x1d0 mm/slab_common.c:513
kmem_cache_create+0xf/0x20 mm/slab_common.c:572
f2fs_kmem_cache_create fs/f2fs/f2fs.h:2410 [inline]
f2fs_init_xattr_caches+0x156/0x230 fs/f2fs/xattr.c:799
f2fs_fill_super+0x57ba/0x9b20 fs/f2fs/super.c:3635
mount_bdev+0x22d/0x340 fs/super.c:1417
legacy_get_tree+0xde/0x170 fs/fs_context.c:647
vfs_get_tree+0x85/0x260 fs/super.c:1547
do_new_mount fs/namespace.c:2825 [inline]
do_mount+0x18ab/0x2660 fs/namespace.c:3145
ksys_mount+0xc2/0xf0 fs/namespace.c:3354
__do_sys_mount fs/namespace.c:3368 [inline]
__se_sys_mount fs/namespace.c:3365 [inline]
__x64_sys_mount+0xb1/0xc0 fs/namespace.c:3365
do_syscall_64+0xcb/0x150 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x460c6a
Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 ad 89 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 8a 89 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007f4b3a1f9a78 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f4b3a1f9b10 RCX: 0000000000460c6a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f4b3a1f9ad0
RBP: 00007f4b3a1f9ad0 R08: 00007f4b3a1f9b10 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 0000000020000200 R15: 0000000020000080
Modules linked in:
---[ end trace d2b3b97dcbdd4dfb ]---
RIP: 0010:pcpu_get_page_chunk mm/percpu.c:253 [inline]
RIP: 0010:pcpu_chunk_addr_search mm/percpu.c:1568 [inline]
RIP: 0010:free_percpu+0x265/0x900 mm/percpu.c:1972
Code: 3c 30 00 48 8b 2c 24 74 08 48 89 df e8 84 c1 0b 00 48 8b 3b 48 01 ef e8 d9 a1 06 00 48 89 c3 48 83 c3 20 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 df e8 5c c1 0b 00 4c 8b 23 4d 8d 7c 24
RSP: 0018:ffff8881e513f6c0 EFLAGS: 00010002
RAX: 0000000000000004 RBX: 0000000000000020 RCX: 0000000000040000
RDX: ffffc90001cfd000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffff1103da44c600 R08: ffffffff818e6986 R09: 0000000000000003
R10: ffffed103ca27ec5 R11: 0000000000000004 R12: ffff88823feaf7c0
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000246
FS: 00007f4b3a1fa700(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2183f76000 CR3: 00000001afed0000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Jan 10, 2021, 10:16:15 PM1/10/21
to syzkaller-a...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: c9951e5d Merge 5.4.88 into android12-5.4
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=124db248d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3cb352affb0dbcb
dashboard link: https://syzkaller.appspot.com/bug?extid=fac18df4349878ea258e
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1245aae0d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1140d0e7500000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+fac18d...@syzkaller.appspotmail.com

R13: 0000000000000005 R14: 0000000000000005 R15: 0000000000000002
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 383 Comm: syz-executor229 Not tainted 5.4.88-syzkaller-00116-gc9951e5d80dd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:pcpu_get_page_chunk mm/percpu.c:253 [inline]
RIP: 0010:pcpu_chunk_addr_search mm/percpu.c:1568 [inline]
RIP: 0010:free_percpu+0x265/0x900 mm/percpu.c:1972
Code: 3c 30 00 48 8b 2c 24 74 08 48 89 df e8 84 c1 0b 00 48 8b 3b 48 01 ef e8 d9 a1 06 00 48 89 c3 48 83 c3 20 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 df e8 5c c1 0b 00 4c 8b 23 4d 8d 7c 24
RSP: 0018:ffff8881e67276c0 EFLAGS: 00010002
RAX: 0000000000000004 RBX: 0000000000000020 RCX: ffff8881e7464d80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff1103de0ab880 R08: ffffffff818e6986 R09: 0000000000000003
R10: ffffed103cce4ec5 R11: 0000000000000004 R12: ffff88823feaf7c0
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000246
FS: 0000000001539880(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa0babcff04 CR3: 00000001df530000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__kmem_cache_release mm/slub.c:3473 [inline]
__kmem_cache_create+0x693/0x6f0 mm/slub.c:4377
create_cache+0x156/0x1f0 mm/slab_common.c:415
kmem_cache_create_usercopy+0x145/0x1d0 mm/slab_common.c:513
kmem_cache_create+0xf/0x20 mm/slab_common.c:572
f2fs_kmem_cache_create fs/f2fs/f2fs.h:2410 [inline]
f2fs_init_xattr_caches+0x156/0x230 fs/f2fs/xattr.c:799
f2fs_fill_super+0x57ba/0x9b20 fs/f2fs/super.c:3635
mount_bdev+0x22d/0x340 fs/super.c:1417
legacy_get_tree+0xde/0x170 fs/fs_context.c:647
vfs_get_tree+0x85/0x260 fs/super.c:1547
do_new_mount fs/namespace.c:2825 [inline]
do_mount+0x18ab/0x2660 fs/namespace.c:3145
ksys_mount+0xc2/0xf0 fs/namespace.c:3354
__do_sys_mount fs/namespace.c:3368 [inline]
__se_sys_mount fs/namespace.c:3365 [inline]
__x64_sys_mount+0xb1/0xc0 fs/namespace.c:3365
do_syscall_64+0xcb/0x150 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x44842a
Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 0d a3 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 ea a2 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007ffd512b9d18 EFLAGS: 00000297 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffd512b9da0 RCX: 000000000044842a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffd512b9d60
RBP: 0000000000000006 R08: 00007ffd512b9da0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000297 R12: 0000000000000002
R13: 0000000000000005 R14: 0000000000000005 R15: 0000000000000002
Modules linked in:
---[ end trace 66a212ebbaffc0a0 ]---
RIP: 0010:pcpu_get_page_chunk mm/percpu.c:253 [inline]
RIP: 0010:pcpu_chunk_addr_search mm/percpu.c:1568 [inline]
RIP: 0010:free_percpu+0x265/0x900 mm/percpu.c:1972
Code: 3c 30 00 48 8b 2c 24 74 08 48 89 df e8 84 c1 0b 00 48 8b 3b 48 01 ef e8 d9 a1 06 00 48 89 c3 48 83 c3 20 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 df e8 5c c1 0b 00 4c 8b 23 4d 8d 7c 24
RSP: 0018:ffff8881e67276c0 EFLAGS: 00010002
RAX: 0000000000000004 RBX: 0000000000000020 RCX: ffff8881e7464d80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff1103de0ab880 R08: ffffffff818e6986 R09: 0000000000000003
R10: ffffed103cce4ec5 R11: 0000000000000004 R12: ffff88823feaf7c0
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000246
FS: 0000000001539880(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa0babcff04 CR3: 00000001df530000 CR4: 00000000001406f0

syzbot

unread,
Apr 17, 2023, 12:54:33 PM4/17/23
to syzkaller-a...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages