WARNING: ODEBUG bug in ion_page_pool_alloc

4 views
Skip to first unread message

syzbot

unread,
Jan 24, 2021, 7:11:17 AM1/24/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2d2791fc Linux 4.14.217
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17187180d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=80753487c013c9c7
dashboard link: https://syzkaller.appspot.com/bug?extid=9fa850111fb5dfaf40fd
compiler: gcc (GCC) 10.1.0-syz 20200507

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+9fa850...@syzkaller.appspotmail.com

R13: 0000000000000000 R14: 00000000016b4350 R15: 0000000000000003
ODEBUG: assert_init not available (active state 0) object type: timer_list hint: (null)
CPU: 1 PID: 1023 Comm: syz-executor.1 Not tainted 4.14.217-syzkaller #0
------------[ cut here ]------------
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
WARNING: CPU: 0 PID: 963 at lib/debugobjects.c:287 debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
Call Trace:
Kernel panic - not syncing: panic_on_warn set ...

__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
warn_alloc.cold+0x96/0x1cc mm/page_alloc.c:3255
__alloc_pages_slowpath mm/page_alloc.c:4102 [inline]
__alloc_pages_nodemask+0x2127/0x2720 mm/page_alloc.c:4205
alloc_pages_current+0x155/0x260 mm/mempolicy.c:2113
alloc_pages include/linux/gfp.h:520 [inline]
ion_page_pool_alloc_pages drivers/staging/android/ion/ion_page_pool.c:30 [inline]
ion_page_pool_alloc+0x118/0x1b0 drivers/staging/android/ion/ion_page_pool.c:89
alloc_buffer_page drivers/staging/android/ion/ion_system_heap.c:75 [inline]
alloc_largest_available drivers/staging/android/ion/ion_system_heap.c:115 [inline]
ion_system_heap_allocate+0x133/0x8c0 drivers/staging/android/ion/ion_system_heap.c:146
ion_buffer_create drivers/staging/android/ion/ion.c:94 [inline]
ion_alloc+0x204/0x810 drivers/staging/android/ion/ion.c:425
ion_ioctl+0xea/0x1f0 drivers/staging/android/ion/ion-ioctl.c:87
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45e219
RSP: 002b:00007f90e5973c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045e219
RDX: 00000000200001c0 RSI: 00000000c0184900 RDI: 0000000000000004
RBP: 000000000119bfc0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000119bf8c
R13: 00007ffd8263e14f R14: 00007f90e59749c0 R15: 000000000119bf8c
CPU: 0 PID: 963 Comm: syz-executor.2 Not tainted 4.14.217-syzkaller #0
0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
0
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
RSP: 0018:ffff88801e86f248 EFLAGS: 00010086
RAX: 0000000000000061 RBX: 0000000000000005 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff878bbb40 RDI: ffffed1003d0de3f
RBP: ffffffff878b6e00 R08: 0000000000000061 R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880403de100 R12: 0000000000000000
R13: 0000000000000000 R14: ffff88803a1c26f0 R15: 1ffff11003d0de52
Node 0
debug_object_assert_init lib/debugobjects.c:656 [inline]
debug_object_assert_init+0x1d3/0x2d0 lib/debugobjects.c:627
debug_timer_assert_init kernel/time/timer.c:708 [inline]
debug_assert_init kernel/time/timer.c:756 [inline]
del_timer+0x5d/0xe0 kernel/time/timer.c:1151
try_to_grab_pending+0x243/0x610 kernel/workqueue.c:1225
Normal free:0kB min:4kB low:4kB high:4kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:1048576kB managed:520kB mlocked:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
__cancel_work_timer+0x90/0x460 kernel/workqueue.c:2923
batadv_nc_mesh_free+0x41/0x120 net/batman-adv/network-coding.c:1880
batadv_mesh_free+0x70/0x150 net/batman-adv/main.c:231
batadv_mesh_init+0x561/0x630 net/batman-adv/main.c:216
batadv_softif_init_late+0xa26/0xc90 net/batman-adv/soft-interface.c:856
lowmem_reserve[]:
0
register_netdevice+0x291/0xe40 net/core/dev.c:7590
0
rtnl_newlink+0x14dc/0x1830 net/core/rtnetlink.c:2742
0
rtnetlink_rcv_msg+0x3be/0xb10 net/core/rtnetlink.c:4316
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2433
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1313
0
netlink_sendmsg+0x62e/0xb80 net/netlink/af_netlink.c:1878
0
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
SYSC_sendto net/socket.c:1763 [inline]
SyS_sendto+0x1c7/0x2c0 net/socket.c:1731
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x417c97
RSP: 002b:00007ffd20d56480 EFLAGS: 00000293 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 00000000016b4300 RCX: 0000000000417c97
RDX: 000000000000003c RSI: 00000000016b4350 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007ffd20d56490 R09: 000000000000000c
Node 1
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000
R13: 0000000000000000 R14: 00000000016b4350 R15: 0000000000000003
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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,
May 25, 2021, 3:46:21 PM5/25/21
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages