linux-kernel - [syzbot] upstream boot error: WARNING: locking bug in __anon_vma

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <000000000000623d9a05e657af56@google.com>
Date:   Tue, 16 Aug 2022 01:39:22 -0700
From:   syzbot <syzbot+80f7b10866c848183bb6@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, llvm@...ts.linux.dev,
        syzkaller-bugs@...glegroups.com
Subject: [syzbot] upstream boot error: WARNING: locking bug in __anon_vma_prepare

Hello,

syzbot found the following issue on:

HEAD commit:    4a9350597aff Merge tag 'sound-fix-6.0-rc1' of git://git.ke..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=106daf73080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4757943c2b26daff
dashboard link: https://syzkaller.appspot.com/bug?extid=80f7b10866c848183bb6
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2

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

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 0 PID: 1099 at kernel/locking/lockdep.c:231 check_wait_context kernel/locking/lockdep.c:4727 [inline]
WARNING: CPU: 0 PID: 1099 at kernel/locking/lockdep.c:231 __lock_acquire+0xac2/0x1f60 kernel/locking/lockdep.c:5003
Modules linked in:
CPU: 0 PID: 1099 Comm: kworker/u4:5 Not tainted 5.19.0-syzkaller-14090-g4a9350597aff #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:hlock_class kernel/locking/lockdep.c:231 [inline]
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4727 [inline]
RIP: 0010:__lock_acquire+0xac2/0x1f60 kernel/locking/lockdep.c:5003
Code: bc 0c 00 0f 85 2b fa ff ff 31 db 48 c7 c7 60 74 ad 8a 48 c7 c6 00 77 ad 8a 31 c0 e8 98 12 e8 ff 48 ba 00 00 00 00 00 fc ff df <0f> 0b e9 25 fa ff ff e8 22 c7 c8 02 85 c0 0f 84 b1 06 00 00 48 c7
RSP: 0000:ffffc9000468f528 EFLAGS: 00010046
RAX: cd292025beaed200 RBX: 0000000000000000 RCX: ffff888020338000
RDX: dffffc0000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff816d56dd R09: fffff520008d1e21
R10: fffff520008d1e21 R11: 1ffff920008d1e20 R12: 0000000000040000
R13: ffff888020338000 R14: 00000000000413c1 R15: ffff888020338ae8
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000ca8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5666
 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
 _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
 spin_lock include/linux/spinlock.h:349 [inline]
 __anon_vma_prepare+0x198/0x400 mm/rmap.c:209
 anon_vma_prepare include/linux/rmap.h:156 [inline]
 do_anonymous_page+0xe4e/0x1150 mm/memory.c:4082
 handle_pte_fault mm/memory.c:4909 [inline]
 __handle_mm_fault mm/memory.c:5053 [inline]
 handle_mm_fault+0x186b/0x35c0 mm/memory.c:5151
 faultin_page mm/gup.c:955 [inline]
 __get_user_pages+0x516/0x1230 mm/gup.c:1195
 __get_user_pages_locked mm/gup.c:1399 [inline]
 __get_user_pages_remote+0x1c2/0x750 mm/gup.c:2109
 get_arg_page fs/exec.c:222 [inline]
 copy_string_kernel+0x286/0x510 fs/exec.c:639
 kernel_execve+0x5cb/0xa00 fs/exec.c:1993
 call_usermodehelper_exec_async+0x262/0x3b0 kernel/umh.c:112
 ret_from_fork+0x1f/0x30
 </TASK>


---
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.