| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <000000000000ef663405c671f3a5@google.com>
Date: Tue, 06 Jul 2021 03:33:29 -0700
From: syzbot <syzbot+0fb43da032dd2c0d2dbb@...kaller.appspotmail.com>
To: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] upstream boot error: BUG: sleeping function called from
invalid context in stack_depot_save
Hello,
syzbot found the following issue on:
HEAD commit: 79160a60 Merge tag 'usb-5.14-rc1' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11052e78300000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c86f97408164ca1
dashboard link: https://syzkaller.appspot.com/bug?extid=0fb43da032dd2c0d2dbb
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0fb43da032dd2c0d2dbb@...kaller.appspotmail.com
BUG: sleeping function called from invalid context at mm/page_alloc.c:5178
in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 2, name: kthreadd
1 lock held by kthreadd/2:
#0: ffff8880b9c31660 (lock#2){....}-{2:2}, at: __alloc_pages_bulk+0x4ad/0x1870 mm/page_alloc.c:5290
irq event stamp: 1804
hardirqs last enabled at (1803): [<ffffffff81ba1f82>] slab_alloc_node mm/slab.c:3256 [inline]
hardirqs last enabled at (1803): [<ffffffff81ba1f82>] kmem_cache_alloc_node_trace+0x412/0x5d0 mm/slab.c:3617
hardirqs last disabled at (1804): [<ffffffff81b17107>] __alloc_pages_bulk+0x1017/0x1870 mm/page_alloc.c:5290
softirqs last enabled at (1716): [<ffffffff812b1cec>] memcpy include/linux/fortify-string.h:191 [inline]
softirqs last enabled at (1716): [<ffffffff812b1cec>] fpu__copy+0x16c/0x660 arch/x86/kernel/fpu/core.c:241
softirqs last disabled at (1714): [<ffffffff812b1c21>] fpu__copy+0xa1/0x660 arch/x86/kernel/fpu/core.c:229
CPU: 0 PID: 2 Comm: kthreadd Not tainted 5.13.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:79 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:96
___might_sleep.cold+0x1f1/0x237 kernel/sched/core.c:9153
prepare_alloc_pages+0x3da/0x580 mm/page_alloc.c:5178
__alloc_pages+0x12f/0x500 mm/page_alloc.c:5374
alloc_pages+0x18c/0x2a0 mm/mempolicy.c:2244
stack_depot_save+0x39d/0x4e0 lib/stackdepot.c:303
save_stack+0x15e/0x1e0 mm/page_owner.c:120
__set_page_owner+0x50/0x290 mm/page_owner.c:181
prep_new_page mm/page_alloc.c:2444 [inline]
__alloc_pages_bulk+0x8b9/0x1870 mm/page_alloc.c:5312
alloc_pages_bulk_array_node include/linux/gfp.h:557 [inline]
vm_area_alloc_pages mm/vmalloc.c:2793 [inline]
__vmalloc_area_node mm/vmalloc.c:2863 [inline]
__vmalloc_node_range+0x39d/0x960 mm/vmalloc.c:2966
alloc_thread_stack_node kernel/fork.c:245 [inline]
dup_task_struct kernel/fork.c:875 [inline]
copy_process+0x8db/0x74d0 kernel/fork.c:1952
kernel_clone+0xe7/0xac0 kernel/fork.c:2509
kernel_thread+0xb5/0xf0 kernel/fork.c:2561
create_kthread kernel/kthread.c:342 [inline]
kthreadd+0x4ea/0x750 kernel/kthread.c:685
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
============================================
WARNING: possible recursive locking detected
5.13.0-syzkaller #0 Tainted: G W
--------------------------------------------
kthreadd/2 is trying to acquire lock:
ffff8880b9c31660 (lock#2){....}-{2:2}, at: rmqueue_pcplist mm/page_alloc.c:3674 [inline]
ffff8880b9c31660 (lock#2){....}-{2:2}, at: rmqueue mm/page_alloc.c:3712 [inline]
ffff8880b9c31660 (lock#2){....}-{2:2}, at: get_page_from_freelist+0x486/0x2f80 mm/page_alloc.c:4174
but task is already holding lock:
ffff8880b9c31660 (lock#2){....}-{2:2}, at: __alloc_pages_bulk+0x4ad/0x1870 mm/page_alloc.c:5290
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(lock#2);
lock(lock#2);
*** DEADLOCK ***
May be due to missing lock nesting notation
1 lock held by kthreadd/2:
#0: ffff8880b9c31660 (lock#2){....}-{2:2}, at: __alloc_pages_bulk+0x4ad/0x1870 mm/page_alloc.c:5290
stack backtrace:
CPU: 0 PID: 2 Comm: kthreadd Tainted: G W 5.13.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:79 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:96
print_deadlock_bug kernel/locking/lockdep.c:2944 [inline]
check_deadlock kernel/locking/lockdep.c:2987 [inline]
validate_chain kernel/locking/lockdep.c:3776 [inline]
__lock_acquire.cold+0x149/0x3ab kernel/locking/lockdep.c:5015
lock_acquire kernel/locking/lockdep.c:5625 [inline]
lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5590
local_lock_acquire include/linux/local_lock_internal.h:42 [inline]
rmqueue_pcplist mm/page_alloc.c:3674 [inline]
rmqueue mm/page_alloc.c:3712 [inline]
get_page_from_freelist+0x4aa/0x2f80 mm/page_alloc.c:4174
__alloc_pages+0x1b2/0x500 mm/page_alloc.c:5385
alloc_pages+0x18c/0x2a0 mm/mempolicy.c:2244
stack_depot_save+0x39d/0x4e0 lib/stackdepot.c:303
save_stack+0x15e/0x1e0 mm/page_owner.c:120
__set_page_owner+0x50/0x290 mm/page_owner.c:181
prep_new_page mm/page_alloc.c:2444 [inline]
__alloc_pages_bulk+0x8b9/0x1870 mm/page_alloc.c:5312
alloc_pages_bulk_array_node include/linux/gfp.h:557 [inline]
vm_area_alloc_pages mm/vmalloc.c:2793 [inline]
__vmalloc_area_node mm/vmalloc.c:2863 [inline]
__vmalloc_node_range+0x39d/0x960 mm/vmalloc.c:2966
alloc_thread_stack_node kernel/fork.c:245 [inline]
dup_task_struct kernel/fork.c:875 [inline]
copy_process+0x8db/0x74d0 kernel/fork.c:1952
kernel_clone+0xe7/0xac0 kernel/fork.c:2509
kernel_thread+0xb5/0xf0 kernel/fork.c:2561
create_kthread kernel/kthread.c:342 [inline]
kthreadd+0x4ea/0x750 kernel/kthread.c:685
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
---
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 syzkaller@...glegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
Powered by blists - more mailing lists