Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp346230pxk; Thu, 17 Sep 2020 04:52:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxwxYNfo9j0/vhSLmdSsAEdR3hlmqRvboidWlXIuOJuaKoF2SuOFtb7bhaJ6QMvJizZZXBn X-Received: by 2002:a17:906:c1c6:: with SMTP id bw6mr31460286ejb.374.1600343533365; Thu, 17 Sep 2020 04:52:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600343533; cv=none; d=google.com; s=arc-20160816; b=KeJSPCvvfHIDxGvWxo1Tz+kIms1gZx3W340aJ6oiQXiJhTTeNJjAFtMNT0YU+4MZOF dsB1vXvomVlVjjCoGUXbZjN1TdspIylHcBIc4Q/2dtDsJXOfd2JltKNW3wy0RYfWBTbF zcL+COMI+KRUeIHg0P5etEIzF84rJxvbfKCIFIHaBx/Pf4XixJdPJUwHT7dpI02OSkMi GV464nAuo0/dMrGhmu4WDDPszfipE9ANk9YgdPLQZoKmxxd6pKPRu4feKtBKd60WocsN ZdNZ+2tdC2vco61oDOG2eBiECKy80wf5/q+FlXG77k7LJW4R6JTvUkX+UTCM4wOlNS20 4omQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=ieOyT+3dJRv+nNDkG5NiJYcXgSLXAkfjSjp+E1iGrHc=; b=WLpFs8OC3+KFZohDRT+Qix74cHPFqj5dlQQCYq1gwKw9WZY2G6yVb7oM77MQu7RyH1 uBcV7vcH/ENvdWBU5C2AHU8cfWjAHpLC0tnxICIPSConLPwSarl1+KGxXLINyAlJvS/T 7eeOkUM8KCEGErAYdp1Bzhatamg7E+c7GFUWFznQIGFURbOsQWzUJkhkk1yqv5p2iAsm lDyeqq5XngSS2fbwVEm2CoDkkpRfOGyKE6boZhnlkcXt0BgHlK+AdrUyuwj+5NhNJfoP mUs8Dy+qozC8hh0+Kyp3YJmJUnPEHF6izgkOjVUE3270M/Ap6ysgiDkKxh3hFeNv8yoU Ldpg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bn11si14203681ejb.658.2020.09.17.04.51.46; Thu, 17 Sep 2020 04:52:13 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726862AbgIQLvR (ORCPT + 99 others); Thu, 17 Sep 2020 07:51:17 -0400 Received: from mx2.suse.de ([195.135.220.15]:59946 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726677AbgIQLvK (ORCPT ); Thu, 17 Sep 2020 07:51:10 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 95DA1ADBD; Thu, 17 Sep 2020 11:51:37 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id 680351E12E1; Thu, 17 Sep 2020 13:51:03 +0200 (CEST) Date: Thu, 17 Sep 2020 13:51:03 +0200 From: Jan Kara To: "zhangyi (F)" Cc: Jan Kara , linux-ext4@vger.kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca, jack@suse.com Subject: Re: [PATCH] ext4: clear buffer verified flag if read meta block from disk Message-ID: <20200917115103.GD16097@quack2.suse.cz> References: <20200914112420.1906407-1-yi.zhang@huawei.com> <20200915130711.GP4863@quack2.suse.cz> <2b43d24e-f220-a9f8-d1a6-e85363020a3b@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2b43d24e-f220-a9f8-d1a6-e85363020a3b@huawei.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Tue 15-09-20 22:57:35, zhangyi (F) wrote: > Hi, Jan > > On 2020/9/15 21:07, Jan Kara wrote: > > On Mon 14-09-20 19:24:20, zhangyi (F) wrote: > >> The metadata buffer is no longer trusted after we read it from disk > >> again because it is not uptodate for some reasons (e.g. failed to write > >> back). Otherwise we may get below memory corruption problem in > >> ext4_ext_split()->memset() if we read stale data from the newly > >> allocated extent block on disk which has been failed to async write > >> out but miss verify again since the verified bit has already been set > >> on the buffer. > >> > >> [ 29.774674] BUG: unable to handle kernel paging request at ffff88841949d000 > >> ... > >> [ 29.783317] Oops: 0002 [#2] SMP > >> [ 29.784219] R10: 00000000000f4240 R11: 0000000000002e28 R12: ffff88842fa1c800 > >> [ 29.784627] CPU: 1 PID: 126 Comm: kworker/u4:3 Tainted: G D W > >> [ 29.785546] R13: ffffffff9cddcc20 R14: ffffffff9cddd420 R15: ffff88842fa1c2f8 > >> [ 29.786679] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),BIOS ?-20190727_0738364 > >> [ 29.787588] FS: 0000000000000000(0000) GS:ffff88842fa00000(0000) knlGS:0000000000000000 > >> [ 29.789288] Workqueue: writeback wb_workfn > >> [ 29.790319] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > >> [ 29.790321] (flush-8:0) > >> [ 29.790844] CR2: 0000000000000008 CR3: 00000004234f2000 CR4: 00000000000006f0 > >> [ 29.791924] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > >> [ 29.792839] RIP: 0010:__memset+0x24/0x30 > >> [ 29.793739] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > >> [ 29.794256] Code: 90 90 90 90 90 90 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 033 > >> [ 29.795161] Kernel panic - not syncing: Fatal exception in interrupt > >> ... > >> [ 29.808149] Call Trace: > >> [ 29.808475] ext4_ext_insert_extent+0x102e/0x1be0 > >> [ 29.809085] ext4_ext_map_blocks+0xa89/0x1bb0 > >> [ 29.809652] ext4_map_blocks+0x290/0x8a0 > >> [ 29.809085] ext4_ext_map_blocks+0xa89/0x1bb0 > >> [ 29.809652] ext4_map_blocks+0x290/0x8a0 > >> [ 29.810161] ext4_writepages+0xc85/0x17c0 > >> ... > >> > >> Fix this by clear buffer's verified bit if we read it from disk again. > >> > >> Signed-off-by: zhangyi (F) > > > > Good spotting! When looking at the patch I was just wondering that it's > > rather easy to miss clearing of buffer_verified() bit in some place where > > we read metadata block from disk. So I was wondering that maybe it would be > > Indeed, I clear the buffer_verified() bit in some common helpers of ext4, > such as ext4_bread() and ext4_sb_bread(), so we may not miss clear it > where we invoke these helpers, but it is rather easy to miss in the > others places where submit read bio directly. How about add some common > helpers for them too ? I was thinking about this for some time and yes, I agree this is probably the best way forward. I've looked at places where we submit reads and probably some helper like below should work: void ext4_read_bh(struct buffer_head *bh, int op_flags, void (*end_io)(struct buffer_head *bh, int uptodate)) which would do the final ext4_buffer_uptodate() check, set end_io (fill in end_buffer_read_sync if NULL), clear verified bit, get bh ref, and do submit_bh(). And use this in all the places reading metadata buffers instead of various different helpers. Honza -- Jan Kara SUSE Labs, CR