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 X-Spam-Level: X-Spam-Status: No, score=-3.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DDB64C4338F for ; Sun, 25 Jul 2021 08:18:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B46F060F13 for ; Sun, 25 Jul 2021 08:18:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230240AbhGYHh5 (ORCPT ); Sun, 25 Jul 2021 03:37:57 -0400 Received: from mail-il1-f199.google.com ([209.85.166.199]:33725 "EHLO mail-il1-f199.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229853AbhGYHh4 (ORCPT ); Sun, 25 Jul 2021 03:37:56 -0400 Received: by mail-il1-f199.google.com with SMTP id d6-20020a056e020506b0290208fe58bd16so3116618ils.0 for ; Sun, 25 Jul 2021 01:18:27 -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=U24W+LfChl+ScshcLF966qUWOmPFa41pDXZunhLFn7k=; b=W9oEK+NJYMve7dkJ2n8cBG6VXLa6C962lLgyIBV6jwsqqmrUU/2a910UnHc5SMW7Uk Bg9dKHQCx7xku9Zy1wCMYZJVfRSF1lS2fgiV1ujCbSOezR5gAGIgxmw+JG//w5QnoT6c n2ywGMPfJTEFQsQJm6UKfKTIz6HVHYXoHQvrREpM2ziXUnevRiLMygwIegbcTXT7hal+ u588N6MrUAv8t+NA7V44U/IAGNJ1yoClnWtrPgEVsq8AF/UgMKn0gReLqzrtuWxKFhjz Qc9Yxtmyy5gfv7cE+uJCzVBFna8WHTE3jAMHM8ebI8iEksnVnklN+komjPnbEam1d1eu 78fw== X-Gm-Message-State: AOAM532RmoKDmko79vrYBfIH49gmyKYNFHWWA0FvvcwVLDISIYIr45uj oGXlrjyd0X1zLK4b9dK6ouVLLhzlFrA2d3g2NbinCnqOmyJm X-Google-Smtp-Source: ABdhPJwPh1rW6+9TDbNXJ+G3eA0T9qT0uLflBCJfoYcyJN+Ou2esZn5HyHslFLH2GQVvII0GqUH6LSnT8Qo9iKYDIfFfSiDkYQFY MIME-Version: 1.0 X-Received: by 2002:a6b:e90b:: with SMTP id u11mr10297028iof.134.1627201107150; Sun, 25 Jul 2021 01:18:27 -0700 (PDT) Date: Sun, 25 Jul 2021 01:18:27 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000f84cad05c7ee4778@google.com> Subject: [syzbot] BUG: sleeping function called from invalid context in folio_copy 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: b1347210b01d Add linux-next specific files for 20210721 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=1417aeca300000 kernel config: https://syzkaller.appspot.com/x/.config?x=86c6d14fadc3db60 dashboard link: https://syzkaller.appspot.com/bug?extid=bb4c69145b4a52b40b27 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1202e6ca300000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12ca875a300000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+bb4c69145b4a52b40b27@syzkaller.appspotmail.com BUG: sleeping function called from invalid context at mm/util.c:761 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1660, name: kcompactd0 1 lock held by kcompactd0/1660: #0: ffff8880111a4f70 (&mapping->private_lock){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:359 [inline] #0: ffff8880111a4f70 (&mapping->private_lock){+.+.}-{2:2}, at: __buffer_migrate_page+0x3a8/0xa80 mm/migrate.c:722 Preemption disabled at: [<0000000000000000>] 0x0 CPU: 0 PID: 1660 Comm: kcompactd0 Not tainted 5.14.0-rc2-next-20210721-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:105 ___might_sleep.cold+0x1f3/0x239 kernel/sched/core.c:9182 folio_copy+0x10c/0x1a0 mm/util.c:761 folio_migrate_copy+0x19/0x30 mm/migrate.c:619 __buffer_migrate_page+0x820/0xa80 mm/migrate.c:757 move_to_new_page+0x339/0xf00 mm/migrate.c:904 __unmap_and_move mm/migrate.c:1069 [inline] unmap_and_move mm/migrate.c:1210 [inline] migrate_pages+0x2867/0x3890 mm/migrate.c:1487 compact_zone+0x1abb/0x3860 mm/compaction.c:2393 kcompactd_do_work+0x2c9/0x730 mm/compaction.c:2808 kcompactd+0x262/0xd10 mm/compaction.c:2903 kthread+0x3e5/0x4d0 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 BUG: sleeping function called from invalid context at mm/util.c:761 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1660, name: kcompactd0 1 lock held by kcompactd0/1660: #0: ffff8880111a4f70 (&mapping->private_lock){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:359 [inline] #0: ffff8880111a4f70 (&mapping->private_lock){+.+.}-{2:2}, at: __buffer_migrate_page+0x3a8/0xa80 mm/migrate.c:722 Preemption disabled at: [<0000000000000000>] 0x0 CPU: 0 PID: 1660 Comm: kcompactd0 Tainted: G W 5.14.0-rc2-next-20210721-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:105 ___might_sleep.cold+0x1f3/0x239 kernel/sched/core.c:9182 folio_copy+0x10c/0x1a0 mm/util.c:761 folio_migrate_copy+0x19/0x30 mm/migrate.c:619 __buffer_migrate_page+0x820/0xa80 mm/migrate.c:757 move_to_new_page+0x339/0xf00 mm/migrate.c:904 __unmap_and_move mm/migrate.c:1069 [inline] unmap_and_move mm/migrate.c:1210 [inline] migrate_pages+0x2867/0x3890 mm/migrate.c:1487 compact_zone+0x1abb/0x3860 mm/compaction.c:2393 kcompactd_do_work+0x2c9/0x730 mm/compaction.c:2808 kcompactd+0x262/0xd10 mm/compaction.c:2903 kthread+0x3e5/0x4d0 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 --- 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. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches