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 F2920C433F5 for ; Tue, 4 Jan 2022 21:00:41 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 54B2A6B0074; Tue, 4 Jan 2022 16:00:41 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 4FA046B0078; Tue, 4 Jan 2022 16:00:41 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3E9376B007B; Tue, 4 Jan 2022 16:00:41 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0238.hostedemail.com [216.40.44.238]) by kanga.kvack.org (Postfix) with ESMTP id 307DB6B0074 for ; Tue, 4 Jan 2022 16:00:41 -0500 (EST) Received: from smtpin03.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id DBF9B944E0 for ; Tue, 4 Jan 2022 21:00:40 +0000 (UTC) X-FDA: 78993823440.03.CF6EF45 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by imf21.hostedemail.com (Postfix) with ESMTP id 6619B1C0008 for ; Tue, 4 Jan 2022 21:00:33 +0000 (UTC) Received: from cwcc.thunk.org (pool-108-7-220-252.bstnma.fios.verizon.net [108.7.220.252]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 204L0UVV019108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 4 Jan 2022 16:00:30 -0500 Received: by cwcc.thunk.org (Postfix, from userid 15806) id 2D81115C00E1; Tue, 4 Jan 2022 16:00:30 -0500 (EST) Date: Tue, 4 Jan 2022 16:00:30 -0500 From: "Theodore Ts'o" To: Matthew Wilcox Cc: kvartet , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, sunhao.th@gmail.com Subject: Re: INFO: task hung in __filemap_get_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: 6619B1C0008 X-Stat-Signature: nzkztjk959to1gx1b65ep9tiu1tcibw3 Authentication-Results: imf21.hostedemail.com; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=mit.edu (policy=none); spf=none (imf21.hostedemail.com: domain of tytso@mit.edu has no SPF policy when checking 18.9.28.11) smtp.mailfrom=tytso@mit.edu X-Rspamd-Server: rspam11 X-HE-Tag: 1641330033-649667 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000001, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, Jan 04, 2022 at 06:18:23PM +0000, Matthew Wilcox wrote: > On Tue, Jan 04, 2022 at 07:44:10PM +0800, kvartet wrote: > > Hello, > > > > When using Syzkaller to fuzz the latest Linux kernel, the following > > crash was triggered. > > This isn't a crash, it's a notification of a hang. More than likely > syzbot is playing with RT scheduling again. > > We do not need more people running syzbot. We need more people tracking > down and fixing the syzbot reports that already exist. One of the syzbot spam reported by kvartet was a hang in the jbd2 layer, while it was waiting for processes to complete running handles, and the oom killer lock was reported as being involved. At which point, I stopped reading or caring about *any* of the syzbot complaints being reported by kvartet.... - Ted