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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5A74CE77188 for ; Sun, 12 Jan 2025 12:02:26 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 809CA6B0092; Sun, 12 Jan 2025 07:02:25 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 7B9856B0098; Sun, 12 Jan 2025 07:02:25 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 6A8BD6B0099; Sun, 12 Jan 2025 07:02:25 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 4D8806B0092 for ; Sun, 12 Jan 2025 07:02:25 -0500 (EST) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 6B39AA1833 for ; Sun, 12 Jan 2025 12:02:24 +0000 (UTC) X-FDA: 82998662208.11.343A808 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf18.hostedemail.com (Postfix) with ESMTP id 3E4FD1C0011 for ; Sun, 12 Jan 2025 12:02:20 +0000 (UTC) Authentication-Results: imf18.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=BG2WxpxE; spf=none (imf18.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1736683342; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=mINOFD/z3wJJsYIblZcazetsQ/fwmJD/fCcLc2fXueY=; b=XFDb1ea2UKFuRB5WsBGqPlx0bEIn/bB1UFWmS5JxGO6IOwfHDYudbITbr8pr3dtq6OyyGf dWuuLrmCgcvRYzvsH6LA/Dd2ydvCqaN+nL5oQEj60LW8Y1E7jv7hlovK6knCfksxNQCMaF 8BhxgZn+TM+BZfZnWd760JmcP5CYJVQ= ARC-Authentication-Results: i=1; imf18.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=BG2WxpxE; spf=none (imf18.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1736683342; a=rsa-sha256; cv=none; b=3QfD01XCvzYmWbzmq2I/n4fbxeE6YBC2Tw4B5U2n4EClpS6maOJnVCy66KSlcDLlkXIkh2 oe6dC8/robIjx0bDeGaIVS44bl2WTwuPEOZagMffzgtvyX0TWR13dLFzFWAuofW7LHuDKr 2eU3SbqVly1tbw9MqXIJysrBEoCy1ww= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=mINOFD/z3wJJsYIblZcazetsQ/fwmJD/fCcLc2fXueY=; b=BG2WxpxEW6964q+g1ejYxmigMt wmk+HS+jx0f0Bq4I2skTCrODifdH9+bjiaU9HhtnH5TXnF4A2kRTiCM+/2kSgeqUh1SVfQj17QeiS QO//EDvMO216OzEAT+mPLXABn9PgBfbgeSx5XWKyEGxIaqbiMNvT/GximzAubaHaLJ62I4VRCLhLv cm8GoQ/Z2KbG8AzCEQuznBl/j2jeWQggYbih9g78YAXwS5YjcqKJICirRXXSML5qoMmDJ+ymxs11m 3YPhl5rOq6ZHSM55nCua9CzFVP13YK239en6LcyTC8OnsYG60VqZy+gBeXev9Kg96DrfsYHgWeKAX v4Dzq4xg==; Received: from willy by casper.infradead.org with local (Exim 4.98 #2 (Red Hat Linux)) id 1tWwfS-0000000GVo1-00Vt; Sun, 12 Jan 2025 12:02:10 +0000 Date: Sun, 12 Jan 2025 12:02:09 +0000 From: Matthew Wilcox To: Kun Hu Cc: hch@lst.de, jlayton@kernel.org, kirill.shutemov@linux.intel.com, vbabka@suse.cz, william.kucharski@oracle.com, rppt@linux.ibm.com, dhowells@redhat.com, akpm@linux-foundation.org, hughd@google.com, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: Bug: task hung in shmem_swapin_folio Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 3E4FD1C0011 X-Rspamd-Server: rspam12 X-Stat-Signature: ountikhmsxcdft98f6fuspgyak7hq16p X-Rspam-User: X-HE-Tag: 1736683340-406556 X-HE-Meta: U2FsdGVkX19iY691MWbLzkE5sB3bTJKkmbE81Pi2HZqEEFuw1itJAb2h5KWhQUw/gD9UtY6cR9mydwb4bdQ0stXzo3we5rMjRZpsHemlccFfF116V4/Gqa3gU5m4/byAYc3R390dQdEuryMrGRBihD45POzEhXAyxsr1X6I1HWU9ceLr7BnTcctRP+UbGnmeMXwuq0vOZw5C9gYMG2plsh84fXWyv7PNd3/seuRCedYCX/BVHQzWqKw7TLMJ6k2R7IVU6XqxmFZM+AYoZVig+QivHJI2nDVsNCSL6BlEWdEMdnVeixEMG5bJg94444SLng877HEBWTohGECaqDNID93dMBiNsGjuczXMi9lVt81IZu40eZMpU/0kO1Gc9OhLYLr+omH1to3J7QOoMN85V4vHkYt0ijocnS++H5r7p4NmpyRKz7IDlf7GzmwOntuZghyDokKkdi3pgR/+1pSGGwuyfKxTSU91sofv37UvHdFEkERLW/HZf0ep94+GOeLQv2PIOlMn12sqxlDDppoiAnNzrTnAsu6Ohdszliavz49mlW58x2TwB6ao93McBquTzaySdJqDVuiSCubh1uXjyS8Pknqi3Vi864BLzHhyh2cFO9J7odb4zP/ZwsT789/Glgqfc/bdEfaX7vO3w5etobahqd/6u4ieKpi/727EuLZhIOP5Dd9igZXuqx6RfWdnIimAxGzVkEouK3tWV/5nh9Z1t5YdH6gqUTFPc/+Sw/fKjmj3yLoNbaPE9+vXucNCVmL9xwH/Rw2LGGxhehCMXzdIh2t7C7ttfCFQH4rtwE3+g7c4TA30WhsHDVH3RYNPFWSEPKqs//AkeHQEjb5lHvxG9uAWf5o/HEm+Kkj5JPjnjoPXDWOJp64pG4Ba2eDFdRIQHt78eCNyYMorvYW4qHuakt/DHRNHcTTN3OuAEZphEoyzknMXK7MQSuKu0dLEO9dt5ZiqQz5sQRZch3m tTKMIOUM n3SRBC0QmnSMP5CQKYY2ZFhxMmjDtMbaZfUSdit6GUggszY+M58fqObMHqYxf9g1Tb5KNBLdXVOyO8NxRmzkJ98QdpR82woms3VYuOG+37NYLzskR1sEZ32/joEXI8C28r2L0L4D+xjyxzA/8b5+iIaNbhF8RmOaZUqtc+ugeQ5a5qaIwUdp8i4StiTOryGV3z3VcFyTxjjcEYRVb+TnTHLzlr0a+75hUcDKadv2BHOP3couTfT4V3IO7dTo9Xe6yIE3MOAQyWx2Ned9MAKlUtwQoSw== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Sun, Jan 12, 2025 at 05:46:24PM +0800, Kun Hu wrote: > Hello, > > When using our customized fuzzer tool to fuzz the latest Linux kernel, the following crash (42s) > was triggered. It's not a crash. It's a warning. You've just configured your kernel to crash when emitting a warning. What you need to do is poke around in the reproducer you've found and figure out what it is you're doing that causes this warning. Are you constraining your task with memory groups, for example? Are you doing a huge amount of I/O which is causing your disk to be bottlenecked? Something else? It's all very well to automate finding bugs, but you're asking other people to do a lot of the work for you.