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 1A423C433F5 for ; Fri, 7 Jan 2022 22:49:07 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 362B96B0072; Fri, 7 Jan 2022 17:49:07 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 311E16B0073; Fri, 7 Jan 2022 17:49:07 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 1D9536B0074; Fri, 7 Jan 2022 17:49:07 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0106.hostedemail.com [216.40.44.106]) by kanga.kvack.org (Postfix) with ESMTP id 0D9BC6B0072 for ; Fri, 7 Jan 2022 17:49:07 -0500 (EST) Received: from smtpin12.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id ADD0180C179B for ; Fri, 7 Jan 2022 22:49:06 +0000 (UTC) X-FDA: 79004983092.12.2EA9781 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf28.hostedemail.com (Postfix) with ESMTP id 309DEC000E for ; Fri, 7 Jan 2022 22:49:05 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 1AB4161F84; Fri, 7 Jan 2022 22:49:05 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4A920C36AE5; Fri, 7 Jan 2022 22:49:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1641595744; bh=ViSqgQgJuvP+htaIPnhi8An9uFQEuN9qNJ/GiLYWh+8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=X1oCrg9LFE1Jvd6RAH9k2xELL+kLGarb8CZsayVgHdtMIvEHSd954rjT0/h/vgDkJ MpYyr7hl6H4CWPGTx3439RkplHvCY55qpaVJGndfucNbQvIn9Iymj+K7GLh5rKCoks d69kq4uXX0gwXguQeQwuZZi9TBwkdprAMFqRI+VRr2pZ7cDz36FN2y8wgYijT3hrBd rB6bCFVMEQD+XgWq4ccMp2s2ysLS/5o77YvCIFS6hR2MRwFL8gefSwCApG83MM8NYS dVCkXbrZKfnNSsUpWsFw414UvdLkMmk72imthqc/e5G+iz3NR6iPW9GkuY5dfulAMf Z6pGm4B+hGWhA== Date: Fri, 7 Jan 2022 14:49:02 -0800 From: Eric Biggers To: kernel test robot Cc: lkp@intel.com, Linux Memory Management List , LKML , lkp@lists.01.org, Jaegeuk Kim , ltp@lists.linux.it Subject: Re: [LTP] [f2fs] a1e09b03e6: ltp.ADSP024.fail Message-ID: References: <20211226132851.GC34518@xsang-OptiPlex-9020> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211226132851.GC34518@xsang-OptiPlex-9020> X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 309DEC000E X-Stat-Signature: 1nj4o8gxagrk1rkymwzjh8qn37bngzya Authentication-Results: imf28.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=X1oCrg9L; dmarc=pass (policy=none) header.from=kernel.org; spf=pass (imf28.hostedemail.com: domain of ebiggers@kernel.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=ebiggers@kernel.org X-HE-Tag: 1641595745-780379 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: On Sun, Dec 26, 2021 at 09:28:52PM +0800, kernel test robot wrote: > > > Greeting, > > FYI, we noticed the following commit (built with gcc-9): > > commit: a1e09b03e6f5c1d713c88259909137c0fd264ede ("f2fs: use iomap for direct I/O") > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master > > in testcase: ltp > version: ltp-x86_64-14c1f76-1_20211221 > with following parameters: > > disk: 1HDD > fs: f2fs > test: ltp-aiodio.part2 > ucode: 0x21 > This is caused by an f2fs bug where it exposes DIO-allocated blocks to users before they have been initialized. This test actually fails both before and after my commit "f2fs: use iomap for direct I/O". It is nondeterministic, which is why it may have appeared to be a regression. I'll start a separate discussion on linux-f2fs-devel about this, since this thread has too many irrelevant mailing lists and this has been discussed before. - Eric