From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9775AC43219 for ; Sat, 5 Nov 2022 16:08:05 +0000 (UTC) Received: from [127.0.0.1] (helo=sfs-ml-1.v29.lw.sourceforge.com) by sfs-ml-1.v29.lw.sourceforge.com with esmtp (Exim 4.95) (envelope-from ) id 1orLiC-0008VJ-Sw; Sat, 05 Nov 2022 16:08:00 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-1.v29.lw.sourceforge.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <3WIpmYwkbACkXdePFQQJWFUUNI.LTTLQJZXJWHTSYJSY.HTR@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com>) id 1orLiA-0008V4-UB for linux-f2fs-devel@lists.sourceforge.net; Sat, 05 Nov 2022 16:07:58 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Type:To:From:Subject:Message-ID:Date: MIME-Version:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=SrkMdh2rzSEfUpITUGJrHhsutoE7n5vCXPNepIr4K2k=; b=F0GyljvPEva7qDIFDC7Tk50D/q I0kMtfuWKk1mpw+yfD8ix9cVUjIGSEy4ljmgATDWtr5yQog/GykUkt1UwT1n2ro0dciS30R0Z4kks eyc+LyI0AmKL7Gf+L7ifyVt/paBg7GrnxLb4KOKlOKYv4hBtwLLqZ/D2V0grFwqOdoLU=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Type:To:From:Subject:Message-ID:Date:MIME-Version:Sender:Reply-To :Cc:Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive; bh=SrkMdh2rzSEfUpITUGJrHhsutoE7n5vCXPNepIr4K2k=; b=C du8TXNJ7PGWmX5LX+Ogn6wdFvgKZxc4bp6HWCA7ZQMBYMQKhnwK/zwccbP3FyBp4LS2DOawCshHCn lAYm9pjc2owy7G/qY2g0NytiWSuHZh1Kd3Yh3jmMifetRVYt4pcrg9WmEwmv5Crb6DpmSXqiUYBVP 8AX3ueQCQ94+AMtQ=; Received: from mail-il1-f197.google.com ([209.85.166.197]) by sfi-mx-1.v28.lw.sourceforge.com with esmtps (TLS1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.95) id 1orLiA-00D2Nr-6r for linux-f2fs-devel@lists.sourceforge.net; Sat, 05 Nov 2022 16:07:58 +0000 Received: by mail-il1-f197.google.com with SMTP id o13-20020a056e0214cd00b00300a27f9424so5822656ilk.10 for ; Sat, 05 Nov 2022 09:07:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=SrkMdh2rzSEfUpITUGJrHhsutoE7n5vCXPNepIr4K2k=; b=Ot7dIzpNtYs/gNi5tCgML+icFOcYqRDkwZMANXpHbQwiU7OP+jZVbFW9aZ6U2UAOLL qjisnAODULJlAalSr1NvHEkVBR6UkFN4F1cL0J+0SWFAkCk9O1pVi2BiCO7OKBLPdUti Sn7d9COH5np8UoggtpdG+kXuWCKe9P5dtf/9gFDv83rkCloQ5ct6rOkamJP6CH7BlIGK 1y6Z/ZWbjbosBSOnWKoQvl/l60fnyCjMIMZ40LvbnufrJRCoZAb2gHrCepeRTteTdFFK LJYtYC6wleZGl6BqKObHiQZr70IhLpl64hoDYPKIMItABN6hQafoKPY31llZ8+m1R3/t 0cTA== X-Gm-Message-State: ACrzQf2wawDUiKb771fkinRYm1hzZSmFveFxyATchLFe5srMhJSIxvnC 0LfF21IzBn6oGjYMj7uwXfU/xIzi9J29FTrWPY4de4Nan+9n X-Google-Smtp-Source: AMsMyM6ys/LYnOhuTYOgkQ7MFHH4ecac145EmKuKP9CrJkMvbn34KrtBesqKzcBYna0D2fV2xIFVycZ7w9BmJZ5cZKkPFQ2r0IDY MIME-Version: 1.0 X-Received: by 2002:a05:6638:ce:b0:373:fccb:63e3 with SMTP id w14-20020a05663800ce00b00373fccb63e3mr24202249jao.66.1667664472626; Sat, 05 Nov 2022 09:07:52 -0700 (PDT) Date: Sat, 05 Nov 2022 09:07:52 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000007edb6605ecbb6442@google.com> From: syzbot To: chao@kernel.org, jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, terrelln@fb.com X-Headers-End: 1orLiA-00D2Nr-6r Subject: [f2fs-dev] [syzbot] INFO: trying to register non-static key in f2fs_handle_error X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net Hello, syzbot found the following issue on: HEAD commit: 10d916c86eca Merge tag 'soc-fixes-6.1-2' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=117b4251880000 kernel config: https://syzkaller.appspot.com/x/.config?x=ddb381fe9a8f6a8b dashboard link: https://syzkaller.appspot.com/bug?extid=40642be9b7e0bb28e0df compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, 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/73d5475b518c/disk-10d916c8.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/2ce12d00f04a/vmlinux-10d916c8.xz kernel image: https://storage.googleapis.com/syzbot-assets/4d23719c0557/bzImage-10d916c8.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+40642be9b7e0bb28e0df@syzkaller.appspotmail.com loop1: detected capacity change from 0 to 264192 F2FS-fs (loop1): inaccessible inode: 2, run fsck to repair INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn't initialize this object before use? turning off the locking correctness validator. CPU: 1 PID: 28028 Comm: syz-executor.1 Not tainted 6.1.0-rc3-syzkaller-00239-g10d916c86eca #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 assign_lock_key+0x22a/0x240 kernel/locking/lockdep.c:981 register_lock_class+0x287/0x9b0 kernel/locking/lockdep.c:1294 __lock_acquire+0xe4/0x1f60 kernel/locking/lockdep.c:4934 lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline] _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154 spin_lock include/linux/spinlock.h:350 [inline] f2fs_save_errors fs/f2fs/super.c:3868 [inline] f2fs_handle_error+0x29/0x230 fs/f2fs/super.c:3896 f2fs_iget+0x215/0x4bb0 fs/f2fs/inode.c:516 f2fs_fill_super+0x47d3/0x7b50 fs/f2fs/super.c:4222 mount_bdev+0x26c/0x3a0 fs/super.c:1401 legacy_get_tree+0xea/0x180 fs/fs_context.c:610 vfs_get_tree+0x88/0x270 fs/super.c:1531 do_new_mount+0x289/0xad0 fs/namespace.c:3040 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f5a7388cada Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f5a74682f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f5a7388cada RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f5a74682fe0 RBP: 00007f5a74683020 R08: 00007f5a74683020 R09: 0000000020000000 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000 R13: 0000000020000100 R14: 00007f5a74682fe0 R15: 00000000200005c0 F2FS-fs (loop1): Failed to read F2FS meta data inode --- 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. _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D7DDAC4332F for ; Sat, 5 Nov 2022 16:07:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229932AbiKEQHz (ORCPT ); Sat, 5 Nov 2022 12:07:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43358 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229493AbiKEQHy (ORCPT ); Sat, 5 Nov 2022 12:07:54 -0400 Received: from mail-io1-f71.google.com (mail-io1-f71.google.com [209.85.166.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 459E310068 for ; Sat, 5 Nov 2022 09:07:53 -0700 (PDT) Received: by mail-io1-f71.google.com with SMTP id bf14-20020a056602368e00b006ce86e80414so4719223iob.7 for ; Sat, 05 Nov 2022 09:07:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=SrkMdh2rzSEfUpITUGJrHhsutoE7n5vCXPNepIr4K2k=; b=t++IHxtiYhJnZEFuXAJ01GL1iEYqFnThQBPDRRwzRrTc6tK+e9GrcPOYIZNH5f5heT GVxp+O/02TW94bleAQ7M8M5tiqTcDTfjmMLHjm7s0bYR8S1glCll+40Quf1o/Vy326rq JJYjuduPu+s+ms433pKpwbyXmQtg7ThtZhhxRMkTyDH5JsvhipU3Sdmivqn5knPIJmFf V5sgbvhVvPZMF5ScL8cETlWrW5v1GSdv9G5aQvpG8QhVqs3bZqSj/cW+TphmRtmc17j1 PY+PAnQgnFG3U4eGUFVYzuG/8WkBrhMxbC2v0jNTUZeMEiLfSsIiIfn7dKQWY7/5Fjym Z2UQ== X-Gm-Message-State: ACrzQf2XccjURid4XXp3H/+AXRDesUxzTbS7LbsTXurYuacyHtPH50yJ hw+NPy48eFQoKs4slIseaLOrDc/YuBKQXHHCkR6csHRxyjao X-Google-Smtp-Source: AMsMyM6ys/LYnOhuTYOgkQ7MFHH4ecac145EmKuKP9CrJkMvbn34KrtBesqKzcBYna0D2fV2xIFVycZ7w9BmJZ5cZKkPFQ2r0IDY MIME-Version: 1.0 X-Received: by 2002:a05:6638:ce:b0:373:fccb:63e3 with SMTP id w14-20020a05663800ce00b00373fccb63e3mr24202249jao.66.1667664472626; Sat, 05 Nov 2022 09:07:52 -0700 (PDT) Date: Sat, 05 Nov 2022 09:07:52 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000007edb6605ecbb6442@google.com> Subject: [syzbot] INFO: trying to register non-static key in f2fs_handle_error From: syzbot To: chao@kernel.org, jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, terrelln@fb.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 10d916c86eca Merge tag 'soc-fixes-6.1-2' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=117b4251880000 kernel config: https://syzkaller.appspot.com/x/.config?x=ddb381fe9a8f6a8b dashboard link: https://syzkaller.appspot.com/bug?extid=40642be9b7e0bb28e0df compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, 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/73d5475b518c/disk-10d916c8.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/2ce12d00f04a/vmlinux-10d916c8.xz kernel image: https://storage.googleapis.com/syzbot-assets/4d23719c0557/bzImage-10d916c8.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+40642be9b7e0bb28e0df@syzkaller.appspotmail.com loop1: detected capacity change from 0 to 264192 F2FS-fs (loop1): inaccessible inode: 2, run fsck to repair INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn't initialize this object before use? turning off the locking correctness validator. CPU: 1 PID: 28028 Comm: syz-executor.1 Not tainted 6.1.0-rc3-syzkaller-00239-g10d916c86eca #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 assign_lock_key+0x22a/0x240 kernel/locking/lockdep.c:981 register_lock_class+0x287/0x9b0 kernel/locking/lockdep.c:1294 __lock_acquire+0xe4/0x1f60 kernel/locking/lockdep.c:4934 lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline] _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154 spin_lock include/linux/spinlock.h:350 [inline] f2fs_save_errors fs/f2fs/super.c:3868 [inline] f2fs_handle_error+0x29/0x230 fs/f2fs/super.c:3896 f2fs_iget+0x215/0x4bb0 fs/f2fs/inode.c:516 f2fs_fill_super+0x47d3/0x7b50 fs/f2fs/super.c:4222 mount_bdev+0x26c/0x3a0 fs/super.c:1401 legacy_get_tree+0xea/0x180 fs/fs_context.c:610 vfs_get_tree+0x88/0x270 fs/super.c:1531 do_new_mount+0x289/0xad0 fs/namespace.c:3040 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f5a7388cada Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f5a74682f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f5a7388cada RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f5a74682fe0 RBP: 00007f5a74683020 R08: 00007f5a74683020 R09: 0000000020000000 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000 R13: 0000000020000100 R14: 00007f5a74682fe0 R15: 00000000200005c0 F2FS-fs (loop1): Failed to read F2FS meta data inode --- 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.