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 1B935C77B73 for ; Sun, 30 Apr 2023 08:01:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229851AbjD3IBp (ORCPT ); Sun, 30 Apr 2023 04:01:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44658 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229570AbjD3IBn (ORCPT ); Sun, 30 Apr 2023 04:01:43 -0400 Received: from mail-io1-f72.google.com (mail-io1-f72.google.com [209.85.166.72]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D5ADF2693 for ; Sun, 30 Apr 2023 01:01:41 -0700 (PDT) Received: by mail-io1-f72.google.com with SMTP id ca18e2360f4ac-769036b47a7so46459239f.0 for ; Sun, 30 Apr 2023 01:01:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682841701; x=1685433701; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=dzOY9AIDwld6DWL0ECVniyf1GhcTphj+R8EavfMT1hM=; b=NPP+LrIzQZZ61k3w62wVkcPHhpB4AItX63hkC17Rr0Fa/g2yuL+QR4LH9Gou68Uq6y USjunJz6n8uAumXqy8YZg41DmRwZp2cB2tlphnbp/Lo9Jm4z/kVWPa2KcRnKYvlyuW5U DZNan5FC/FBzm4KuuTE9smnNE1AH0WeDNRqJMPCTxzMy01EQciOnSX6YZyCj/wyNupnX BaoXsMBEQBsNtcLLdNliK95ZWtc2t13P7iLRAeAk0KcKw/JTn3KeMPvpnzz/dvkfXutN nGRjexe7k4ywRone7YB5fSq6nmaSLoR1oNZV3Q9ryF6F/SmcMmvi5xdqKOOmjywpHzaq Tc6Q== X-Gm-Message-State: AC+VfDz0/sd41/DLy4tjHuH3Lb/7RZahVECFF1rTmtnPuKxFSyA0Snf7 XKh9YqT7NAnsU+AEEHh7OETQzmH6wLn7qskg5fY6BX8weEhm X-Google-Smtp-Source: ACHHUZ68b62ZbfZNQX2uUdpv95IGImoqd3TKpsyalHK5m8wE0nSABqEuouIp+dGOocsLfYbWM4OebFpAwQ1xs3kT3Ar/ZZJ4Ccso MIME-Version: 1.0 X-Received: by 2002:a02:b10e:0:b0:40f:d134:95d with SMTP id r14-20020a02b10e000000b0040fd134095dmr4732420jah.2.1682841701223; Sun, 30 Apr 2023 01:01:41 -0700 (PDT) Date: Sun, 30 Apr 2023 01:01:41 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000d0a73c05fa891d24@google.com> Subject: [syzbot] Monthly gfs2 report (Apr 2023) From: syzbot To: cluster-devel@redhat.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello gfs2 maintainers/developers, This is a 31-day syzbot report for the gfs2 subsystem. All related reports/information can be found at: https://syzkaller.appspot.com/upstream/s/gfs2 During the period, 0 new issues were detected and 0 were fixed. In total, 19 issues are still open and 17 have been fixed so far. Some of the still happening issues: Ref Crashes Repro Title <1> 1172 Yes WARNING in __folio_mark_dirty (2) https://syzkaller.appspot.com/bug?extid=e14d6cd6ec241f507ba7 <2> 392 Yes kernel BUG in gfs2_glock_nq (2) https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80 <3> 127 Yes general protection fault in gfs2_evict_inode (2) https://syzkaller.appspot.com/bug?extid=8a5fc6416c175cecea34 <4> 35 Yes INFO: task hung in gfs2_gl_hash_clear (3) https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77 <5> 28 Yes WARNING in gfs2_check_blk_type https://syzkaller.appspot.com/bug?extid=092b28923eb79e0f3c41 <6> 23 Yes INFO: task hung in __gfs2_trans_begin https://syzkaller.appspot.com/bug?extid=a159cc6676345e04ff7d <7> 13 Yes general protection fault in gfs2_dump_glock (2) https://syzkaller.appspot.com/bug?extid=427fed3295e9a7e887f2 --- 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. To disable reminders for individual bugs, reply with the following command: #syz set no-reminders To change bug's subsystems, reply with: #syz set subsystems: new-subsystem You may send multiple commands in a single email message. From mboxrd@z Thu Jan 1 00:00:00 1970 From: syzbot Date: Sun, 30 Apr 2023 01:01:41 -0700 Subject: [Cluster-devel] [syzbot] Monthly gfs2 report (Apr 2023) Message-ID: <000000000000d0a73c05fa891d24@google.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello gfs2 maintainers/developers, This is a 31-day syzbot report for the gfs2 subsystem. All related reports/information can be found at: https://syzkaller.appspot.com/upstream/s/gfs2 During the period, 0 new issues were detected and 0 were fixed. In total, 19 issues are still open and 17 have been fixed so far. Some of the still happening issues: Ref Crashes Repro Title <1> 1172 Yes WARNING in __folio_mark_dirty (2) https://syzkaller.appspot.com/bug?extid=e14d6cd6ec241f507ba7 <2> 392 Yes kernel BUG in gfs2_glock_nq (2) https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80 <3> 127 Yes general protection fault in gfs2_evict_inode (2) https://syzkaller.appspot.com/bug?extid=8a5fc6416c175cecea34 <4> 35 Yes INFO: task hung in gfs2_gl_hash_clear (3) https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77 <5> 28 Yes WARNING in gfs2_check_blk_type https://syzkaller.appspot.com/bug?extid=092b28923eb79e0f3c41 <6> 23 Yes INFO: task hung in __gfs2_trans_begin https://syzkaller.appspot.com/bug?extid=a159cc6676345e04ff7d <7> 13 Yes general protection fault in gfs2_dump_glock (2) https://syzkaller.appspot.com/bug?extid=427fed3295e9a7e887f2 --- 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 at googlegroups.com. To disable reminders for individual bugs, reply with the following command: #syz set no-reminders To change bug's subsystems, reply with: #syz set subsystems: new-subsystem You may send multiple commands in a single email message.