From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-il1-f208.google.com (mail-il1-f208.google.com [209.85.166.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 57F34172BD5 for ; Mon, 27 Jan 2025 07:56:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.208 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737964590; cv=none; b=uQy9B1T+PsHAh+DaJiCgvvJijONQIdcMsZ9eVxgHf5cvI5m7rSlfqqgpGJyFgLiR2KcldOioIj3x9/Z2YR6tU+jNqRwy952zB0NdTkGvyCFbwWjrYelN204OSBdHri3OqxGstAAD2ZOvx1ZTZo+jKyakWtMqOSsIi/ZnkldQm18= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737964590; c=relaxed/simple; bh=21zewh14uhjdUYIk77A2TMEqGx2ULta4K0FwNUQpraE=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=dz9rU75+OUabtNyuR7WnoVaFRIrYPqttg2yLJUoNGS2TrdcFxaW6Oa9bdZEu/8mtvzMdfCg/w0wqSBAknchSo5BcYsVn7g2pw6L7M99dYEmzveJ1h0d+fol5emE+v8r/4kCpAS7wlUVTbJar4AUt9V/JXtJVjv0ccWsDSxvyAn8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.166.208 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-il1-f208.google.com with SMTP id e9e14a558f8ab-3a9c9b37244so75595965ab.1 for ; Sun, 26 Jan 2025 23:56:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737964587; x=1738569387; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=hJcB7Kr/MyGcTqRVm2CC+tjRLzd0VrcBipQTfCjD3gM=; b=ubp/0jTKUUwDuVMj4Xks8Yj1R2a1dj+q571/Dn6Ajusk6Ushmw3tQTXKY2Ss0efsrG u+Bj/JsLHOPNodVG0RS2Y8OXFvYPa71g8zPV/Cr8/SsV42s4sCuKM5wxrCzDRAbmBc0F th4TOG7KIrwJwRKkh1pcNru2ho3/nBA86C3bs79xLq0MsdjfGw3Zv9hjQF0IHotqvGVX Pw7vCGgYdA5S0k4oHwA+d+2yFCiHQAUtBI20bBuiBcVtau9Xx2mhYbUANKB1BogIFyEQ i6UBURYedbaUJkrdtwTKRAEfb8UihQlLzrE5tYnGer2DH/qXMXRIMTjGYAGliPsy5eSL 1HLQ== X-Forwarded-Encrypted: i=1; AJvYcCWXyAMaXPoiaSbIWqr5cO8U70SS3SzJ/7DJLtAU8LTsr3Yfg9HAsPc7MGIX9bHf34s+hzBsR+EPGV5++7Q=@vger.kernel.org X-Gm-Message-State: AOJu0YwdT+/cbzDhOabX8ayNHogu89cHTcsYExQQC++0Ky+WEojB6jzz sPo3HTKmZN0tfLtaO1hicUiMnhUjjRb8AWxFEagiNjh2npWZ8jGizK3d7gW2dNxudwCLuHjntBe oZBlstVGR6atTSlA0A3UAXQUODhBpNULfOKaqeTs1Ssz2TbqVBn9z6s0= X-Google-Smtp-Source: AGHT+IGOhcSC4/+e0ekoStNGl5inEYUNQoGUudSGvUzDLwM1ViRAAYMRdPfoeRKOH7yYKUS8nunoyEl3MHhqp6n8wj6MmMTABlrC Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1c23:b0:3ce:8ed9:ca94 with SMTP id e9e14a558f8ab-3cf744905d8mr339180105ab.14.1737964587474; Sun, 26 Jan 2025 23:56:27 -0800 (PST) Date: Sun, 26 Jan 2025 23:56:27 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <67973c2b.050a0220.11b1bb.0089.GAE@google.com> Subject: [syzbot] [f2fs?] BUG: unable to handle kernel paging request in has_enough_free_secs From: syzbot To: chao@kernel.org, jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: df60eac9efe8 Merge tag 'for-linus-6.14-1' of https://githu.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10e14a38580000 kernel config: https://syzkaller.appspot.com/x/.config?x=e56f16478dfabb4 dashboard link: https://syzkaller.appspot.com/bug?extid=b6b347b7a4ea1b2e29b6 compiler: Debian clang version 15.0.6, 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/c42a22eab378/disk-df60eac9.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/e8d947efbb6a/vmlinux-df60eac9.xz kernel image: https://storage.googleapis.com/syzbot-assets/0225eaefda10/bzImage-df60eac9.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+b6b347b7a4ea1b2e29b6@syzkaller.appspotmail.com F2FS-fs (loop3): Stopped filesystem due to reason: 7 kworker/u8:7: attempt to access beyond end of device loop3: rw=1, sector=45096, nr_sectors = 8 limit=40427 BUG: unable to handle page fault for address: ffffed1604ea3dfa #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 23ffee067 P4D 23ffee067 PUD 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 0 UID: 0 PID: 2977 Comm: kworker/u8:7 Not tainted 6.13.0-syzkaller-04541-gdf60eac9efe8 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024 Workqueue: writeback wb_workfn (flush-7:3) RIP: 0010:get_ckpt_valid_blocks fs/f2fs/segment.h:361 [inline] RIP: 0010:has_curseg_enough_space fs/f2fs/segment.h:570 [inline] RIP: 0010:__get_secs_required fs/f2fs/segment.h:620 [inline] RIP: 0010:has_not_enough_free_secs fs/f2fs/segment.h:633 [inline] RIP: 0010:has_enough_free_secs+0x575/0x1660 fs/f2fs/segment.h:649 Code: 3c 08 00 74 12 48 89 ef e8 88 30 0d fe 48 b9 00 00 00 00 00 fc ff df 4b 8d 1c 7f 48 c1 e3 04 48 03 5d 00 48 89 d8 48 c1 e8 03 <0f> b6 04 08 84 c0 0f 85 bc 02 00 00 44 0f b7 63 02 41 81 e4 ff 03 RSP: 0018:ffffc9000baa7268 EFLAGS: 00010a06 RAX: 1ffff11604ea3dfa RBX: ffff88b02751efd0 RCX: dffffc0000000000 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001 RBP: ffff888028c058e8 R08: ffffffff83f643f7 R09: 1ffff110037e6a00 R10: dffffc0000000000 R11: ffffed10037e6a01 R12: 1ffff110037e682e R13: ffff88801bf34170 R14: 0000000000000001 R15: 00000000ffffffff FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffed1604ea3dfa CR3: 0000000033f0a000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: f2fs_is_checkpoint_ready fs/f2fs/segment.h:671 [inline] f2fs_write_inode+0x425/0x540 fs/f2fs/inode.c:791 write_inode fs/fs-writeback.c:1525 [inline] __writeback_single_inode+0x708/0x10d0 fs/fs-writeback.c:1745 writeback_sb_inodes+0x820/0x1360 fs/fs-writeback.c:1976 wb_writeback+0x413/0xb80 fs/fs-writeback.c:2156 wb_do_writeback fs/fs-writeback.c:2303 [inline] wb_workfn+0x410/0x1080 fs/fs-writeback.c:2343 process_one_work kernel/workqueue.c:3236 [inline] process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3317 worker_thread+0x870/0xd30 kernel/workqueue.c:3398 kthread+0x7a9/0x920 kernel/kthread.c:464 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Modules linked in: CR2: ffffed1604ea3dfa ---[ end trace 0000000000000000 ]--- RIP: 0010:get_ckpt_valid_blocks fs/f2fs/segment.h:361 [inline] RIP: 0010:has_curseg_enough_space fs/f2fs/segment.h:570 [inline] RIP: 0010:__get_secs_required fs/f2fs/segment.h:620 [inline] RIP: 0010:has_not_enough_free_secs fs/f2fs/segment.h:633 [inline] RIP: 0010:has_enough_free_secs+0x575/0x1660 fs/f2fs/segment.h:649 Code: 3c 08 00 74 12 48 89 ef e8 88 30 0d fe 48 b9 00 00 00 00 00 fc ff df 4b 8d 1c 7f 48 c1 e3 04 48 03 5d 00 48 89 d8 48 c1 e8 03 <0f> b6 04 08 84 c0 0f 85 bc 02 00 00 44 0f b7 63 02 41 81 e4 ff 03 RSP: 0018:ffffc9000baa7268 EFLAGS: 00010a06 RAX: 1ffff11604ea3dfa RBX: ffff88b02751efd0 RCX: dffffc0000000000 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001 RBP: ffff888028c058e8 R08: ffffffff83f643f7 R09: 1ffff110037e6a00 R10: dffffc0000000000 R11: ffffed10037e6a01 R12: 1ffff110037e682e R13: ffff88801bf34170 R14: 0000000000000001 R15: 00000000ffffffff FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffed1604ea3dfa CR3: 0000000033f0a000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 ---------------- Code disassembly (best guess): 0: 3c 08 cmp $0x8,%al 2: 00 74 12 48 add %dh,0x48(%rdx,%rdx,1) 6: 89 ef mov %ebp,%edi 8: e8 88 30 0d fe call 0xfe0d3095 d: 48 b9 00 00 00 00 00 movabs $0xdffffc0000000000,%rcx 14: fc ff df 17: 4b 8d 1c 7f lea (%r15,%r15,2),%rbx 1b: 48 c1 e3 04 shl $0x4,%rbx 1f: 48 03 5d 00 add 0x0(%rbp),%rbx 23: 48 89 d8 mov %rbx,%rax 26: 48 c1 e8 03 shr $0x3,%rax * 2a: 0f b6 04 08 movzbl (%rax,%rcx,1),%eax <-- trapping instruction 2e: 84 c0 test %al,%al 30: 0f 85 bc 02 00 00 jne 0x2f2 36: 44 0f b7 63 02 movzwl 0x2(%rbx),%r12d 3b: 41 rex.B 3c: 81 .byte 0x81 3d: e4 ff in $0xff,%al 3f: 03 .byte 0x3 --- 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@googlegroups.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