linux-kernel - [syzbot] [bcachefs?] WARNING in bch2_writepage_io

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: <6725780a.050a0220.35b515.0181.GAE@google.com>
Date: Fri, 01 Nov 2024 17:53:30 -0700
From: syzbot <syzbot+9765be6fa7d03a49a95c@...kaller.appspotmail.com>
To: kent.overstreet@...ux.dev, linux-bcachefs@...r.kernel.org, 
	linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [bcachefs?] WARNING in bch2_writepage_io_done (2)

Hello,

syzbot found the following issue on:

HEAD commit:    e42b1a9a2557 Merge tag 'spi-fix-v6.12-rc5' of git://git.ke..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14a9e940580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5ce635c2e1785fd6
dashboard link: https://syzkaller.appspot.com/bug?extid=9765be6fa7d03a49a95c
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b440ec26d97d/disk-e42b1a9a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/76f539c22a2e/vmlinux-e42b1a9a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b7fffe3fc1ad/bzImage-e42b1a9a.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 52 at fs/bcachefs/fs-io-buffered.c:419 bch2_writepage_io_done+0x857/0xd10 fs/bcachefs/fs-io-buffered.c:419
Modules linked in:
CPU: 0 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc5-syzkaller-00005-ge42b1a9a2557 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: writeback wb_workfn (flush-bcachefs-56)
RIP: 0010:bch2_writepage_io_done+0x857/0xd10 fs/bcachefs/fs-io-buffered.c:419
Code: ff e8 cd 38 82 fd 8b 84 24 88 00 00 00 48 8b 74 24 08 48 8b 7c 24 10 8d 50 01 89 04 24 e8 11 ee ff ff eb c5 e8 aa 38 82 fd 90 <0f> 0b 90 e8 a1 38 82 fd 48 8b 44 24 18 48 8d 78 f8 48 b8 00 00 00
RSP: 0018:ffffc90000bd71b0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000008 RCX: ffffffff840b3bd9
RDX: ffff888022699e00 RSI: ffffffff840b4286 RDI: 0000000000000007
RBP: 0000000000000008 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000000 R12: ffffea00004d63c0
R13: ffff88814cd81b80 R14: 0000000000000008 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7e3b046f98 CR3: 000000005dbaa000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 bch2_write_done+0x246/0x400 fs/bcachefs/io_write.c:477
 bch2_write_data_inline fs/bcachefs/io_write.c:1561 [inline]
 bch2_write+0xb42/0x14a0 fs/bcachefs/io_write.c:1630
 bch2_writepages+0x136/0x200 fs/bcachefs/fs-io-buffered.c:641
 do_writepages+0x1a6/0x7f0 mm/page-writeback.c:2683
 __writeback_single_inode+0x166/0xfa0 fs/fs-writeback.c:1658
 writeback_sb_inodes+0x603/0xfa0 fs/fs-writeback.c:1954
 __writeback_inodes_wb+0xff/0x2e0 fs/fs-writeback.c:2025
 wb_writeback+0x721/0xb50 fs/fs-writeback.c:2136
 wb_check_start_all fs/fs-writeback.c:2262 [inline]
 wb_do_writeback fs/fs-writeback.c:2288 [inline]
 wb_workfn+0x878/0xbc0 fs/fs-writeback.c:2321
 process_one_work+0x9c8/0x1ba0 kernel/workqueue.c:3229
 process_scheduled_works kernel/workqueue.c:3310 [inline]
 worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391
 kthread+0x2c4/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </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 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