linux-kernel - [syzbot] [trace?] WARNING in tracing_buffers_mmap

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: <675f3d4c.050a0220.37aaf.0104.GAE@google.com>
Date: Sun, 15 Dec 2024 12:34:20 -0800
From: syzbot <syzbot+ddc001b92c083dbf2b97@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, 
	mathieu.desnoyers@...icios.com, mhiramat@...nel.org, rostedt@...dmis.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [trace?] WARNING in tracing_buffers_mmap_close

Hello,

syzbot found the following issue on:

HEAD commit:    f92f4749861b Merge tag 'clk-fixes-for-linus' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d92cdf980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=99a5586995ec03b2
dashboard link: https://syzkaller.appspot.com/bug?extid=ddc001b92c083dbf2b97
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12de78f8580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17d92cdf980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b85403132ddc/disk-f92f4749.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/20613d034287/vmlinux-f92f4749.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d1ea80bf7e4e/bzImage-f92f4749.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5829 at kernel/trace/trace.c:8464 tracing_buffers_mmap_close kernel/trace/trace.c:8464 [inline]
WARNING: CPU: 1 PID: 5829 at kernel/trace/trace.c:8464 tracing_buffers_mmap_close+0xe3/0x130 kernel/trace/trace.c:8459
Modules linked in:
CPU: 1 UID: 0 PID: 5829 Comm: syz-executor210 Not tainted 6.13.0-rc2-syzkaller-00031-gf92f4749861b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:tracing_buffers_mmap_close kernel/trace/trace.c:8464 [inline]
RIP: 0010:tracing_buffers_mmap_close+0xe3/0x130 kernel/trace/trace.c:8459
Code: 75 46 48 8b 7b 08 e8 7c 85 ff ff 31 ff 89 c3 89 c6 e8 21 63 fb ff 85 db 75 0a 48 83 c4 08 5b e9 d3 60 fb ff e8 ce 60 fb ff 90 <0f> 0b 90 48 83 c4 08 5b e9 c0 60 fb ff e8 bb e7 5d 00 eb 87 e8 e4
RSP: 0018:ffffc90003857bb8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 00000000ffffffed RCX: ffffffff819ddd0f
RDX: ffff8880339f3c00 RSI: ffffffff819ddd22 RDI: 0000000000000005
RBP: 0000000000000001 R08: 0000000000000005 R09: 0000000000000000
R10: 00000000ffffffed R11: 0000000000000000 R12: ffffffff819ddc40
R13: 0000000000000001 R14: ffff88807610a548 R15: 0000000000000ff9
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f44ec4e1110 CR3: 000000000db7e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 vma_close mm/internal.h:147 [inline]
 remove_vma+0x91/0x1b0 mm/vma.c:380
 exit_mmap+0x4e2/0xb20 mm/mmap.c:1692
 __mmput+0x12a/0x4c0 kernel/fork.c:1353
 mmput+0x62/0x70 kernel/fork.c:1375
 exit_mm kernel/exit.c:570 [inline]
 do_exit+0x9bf/0x2d70 kernel/exit.c:925
 do_group_exit+0xd3/0x2a0 kernel/exit.c:1087
 __do_sys_exit_group kernel/exit.c:1098 [inline]
 __se_sys_exit_group kernel/exit.c:1096 [inline]
 __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1096
 x64_sys_call+0x151f/0x1720 arch/x86/include/generated/asm/syscalls_64.h:232
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f44ec464b49
Code: Unable to access opcode bytes at 0x7f44ec464b1f.
RSP: 002b:00007ffc68920f08 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f44ec464b49
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007f44ec4e02b0 R08: ffffffffffffffb8 R09: 0000000100000000
R10: 0000000000000012 R11: 0000000000000246 R12: 00007f44ec4e02b0
R13: 0000000000000000 R14: 00007f44ec4e0d00 R15: 00007f44ec436160
 </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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup