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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 92340C433F5 for ; Thu, 27 Jan 2022 09:49:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229845AbiA0Jtt (ORCPT ); Thu, 27 Jan 2022 04:49:49 -0500 Received: from verein.lst.de ([213.95.11.211]:43442 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229483AbiA0Jtt (ORCPT ); Thu, 27 Jan 2022 04:49:49 -0500 Received: by verein.lst.de (Postfix, from userid 2407) id 6917268B05; Thu, 27 Jan 2022 10:49:42 +0100 (CET) Date: Thu, 27 Jan 2022 10:49:42 +0100 From: Christoph Hellwig To: Jan Kara Cc: Christoph Hellwig , Jens Axboe , Tetsuo Handa , linux-block@vger.kernel.org, Ming Lei Subject: Re: [PATCH 3/8] block: remove the racy bd_inode->i_mapping->nrpages asserts Message-ID: <20220127094942.GA14727@lst.de> References: <20220126155040.1190842-1-hch@lst.de> <20220126155040.1190842-4-hch@lst.de> <20220127094737.dosrg7xbnwuw3ttx@quack3.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220127094737.dosrg7xbnwuw3ttx@quack3.lan> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Thu, Jan 27, 2022 at 10:47:37AM +0100, Jan Kara wrote: > On Wed 26-01-22 16:50:35, Christoph Hellwig wrote: > > Nothing prevents a file system or userspace opener of the block device > > from redirtying the page right afte sync_blockdev returned. Fortunately > > data in the page cache during a block device change is mostly harmless > > anyway. > > > > Signed-off-by: Christoph Hellwig > > My understanding was these warnings are there to tell userspace it is doing > something wrong. Something like the warning we issue when DIO races with > buffered IO... I'm not sure how useful they are but I don't see strong > reason to remove them either... Well, it is not just a warning, but also fails the command. With some of the reduced synchronization blktests loop/002 can hit them pretty reliably.