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 088A8E7719A for ; Mon, 13 Jan 2025 05:06:21 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 795806B007B; Mon, 13 Jan 2025 00:06:21 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 7449B6B0083; Mon, 13 Jan 2025 00:06:21 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 633086B0085; Mon, 13 Jan 2025 00:06:21 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id 460696B007B for ; Mon, 13 Jan 2025 00:06:21 -0500 (EST) Received: from smtpin16.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id CD039161B8F for ; Mon, 13 Jan 2025 05:06:20 +0000 (UTC) X-FDA: 83001242520.16.853735E Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf07.hostedemail.com (Postfix) with ESMTP id B98BC40006 for ; Mon, 13 Jan 2025 05:06:18 +0000 (UTC) Authentication-Results: imf07.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=SXDTj3A7; spf=none (imf07.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=1736744779; 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:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=QSzmq64LoHaVQGwwp1pbcdAm3sapkgAsTXC1sRTKWrY=; b=mtXu/uuo3eQKouDO65Lq8WrcDr7etOuaEOuvZHlMRqki24EmGC3/uvJ0tf324UptJqO9/6 /IOmfsHAjbkCFRfWgbMjDV56ZZxgoesBAa0Oe+N3AtL4G1Xb3VOR25DXcqX8cpoann+VWB 1MoEDtNjSk6HxrD2Xc0Bb9VgTHh/oKw= ARC-Authentication-Results: i=1; imf07.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=SXDTj3A7; spf=none (imf07.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=1736744779; a=rsa-sha256; cv=none; b=R7tgpRMh18kMHz8etAkh2a/99Voks3erzydLnY1eKqba5z/Twe/wtCM5ADIM6cy01ryqgD 5ZJ+duEdryXVmZaZlByTiTzCnMiU3Q526OrL/lGTby2JevlmlmIXqYuX3m0fXSmNhnYtjY Ueimpb8PZwU7KRa0gTOJIY9RtitvUEA= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Transfer-Encoding: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-ID:Content-Description; bh=QSzmq64LoHaVQGwwp1pbcdAm3sapkgAsTXC1sRTKWrY=; b=SXDTj3A7toNB9CyQ8A2w53vitf faLXR7IdnlE92oUrlDrJQu+D5jUTjjmNawkw+DDS6R22hQssrCeKNJ4hXeUiVBO516Ur5LF+3NIOa B18968e0p/VsSTkF9a4Z6ZaW4khaev+/ofoSfqhEuZMZd/KGOtyj0aOWa8hvegFixZ5bHjKmjeNjW 3rfvH+0+8Z5Lc/iO8jDOH38ao8UjxyuJygURzaycqpo9kB1DTUqkzlQ5uqaRBkI1gD3jZQWs8OzIy BK4vQzCTjXrxmE6nJ8DzNIMmTPdthQNi+eXeE9ViM7Py5AKM89eeaXB2xCEJ2UkOVecI1aR23nAxQ 0Ddn2A1Q==; Received: from willy by casper.infradead.org with local (Exim 4.98 #2 (Red Hat Linux)) id 1tXCeK-000000005ag-1vNr; Mon, 13 Jan 2025 05:06:04 +0000 Date: Mon, 13 Jan 2025 05:06:04 +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: <431D467D-10F3-4316-A34B-6C1315178B05@m.fudan.edu.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <431D467D-10F3-4316-A34B-6C1315178B05@m.fudan.edu.cn> X-Rspamd-Queue-Id: B98BC40006 X-Stat-Signature: ry9pt1mtb594x4m9ryppepkmkuayi9kt X-Rspam-User: X-Rspamd-Server: rspam11 X-HE-Tag: 1736744778-79136 X-HE-Meta: U2FsdGVkX1/6hVisVXyDbYA0G4uArHO62+RvqYuG1a5e754jUiI0JWxKUt58oRoKU4p3s08G6rWf2UzPQCq2P4OB6CeGFyoS2iNiE9cLgTZyIkwbJsaULOmT/Pp72EaHNMenPD4/aA+0+7fMAtpoYdttBbEkMOk/3LOLmp3nwZiF1hA8BQPoYOuv8qnI9tI9izZQ3B9nvKwSXASHYjZZCWpIIOPkFmBKkCqWuunF2uj9ciFYH3hEErzyGvUXtj9pRcL2srvzfiAj5im42/qJmnwUDg82UdvNcycbcred6yhKPcElBeDmh/apYsDyYX7igSMSTS/eEzpYz1zIQnWUav0zpItlVMzIzsnTzDaX+Z2ZtRB4j73CYOifhyqZnXz018L/H3S44ToufNP2+rx2PNUr2WI50pTcNLL0TGca40EiZytsnvs3JP51UxyztOl0KBSawhneGcZGPGx4jU/V/DT6mPuhzx3DStZqb689KcSpkCM8vwf2S1VQzDtkL/tKeaXGWbS323X6A6kIpCwG3Db6Q9unC71vTcallsBBAIJ6N9Xxi1JZZQXz2XBb0q9kiuInI7cWDa0NYkBTO56jl+eOQ+qT5ffh9LmawK2iX2LnMwoUV/ZiR+H7vM4cHrmmoMeZ0CFYlY2RzOJnT+K9x7+avJ3r2jHEMdUl4VKaZpeveNzKnyQhpzJ4yl2dQObfkXhUhp/tjNXhyap8e/pDIV4Ia5BYBfgahJF5ga4Na4CAw8Yi2rEEIeGGhaksIL4n+bg3yLS8SEfCQ+jHO3UsAh/LQkfuSmRG9MoCYsebMe6vJQb+oerL7AbRtBVXFOIrcA0N14zhE9pQHyI+pIl2vhkUGL9KL8hgVWcXrCZBArmeKk68p3xAt3rSbXViO3Q12gWEp6698tMFjt1BLPIFN7EzQf6YYuotblA9JR8ezvxS7suuLSUSU6JdMpSX2J5PsPq584Hq4tJxScC+PlX OUSX1j/Z wy5H1kmZcq8LteUqPD8x8J6pwgCqIjDdnz98/Dgs3+d3tKewEImLoacQjexYRRXr74AJd7TmQIWj/RLQC/nU3BXeM9afw91lWz0ydCmdGZfinpQZgBYjHT6peNiCY8wfRAFXVqOirqfc3j6Y5u/qeknkVTPY2UzELOegk6hc1th9Dafyt9tRq7LWk0nzA3PuH2KlJtH7bHoQky+YK1VVPb3pKhh+nMl3DDd6gPE2R/TGxJ9GZUaiYVVrjlIhQj7Xz2dKjLmTN6ohYDFrgJxVjTEwtYX+obxgInzKynDDmD738R6Ltvgd+XTGEFX1KWVM+NYqqa2SQew0SFOMRP4h9233Ed/aOc07o0HYx5b5glcr1dUU= 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 08:51:20PM +0800, Kun Hu wrote: > > 2025年1月12日 20:02，Matthew Wilcox 写道： > > > > 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. > > > > Thank you very much and sorry at the same time. > > We know that most of the work of locating a issue should be done by the reporter, but having just looked into fuzzing against the kernel, the background knowledge of the kernel is not very familiar at the moment. That's why we've taken the approach of sending out a report first, and after getting professional feedback from the maintainers, we're able to target test a particular subsystem or module for them to improve efficiency. > > Our strategy seems to be incorrect and certainly due to our lack of Kernel expertise, again I apologize, we will improve and hopefully report really useful information. I'm not asking you to analyse the kernel; that is indeed a hard task. I'm asking you to analyse the reproducer. What is it really doing to create the problem? Often syzkaller includes a lot of extraneous goop that's not relevant. So, you can try to minimise the reproducer. If you're going to be fuzzing filesystems (and it seems like you've sent a lot of filesystem reports), then you should probably say if the reproducer uses a specially crafted image. Most filesystem developers will prioritise these bugs differently. It's really hard to get a good workflow going with syzkaller. Google has been trained now, and syzbot mostly produces good quality bugs. It's really frustrating to have to train a new group of people all over again. It would be much better if you worked with Google to get your changes into syzbot. Probably less work for you, too.