linux-kernel - [syzbot] WARNING in __handle_mm

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: <00000000000085d60f05bd1c481f@google.com>
Date:   Tue, 09 Mar 2021 07:34:17 -0800
From:   syzbot <syzbot+ce14a1f8667e17a759a5@...kaller.appspotmail.com>
To:     boqun.feng@...il.com, linux-kernel@...r.kernel.org,
        longman@...hat.com, mingo@...hat.com, peterz@...radead.org,
        syzkaller-bugs@...glegroups.com, will@...nel.org
Subject: [syzbot] WARNING in __handle_mm_fault (2)

Hello,

syzbot found the following issue on:

HEAD commit:    144c79ef Merge tag 'perf-tools-fixes-for-v5.12-2020-03-07'..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14747f1ed00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3c825a7b7b408394
dashboard link: https://syzkaller.appspot.com/bug?extid=ce14a1f8667e17a759a5

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+ce14a1f8667e17a759a5@...kaller.appspotmail.com

------------[ cut here ]------------
raw_local_irq_restore() called with IRQs enabled
WARNING: CPU: 0 PID: 8390 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x1d/0x20 kernel/locking/irqflag-debug.c:10
Modules linked in:
CPU: 0 PID: 8390 Comm: syz-fuzzer Not tainted 5.12.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:warn_bogus_irq_restore+0x1d/0x20 kernel/locking/irqflag-debug.c:10
Code: be ff cc cc cc cc cc cc cc cc cc cc cc 80 3d bd 36 af 04 00 74 01 c3 48 c7 c7 a0 8f 6b 89 c6 05 ac 36 af 04 01 e8 87 ba be ff <0f> 0b c3 48 39 77 10 0f 84 97 00 00 00 66 f7 47 22 f0 ff 74 4b 48
RSP: 0000:ffffc90001b77ac8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff8880320435a0 RCX: 0000000000000000
RDX: ffff888025c20040 RSI: ffffffff815c0ef5 RDI: fffff5200036ef4b
RBP: 0000000000000200 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff815b9c5e R11: 0000000000000000 R12: 0000000000000003
R13: ffffed10064086b4 R14: 0000000000000001 R15: ffff8880b9c36000
FS:  000000c00002e490(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c0002d4020 CR3: 000000001927f000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Call Trace:
 __handle_mm_fault+0xeeb/0x4f70 mm/memory.c:4445
 handle_mm_fault+0x1bc/0x7e0 mm/memory.c:4549
RIP: 0033:0x46d4d4
RAX: 0000000000000080 RBX: 0000000000011f60 RCX: 000000c0002e6000
RDX: 0000000000827a04 RSI: 000000c0002d4020 RDI: 000000c0004aa020
R10: 000000c00048c000 R11: 0000000000000020 R12: 00000000000000fa


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