Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp5085766pxv; Tue, 20 Jul 2021 19:10:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx/iLeIN0zA8v+11YhJB7XfxingduGLJFNFOjHRAQkYQMxirJzjXPNV+EbuAEtC6KNPIEOj X-Received: by 2002:a05:6638:144e:: with SMTP id l14mr28927002jad.69.1626833407544; Tue, 20 Jul 2021 19:10:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626833407; cv=none; d=google.com; s=arc-20160816; b=o8Z+OKf93QlwsTpTLUo+ZvOuhuKSlC/TJhb+15eXwtaNuu//uFhDJzqtO0aEb3E245 1wV7ORGRqgMSVmsrDxdBLNk04rmvbK5acBkgs+FuYDaGAgt43Y4VLw/NYpBOf0sPMY+w H+8QeXITBphu15ayEjAqi2lD7al8mZjYAYlLMj6zd7f9ajn+kgkXisFDOx8wc5bYPEXl qW0+KKXvNcmCfeiKXpXJDZPIfYwYDIvchkeCC+eZ/TlUAhqme5yS/zYx2jc6lPRHmMzT 7RT8Skk1yA1kCzzNLSwtWuW4zI//LuoIUK043B4MmFqT3JCwHSaLsEDIStEbv+34pfYq WM2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:from:subject:message-id:date:mime-version; bh=BPKz6WUtZGu1ul8xqamvY69r2GX73FKLNjyfnpjJrOc=; b=s43ueAHvoxocwdmYq9u/EPjeFrqG1KaXHEFdhbyMxvFdWgq0QIujaOUWoWMjjaSj7c bnUl5z3SUtqWyY7abkH9O3Aiqe4hdPTDX3eMttOsO+GT5QFx4EB0Gaez9ALBkLWsBaVE EenB5CaRkNBCfRwhniA7VTyfnF03gppNLMMF8Bn8qar4+v4s1UOVs/zxOTlZjCHqXFQ4 g2UsBZa5x4Gr6gGunaC/Bc5/YGvOmg7DB5hlvm4dLlDwhi0QGp7ydhGFEmCLe/HjQLys kxv58FZaXaqy8U5OCRynBmsX5FKSmze9tGr0qJexf/FXBTuU/cZwix4i2yBgLl4UarCq ov0w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w4si29416642iov.14.2021.07.20.19.09.56; Tue, 20 Jul 2021 19:10:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230381AbhGUB0w (ORCPT + 99 others); Tue, 20 Jul 2021 21:26:52 -0400 Received: from mail-il1-f200.google.com ([209.85.166.200]:47655 "EHLO mail-il1-f200.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230020AbhGUB0t (ORCPT ); Tue, 20 Jul 2021 21:26:49 -0400 Received: by mail-il1-f200.google.com with SMTP id c7-20020a92b7470000b0290205c6edd752so714615ilm.14 for ; Tue, 20 Jul 2021 19:07:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=BPKz6WUtZGu1ul8xqamvY69r2GX73FKLNjyfnpjJrOc=; b=Fh/AyC64p1jXWDqAzdQCgEuLUgXyMu91Mj+iygbVdsek6Xpo6VqMF+TUcEIXNsK9BH yHT4LeZN2SsY9T0buo8paHLZe8Q8k4dGpaP0ELNYaauV65FfqaVQ0heG8L0xww5xttFT s4GhE+Ezj0n+oIMSy4Gl3ikyGYgGFI1VEb6XUXiRpmMkHj8FkB9lHKDoPEtO7QP0tfBp QGBlmjaE4ymX/EGuH2SYQUfQEV2WGGh1UOF/ybiKxWfL2CtnlJgy/V558Ee7qr1A38Ms 9Clow99zDf7yiAPzZh79UJLFS6BScZQXO0U9wYME0QKpb6fP7adLGB3FMSN8s2WO80W8 4mtw== X-Gm-Message-State: AOAM5306k8rIKeuUz3PykS3DLnLzuyHjSFaf+S3a54SKZWRH9b4z6Qqv ilvvWSA9H9kcsYKO5c3AGadJDO2v9vgL1Jq6p8N+bum1lsjQ MIME-Version: 1.0 X-Received: by 2002:a6b:e90b:: with SMTP id u11mr17586212iof.134.1626833245328; Tue, 20 Jul 2021 19:07:25 -0700 (PDT) Date: Tue, 20 Jul 2021 19:07:25 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000b25bb805c798a1a5@google.com> Subject: [syzbot] WARNING in __set_page_dirty From: syzbot To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.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, syzbot found the following issue on: HEAD commit: d936eb238744 Revert "Makefile: Enable -Wimplicit-fallthrou.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1512834a300000 kernel config: https://syzkaller.appspot.com/x/.config?x=f1b998c1afc13578 dashboard link: https://syzkaller.appspot.com/bug?extid=0d5b462a6f07447991b3 userspace arch: i386 Unfortunately, I don't have any reproducer for this issue yet. IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+0d5b462a6f07447991b3@syzkaller.appspotmail.com ------------[ cut here ]------------ WARNING: CPU: 0 PID: 8696 at include/linux/backing-dev.h:283 inode_to_wb include/linux/backing-dev.h:283 [inline] WARNING: CPU: 0 PID: 8696 at include/linux/backing-dev.h:283 account_page_dirtied mm/page-writeback.c:2435 [inline] WARNING: CPU: 0 PID: 8696 at include/linux/backing-dev.h:283 __set_page_dirty+0xace/0x1070 mm/page-writeback.c:2483 Modules linked in: CPU: 0 PID: 8696 Comm: syz-executor.0 Not tainted 5.14.0-rc1-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 RIP: 0010:inode_to_wb include/linux/backing-dev.h:283 [inline] RIP: 0010:account_page_dirtied mm/page-writeback.c:2435 [inline] RIP: 0010:__set_page_dirty+0xace/0x1070 mm/page-writeback.c:2483 Code: a8 01 00 00 be ff ff ff ff 48 8d 78 70 e8 0a bf 8c 07 31 ff 89 c3 89 c6 e8 3f af d8 ff 85 db 0f 85 ac f7 ff ff e8 f2 a7 d8 ff <0f> 0b e9 a0 f7 ff ff e8 e6 a7 d8 ff 4c 8d 75 08 48 b8 00 00 00 00 RSP: 0000:ffffc90000e578a0 EFLAGS: 00010093 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff888013d71c40 RSI: ffffffff819cdfce RDI: 0000000000000003 RBP: ffffea0001de0240 R08: 0000000000000000 R09: ffff888019819e07 R10: ffffffff819cdfc1 R11: 0000000000000000 R12: 0000000000000293 R13: ffff888078a38c90 R14: ffff888019819e00 R15: ffff888019819c58 FS: 0000000000000000(0000) GS:ffff88802ca00000(0063) knlGS:0000000009b20380 CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 CR2: 00007fd805161390 CR3: 000000004c16a000 CR4: 0000000000150ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: mark_buffer_dirty+0x49a/0x5e0 fs/buffer.c:1108 gfs2_unpin+0x123/0xd10 fs/gfs2/lops.c:111 buf_lo_after_commit+0x140/0x210 fs/gfs2/lops.c:750 lops_after_commit fs/gfs2/lops.h:49 [inline] gfs2_log_flush+0x162b/0x2940 fs/gfs2/log.c:1108 do_sync+0x5ab/0xcd0 fs/gfs2/quota.c:967 gfs2_quota_sync+0x2e2/0x660 fs/gfs2/quota.c:1310 gfs2_sync_fs+0x40/0xb0 fs/gfs2/super.c:711 __sync_filesystem fs/sync.c:39 [inline] sync_filesystem fs/sync.c:64 [inline] sync_filesystem+0x105/0x260 fs/sync.c:48 generic_shutdown_super+0x70/0x370 fs/super.c:448 kill_block_super+0x97/0xf0 fs/super.c:1395 gfs2_kill_sb+0x104/0x160 fs/gfs2/ops_fstype.c:1682 deactivate_locked_super+0x94/0x160 fs/super.c:335 deactivate_super+0xad/0xd0 fs/super.c:366 cleanup_mnt+0x3a2/0x540 fs/namespace.c:1136 task_work_run+0xdd/0x1a0 kernel/task_work.c:164 tracehook_notify_resume include/linux/tracehook.h:189 [inline] exit_to_user_mode_loop kernel/entry/common.c:175 [inline] exit_to_user_mode_prepare+0x27e/0x290 kernel/entry/common.c:209 __syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline] syscall_exit_to_user_mode+0x19/0x60 kernel/entry/common.c:302 __do_fast_syscall_32+0x72/0xf0 arch/x86/entry/common.c:181 do_fast_syscall_32+0x2f/0x70 arch/x86/entry/common.c:203 entry_SYSENTER_compat_after_hwframe+0x4d/0x5c RIP: 0023:0xf7f86549 Code: 03 74 c0 01 10 05 03 74 b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00 RSP: 002b:00000000ffeb89bc EFLAGS: 00000296 ORIG_RAX: 0000000000000034 RAX: 0000000000000000 RBX: 00000000ffeb8a60 RCX: 0000000000000002 RDX: 000000000816c000 RSI: 0000000000000000 RDI: 00000000080ea118 RBP: 00000000ffeb8a60 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 --- 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.