linux-kernel - [syzbot] [block?] [trace?] WARNING in __blk_add

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <68fc07a0.a70a0220.3bf6c6.01aa.GAE@google.com>
Date: Fri, 24 Oct 2025 16:11:28 -0700
From: syzbot <syzbot+153e64c0aa875d7e4c37@...kaller.appspotmail.com>
To: axboe@...nel.dk, linux-block@...r.kernel.org, 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] [block?] [trace?] WARNING in __blk_add_trace

Hello,

syzbot found the following issue on:

HEAD commit:    72fb0170ef1f Add linux-next specific files for 20251024
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1640f734580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f02d98016cc9c137
dashboard link: https://syzkaller.appspot.com/bug?extid=153e64c0aa875d7e4c37
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=105853e2580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12722614580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f63074a739fa/disk-72fb0170.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b15d7b8b9621/vmlinux-72fb0170.xz
kernel image: https://storage.googleapis.com/syzbot-assets/449963b71f60/bzImage-72fb0170.xz

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

------------[ cut here ]------------
WARNING: kernel/trace/blktrace.c:368 at __blk_add_trace+0x79c/0x8d0 kernel/trace/blktrace.c:367, CPU#0: jbd2/sda1-8/5163
Modules linked in:
CPU: 0 UID: 0 PID: 5163 Comm: jbd2/sda1-8 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:__blk_add_trace+0x79c/0x8d0 kernel/trace/blktrace.c:367
Code: ff 4d 85 e4 75 4f e8 83 0e f8 ff e9 fb fd ff ff e8 79 0e f8 ff e9 ec fd ff ff e8 6f 0e f8 ff e9 d8 fd ff ff e8 65 0e f8 ff 90 <0f> 0b 90 e9 ca fd ff ff e8 57 0e f8 ff 48 8b 7c 24 30 e8 cd 51 00
RSP: 0018:ffffc9000e54f460 EFLAGS: 00010293
RAX: ffffffff81c81b4b RBX: 0000000000000001 RCX: ffff8880341abc80
RDX: 0000000000000000 RSI: 00000000901e000f RDI: 000000008000ffff
RBP: ffffc9000e54f578 R08: ffff8880341abc80 R09: 0000000000000009
R10: 0000000000000011 R11: 0000000000000000 R12: 000000008000ffff
R13: ffff888075c86080 R14: 00000000901e000f R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffff888125f22000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555577629808 CR3: 000000000dd38000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 blk_add_trace_bio_remap+0x4b8/0x560 kernel/trace/blktrace.c:1200
 __do_trace_block_bio_remap include/trace/events/block.h:526 [inline]
 trace_block_bio_remap include/trace/events/block.h:526 [inline]
 blk_partition_remap block/blk-core.c:585 [inline]
 submit_bio_noacct+0x187b/0x1b80 block/blk-core.c:804
 journal_submit_commit_record+0x665/0x8b0 fs/jbd2/commit.c:156
 jbd2_journal_commit_transaction+0x3455/0x5a00 fs/jbd2/commit.c:875
 kjournald2+0x3cf/0x750 fs/jbd2/journal.c:201
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </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