linux-kernel - [syzbot] kernel BUG in jbd2_journal_get_create

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: <00000000000037f6b105ed944924@google.com>
Date:   Wed, 16 Nov 2022 02:53:42 -0800
From:   syzbot <syzbot+1db57b8a1f746d42a177@...kaller.appspotmail.com>
To:     jack@...e.com, linux-ext4@...r.kernel.org,
        linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
        tytso@....edu
Subject: [syzbot] kernel BUG in jbd2_journal_get_create_access (2)

Hello,

syzbot found the following issue on:

HEAD commit:    f5020a08b2b3 Merge tag 's390-6.1-4' of git://git.kernel.or..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13dcf7a9880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=63dd4cec15ec5ea2
dashboard link: https://syzkaller.appspot.com/bug?extid=1db57b8a1f746d42a177
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2d4840e0a006/disk-f5020a08.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/da4765f2786a/vmlinux-f5020a08.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5cca8e2906ca/bzImage-f5020a08.xz

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

------------[ cut here ]------------
kernel BUG at fs/jbd2/transaction.c:1290!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 20729 Comm: kworker/u4:2 Not tainted 6.1.0-rc4-syzkaller-00308-gf5020a08b2b3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: writeback wb_workfn (flush-8:0)
RIP: 0010:jbd2_journal_get_create_access+0x36c/0x560 fs/jbd2/transaction.c:1290
Code: 85 01 02 00 00 8b 45 4c bf 02 00 00 00 89 c6 89 44 24 08 e8 26 9f 4c ff 8b 44 24 08 83 f8 02 0f 84 06 fe ff ff e8 44 a2 4c ff <0f> 0b e8 3d a2 4c ff 48 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1
RSP: 0018:ffffc900036d6db8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88814b1b6000 RCX: 0000000000000000
RDX: ffff8880569fe100 RSI: ffffffff822f322c RDI: 0000000000000005
RBP: ffff888045901870 R08: 0000000000000005 R09: 0000000000000002
R10: 0000000000000003 R11: 0000000000000000 R12: ffff88804727e6e0
R13: 0000000000000000 R14: ffff88804e841c80 R15: ffff888045901878
FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020091000 CR3: 00000000322c0000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __ext4_journal_get_create_access+0x50/0x1f0 fs/ext4/ext4_jbd2.c:323
 ext4_ext_grow_indepth fs/ext4/extents.c:1339 [inline]
 ext4_ext_create_new_leaf fs/ext4/extents.c:1435 [inline]
 ext4_ext_insert_extent+0x12ab/0x4130 fs/ext4/extents.c:2102
 ext4_ext_map_blocks+0x1541/0x6270 fs/ext4/extents.c:4308
 ext4_map_blocks+0x775/0x18d0 fs/ext4/inode.c:645
 mpage_map_one_extent fs/ext4/inode.c:2413 [inline]
 mpage_map_and_submit_extent fs/ext4/inode.c:2466 [inline]
 ext4_writepages+0x1e55/0x3da0 fs/ext4/inode.c:2834
 do_writepages+0x1ab/0x690 mm/page-writeback.c:2469
 __writeback_single_inode+0x159/0x1440 fs/fs-writeback.c:1587
 writeback_sb_inodes+0x54d/0xf90 fs/fs-writeback.c:1870
 wb_writeback+0x2c5/0xd70 fs/fs-writeback.c:2044
 wb_do_writeback fs/fs-writeback.c:2187 [inline]
 wb_workfn+0x2dc/0x12f0 fs/fs-writeback.c:2227
 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289
 worker_thread+0x665/0x1080 kernel/workqueue.c:2436
 kthread+0x2e4/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:jbd2_journal_get_create_access+0x36c/0x560 fs/jbd2/transaction.c:1290
Code: 85 01 02 00 00 8b 45 4c bf 02 00 00 00 89 c6 89 44 24 08 e8 26 9f 4c ff 8b 44 24 08 83 f8 02 0f 84 06 fe ff ff e8 44 a2 4c ff <0f> 0b e8 3d a2 4c ff 48 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1
RSP: 0018:ffffc900036d6db8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88814b1b6000 RCX: 0000000000000000
RDX: ffff8880569fe100 RSI: ffffffff822f322c RDI: 0000000000000005
RBP: ffff888045901870 R08: 0000000000000005 R09: 0000000000000002
R10: 0000000000000003 R11: 0000000000000000 R12: ffff88804727e6e0
R13: 0000000000000000 R14: ffff88804e841c80 R15: ffff888045901878
FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020091000 CR3: 00000000322c0000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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