Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp108215pxu; Thu, 3 Dec 2020 21:23:38 -0800 (PST) X-Google-Smtp-Source: ABdhPJz1xG6lfjuS90fNGTs8yACm2AODVZQVA3tPI0XiJAqfTvgb563DKrCTduB3rczxFvmaD3Yx X-Received: by 2002:a17:906:b56:: with SMTP id v22mr1820476ejg.145.1607059418584; Thu, 03 Dec 2020 21:23:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607059418; cv=none; d=google.com; s=arc-20160816; b=JB3FXpKRu5siBdY7dgcCrEMy31xin2WlcPhjPyQjoL9SCtVum+T+/Azojv+CiGd7LN r/YsAWMnXqmoAoL4FI8dkxNgVu24WJTdDnKMti/TVDMlj+yKLfqyL8upW+A7pDw2j1to uxQd8kYjMytEQXX3y7HiG6eMcMDQNcmVxPGSGk8qtiXGfMT0N5TQ4du2CRwY4aYLFxYk oiyVykldxBTgUx4QbZfAqo293uoxLWxfH0leK4OvdSlPrefjig06w6zL24iiqaTmbWQA EHNxNw6u0GVtxZKOdZz2dZkPNIndijmsI8ShoOH8uQWSJkJExzJUtslJ7sadNRDE595F B04g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:dkim-signature:date; bh=ZcMp6lx+FxRyZw+uNwbn0Cpe82tf7rQHjfdMl+yvn2I=; b=fKDuPBlcgBM0r+c/r2eYSQ7cHxqJOPmS9zXAn5+xXIKxRafQ+o0o9iFnlwL2i10Ziw fxU8g6jQXkeMMW6yfC+zlz0zkkgNuCW8MBJVlllV7bJVz1XlGaqjbUjHA8XfvfPc/ns+ kHV6WXKOLiqKVOtZNDpfk0nrrfVBeV/0u1oYQPU7qjXTPNT0dIiDe0HVGtTxV2vrZDfi 9t/M1ZL+Jfg3MxZLFyk2U+pKQLbBtJgKOlgqP4qiRHZI1mA5PuH0nJ38WwU49Ad6ihZE JGHCBoTSKolXOYCdqwXm2m0elEhySBikTPeLF5XRSj0q+D/nC6PwmrO3E6pVqswskWCP 8xWQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=KeJEBuIP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id he7si698558ejc.676.2020.12.03.21.23.15; Thu, 03 Dec 2020 21:23:38 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=KeJEBuIP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727561AbgLDFTg (ORCPT + 99 others); Fri, 4 Dec 2020 00:19:36 -0500 Received: from mail.kernel.org ([198.145.29.99]:48000 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725300AbgLDFTf (ORCPT ); Fri, 4 Dec 2020 00:19:35 -0500 Date: Thu, 3 Dec 2020 21:18:53 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1607059135; bh=NTtFOG1GQx90cr9hCi4Q6/ZGEbwo1wz4YjAws8quq+Y=; h=From:To:Cc:Subject:References:In-Reply-To:From; b=KeJEBuIP38Tw8Wdzo5/eCldxIhwTUc8sNMSvPvgbFt2S20Y9dxy9kLd62M+gHvkxo O8HVGaq6anDcfW50A8aEF4n/ZpmXLzLoUc4Zzs7+lKhKhxMng0nuuL9adZeytp/OSB LyEAOjTfLbu3fhCdYgGoje7zBqi/3efX5GzhWskoDMWAJVlMbb0qhM8VBslu194Sma 4XmZXW8sf7Ysvsv2QL2KYcLZ1PynVMnTRL047LF4GgZFZMt/Wkszc3acv8bt1U89WP nPI79ftT1h9Au9Z6v+kyfAXWUKIEZfx99g53LYngTW0GWixkycvUpetG94nhsFCfTB A2njq7xqQhaGA== From: Eric Biggers To: Daeho Jeong Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com, Daeho Jeong Subject: Re: [f2fs-dev] [PATCH] f2fs: fix race of pending_pages in decompression Message-ID: References: <20201204005847.654074-1-daeho43@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 04, 2020 at 02:00:34PM +0900, Daeho Jeong wrote: > I think I don't understand how verity works. > Right after verity is enabled on a file, is the verity logic working > for the whole file data area? > Or it's just working for the data area which is updated after verity is enabled? > It's for the whole file. My point is just that if there is a bio that saw that verity isn't enabled yet when it started and therefore STEP_VERITY didn't get set in the bio_post_read_ctx (or the bio_post_read_ctx didn't get allocated due to one not being needed), then the filesystem shouldn't change its mind and try to verify the pages when the bio completes if verity happened to be enabled concurrently. It's too late for that bio. - Eric