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 64C97C4332F for ; Thu, 22 Dec 2022 22:55:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230001AbiLVWzu (ORCPT ); Thu, 22 Dec 2022 17:55:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46516 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229582AbiLVWzr (ORCPT ); Thu, 22 Dec 2022 17:55:47 -0500 Received: from mail-io1-f69.google.com (mail-io1-f69.google.com [209.85.166.69]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7043813F6A for ; Thu, 22 Dec 2022 14:55:46 -0800 (PST) Received: by mail-io1-f69.google.com with SMTP id h11-20020a6b7a0b000000b006e0004fc167so1272755iom.5 for ; Thu, 22 Dec 2022 14:55:46 -0800 (PST) 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=aXosvzq+A5vhYtuAlYzsv0/1c7zz/aBO/fowD1BzMYI=; b=WLCnS3pgdvXAYgtDcNwnrN7738SyoCuPAOtR2lSEzrNmez4z5uh3nhiBTPELUxNlde M/4lmVGWQ2UYXAqcGm9OB9N0iSvzp9fU0kIMEcqui8qq8d65KnQO759NIYLKsOW8Frt2 TIHm0cV2fcRk9SyCYAr8BdUwHGo4z/1HtmwFWUh9jqSqWml/M0/7CyUHkHuWT1OTZx57 hWXie/EqEYdAqNIcB9QMnwhmETe+RIJzGNhwWWyqKrprfZ5EswXBYpXupSgqSN72/SeS WqMbF0SbiS1Po4AwGRL4V0LdcdQT7PU/OQyQpmMt69HydsUHO9RHYufCqlYiJGORFGBe 0Mjg== X-Gm-Message-State: AFqh2kpB7/doiamGmiVJYlp6JH8h/MVUGBDpI17ofUULXPEekbpiFAbC HcYdLIgj8bN5zN4EcPAFGxMxDjynZoE0S64EwDi+cPAioyBC X-Google-Smtp-Source: AMrXdXvYmJJ7+eFLnjMIqZuM5kFZXz/Oth90FBvGMSa/1IQ24ZqM8yFCBJwCzt5wTL4cQoXYsuNsEAKFO+o3FMK8oM3o2z9D6EV0 MIME-Version: 1.0 X-Received: by 2002:a5e:850f:0:b0:6ec:f27e:58a5 with SMTP id i15-20020a5e850f000000b006ecf27e58a5mr584311ioj.15.1671749745808; Thu, 22 Dec 2022 14:55:45 -0800 (PST) Date: Thu, 22 Dec 2022 14:55:45 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000c0a08805f07291a0@google.com> Subject: [syzbot] [erofs?] WARNING: CPU: NUM PID: NUM at mm/page_alloc.c:LINE get_page_from_freeli From: syzbot To: akpm@linux-foundation.org, chao@kernel.org, linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com, xiang@kernel.org 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: f9ff5644bcc0 Merge tag 'hsi-for-6.2' of git://git.kernel.o.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15aa58f7880000 kernel config: https://syzkaller.appspot.com/x/.config?x=827916bd156c2ec6 dashboard link: https://syzkaller.appspot.com/bug?extid=c3729cda01706a04fb98 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11bdd020480000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12c53ab3880000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/0c8a5f06ceb3/disk-f9ff5644.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/be222e852ae2/vmlinux-f9ff5644.xz kernel image: https://storage.googleapis.com/syzbot-assets/d9f42a53b05e/bzImage-f9ff5644.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/7f2f76b76cd2/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+c3729cda01706a04fb98@syzkaller.appspotmail.com ------------[ cut here ]------------ WARNING: CPU: 1 PID: 4386 at mm/page_alloc.c:3829 get_page_from_freeli --- 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