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 3CB6AC433EF for ; Thu, 26 May 2022 13:43:59 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id BAC9D8D0003; Thu, 26 May 2022 09:43:58 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B5BBD8D0001; Thu, 26 May 2022 09:43:58 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A4A0C8D0003; Thu, 26 May 2022 09:43:58 -0400 (EDT) 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 942688D0001 for ; Thu, 26 May 2022 09:43:58 -0400 (EDT) Received: from smtpin14.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 6C3AB4D9 for ; Thu, 26 May 2022 13:43:58 +0000 (UTC) X-FDA: 79508012556.14.2A1D89E Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by imf11.hostedemail.com (Postfix) with ESMTP id 8775140025 for ; Thu, 26 May 2022 13:43:50 +0000 (UTC) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out1.suse.de (Postfix) with ESMTP id A970821A06; Thu, 26 May 2022 13:43:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1653572636; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=UpK3/+mflNhNMKFUzS8sRLaHIEJ6kOwAbvdU09gMH7s=; b=3LryFXFDC3AdXNd2lRAYNMZxlZT+62FzmWr4B8ftgsP6BcWFelARCV2g3tqqyflpefmbZC V0TO6tAhWU4d11Zz3OOY5idYus/ihMFEAn8xbzx5CbrfPymCOPoAiHnLNWT/XQO4v7rXUF JKZP6bbyQG8k+ISKbPJmd0FYmlUNVDE= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1653572636; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=UpK3/+mflNhNMKFUzS8sRLaHIEJ6kOwAbvdU09gMH7s=; b=51eEm0IOMH3zxagbLh+mvwGB43Gpbh0I3m8y+KDeUxONAAfQ+Q4NcRdjBVzAmxjnQ89Y9M yNq1pS9sp/GMhKAA== Received: from quack3.suse.cz (unknown [10.100.224.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 9A9C32C141; Thu, 26 May 2022 13:43:56 +0000 (UTC) Received: by quack3.suse.cz (Postfix, from userid 1000) id 26532A0632; Thu, 26 May 2022 15:43:56 +0200 (CEST) Date: Thu, 26 May 2022 15:43:56 +0200 From: Jan Kara To: Stefan Roesch Cc: io-uring@vger.kernel.org, kernel-team@fb.com, linux-mm@kvack.org, linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, david@fromorbit.com, jack@suse.cz, hch@infradead.org Subject: Re: [PATCH v5 04/16] iomap: Add flags parameter to iomap_page_create() Message-ID: <20220526134356.volr3q5ysewszfwo@quack3.lan> References: <20220525223432.205676-1-shr@fb.com> <20220525223432.205676-5-shr@fb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220525223432.205676-5-shr@fb.com> X-Rspam-User: X-Rspamd-Queue-Id: 8775140025 X-Stat-Signature: ttzc4388c58bo14exo4koczc5z4kstku Authentication-Results: imf11.hostedemail.com; dkim=pass header.d=suse.cz header.s=susede2_rsa header.b=3LryFXFD; dkim=pass header.d=suse.cz header.s=susede2_ed25519 header.b=51eEm0IO; dmarc=none; spf=pass (imf11.hostedemail.com: domain of jack@suse.cz designates 195.135.220.28 as permitted sender) smtp.mailfrom=jack@suse.cz X-Rspamd-Server: rspam04 X-HE-Tag: 1653572630-510005 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 Wed 25-05-22 15:34:20, Stefan Roesch wrote: > Add the kiocb flags parameter to the function iomap_page_create(). > Depending on the value of the flags parameter it enables different gfp > flags. > > No intended functional changes in this patch. > > Signed-off-by: Stefan Roesch Just one nit below: > @@ -226,7 +231,7 @@ static int iomap_read_inline_data(const struct iomap_iter *iter, > if (WARN_ON_ONCE(size > iomap->length)) > return -EIO; > if (offset > 0) > - iop = iomap_page_create(iter->inode, folio); > + iop = iomap_page_create(iter->inode, folio, 0); > else > iop = to_iomap_page(folio); > > @@ -264,7 +269,7 @@ static loff_t iomap_readpage_iter(const struct iomap_iter *iter, > return iomap_read_inline_data(iter, folio); > > /* zero post-eof blocks as the page may be mapped */ > - iop = iomap_page_create(iter->inode, folio); > + iop = iomap_page_create(iter->inode, folio, 0); > iomap_adjust_read_range(iter->inode, folio, &pos, length, &poff, &plen); > if (plen == 0) > goto done; Shouldn't we pass iter->flags to iomap_page_create() in the above two call sites? I know functionally it is no different currently but in the future it might be less surprising... With this fixed, feel free to add: Reviewed-by: Jan Kara Honza -- Jan Kara SUSE Labs, CR