Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1982156pxb; Fri, 29 Jan 2021 09:53:03 -0800 (PST) X-Google-Smtp-Source: ABdhPJyq6305JaCYJCU7mgA8uEK2lF8+R1ahlMfk8QTapJ8ZsqkqVm3CMPKnAGFOMOXlzcWIIKy4 X-Received: by 2002:a17:907:7295:: with SMTP id dt21mr5908279ejc.518.1611942783402; Fri, 29 Jan 2021 09:53:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611942783; cv=none; d=google.com; s=arc-20160816; b=YtPEBu99NWYMyDufAyweXhhHvU7Y0YXRrtzC440F+PcdsqSkp5m+IGO7UToFZN23dC GrtBH2aiReQuJWPJlokHNlP2AQfNWQuIi2U4WO+Hgm3tlLvWUznHY9dGD62gN1iT0euF 88t2nZImE2TjaTPlLlbukiRuMIvIY14DqxUEE9Bmx+qgsHNtheJX7CSOpz4qzQXueW8x H4ANqD+87B5rU7PfCp9A6mzfD66N9fcSk5K02+hDlbiMCycoMlhuW6KY25G8kUyqUdy4 nbxRoSWHUepiVR38hsowB7KU9vGk51de1/Tj11hWtaiBpPEcTNBhjTMg7TZ6bes1YIqF onTA== 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:mail-followup-to:reply-to:message-id :subject:cc:to:from:date; bh=TApKjElLBsUcvGslL5SnbEDkaa5Qh/T8xwI8z0EOfog=; b=xSgsxAcungQ5ZQVWwkKdG3EQxjRUIHCCqkG2739J462xJ8JjJxS9PYWf/bwzffr8Ll eZpYo0dvv7itGlIS7IiydOPtWGLcD1uxj1J/zWJd30biObSYfFO0Obv5nGe6VfUHKLIN 0u1FqAJSV0dJgkQQeyvHvRUFqkKk1bi/992a5WNctsZ+g/fu9R/YKHLHNgvVN261uQ41 jpqq4sNlcCAli+lq5J1VGNiskOQkzmBR1Xw1mrlO3BIw7pRerz/NECsKA4sXAmny9Xr7 Dup6knfh1qI1iZJUSbYF/kr6qQUmDtoK57BEmdEbNx0ODIEpT5GvKaD/66HLOrwBxDEz Hd7w== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e8si5173570eja.251.2021.01.29.09.52.37; Fri, 29 Jan 2021 09:53:03 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232570AbhA2Rv3 (ORCPT + 99 others); Fri, 29 Jan 2021 12:51:29 -0500 Received: from mx2.suse.de ([195.135.220.15]:34370 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232498AbhA2Ru1 (ORCPT ); Fri, 29 Jan 2021 12:50:27 -0500 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 13CB1AC4F; Fri, 29 Jan 2021 17:49:42 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id CDA3DDA7C3; Fri, 29 Jan 2021 18:47:53 +0100 (CET) Date: Fri, 29 Jan 2021 18:47:53 +0100 From: David Sterba To: Michal Rostecki Cc: Josef Bacik , Chris Mason , David Sterba , linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org, Michal Rostecki Subject: Re: [PATCH v2] btrfs: Avoid calling btrfs_get_chunk_map() twice Message-ID: <20210129174753.GL1993@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Michal Rostecki , Josef Bacik , Chris Mason , David Sterba , linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org, Michal Rostecki References: <20210127135728.30276-1-mrostecki@suse.de> <18dab74b-aea9-0e34-1be5-39d62f44cfd2@toxicpanda.com> <20210129171521.GB22949@wotan.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210129171521.GB22949@wotan.suse.de> User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 29, 2021 at 05:15:21PM +0000, Michal Rostecki wrote: > On Fri, Jan 29, 2021 at 11:22:48AM -0500, Josef Bacik wrote: > > On 1/27/21 8:57 AM, Michal Rostecki wrote: > > > From: Michal Rostecki > > > > > > Before this change, the btrfs_get_io_geometry() function was calling > > > btrfs_get_chunk_map() to get the extent mapping, necessary for > > > calculating the I/O geometry. It was using that extent mapping only > > > internally and freeing the pointer after its execution. > > > > > > That resulted in calling btrfs_get_chunk_map() de facto twice by the > > > __btrfs_map_block() function. It was calling btrfs_get_io_geometry() > > > first and then calling btrfs_get_chunk_map() directly to get the extent > > > mapping, used by the rest of the function. > > > > > > This change fixes that by passing the extent mapping to the > > > btrfs_get_io_geometry() function as an argument. > > > > > > v2: > > > When btrfs_get_chunk_map() returns an error in btrfs_submit_direct(): > > > - Use errno_to_blk_status(PTR_ERR(em)) as the status > > > - Set em to NULL > > > > > > Signed-off-by: Michal Rostecki > > > > This panic'ed all of my test vms in their overnight xfstests runs, the panic is this > > > > [ 2449.936502] BTRFS critical (device dm-7): mapping failed logical > > 1113825280 bio len 40960 len 24576 > > [ 2449.937073] ------------[ cut here ]------------ > > [ 2449.937329] kernel BUG at fs/btrfs/volumes.c:6450! > > [ 2449.937604] invalid opcode: 0000 [#1] SMP NOPTI > > [ 2449.937855] CPU: 0 PID: 259045 Comm: kworker/u5:0 Not tainted 5.11.0-rc5+ #122 > > [ 2449.938252] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS > > 1.13.0-2.fc32 04/01/2014 > > [ 2449.938713] Workqueue: btrfs-worker-high btrfs_work_helper > > [ 2449.939016] RIP: 0010:btrfs_map_bio.cold+0x5a/0x5c > > [ 2449.939392] Code: 37 87 ff ff e8 ed d4 8a ff 48 83 c4 18 e9 b5 52 8b ff > > 49 89 c8 4c 89 fa 4c 89 f1 48 c7 c6 b0 c0 61 8b 48 89 ef e8 11 87 ff ff <0f> > > 0b 4c 89 e7 e8 42 09 86 ff e9 fd 59 8b ff 49 8b 7a 50 44 89 f2 > > [ 2449.940402] RSP: 0000:ffff9f24c1637d90 EFLAGS: 00010282 > > [ 2449.940689] RAX: 0000000000000057 RBX: ffff90c78ff716b8 RCX: 0000000000000000 > > [ 2449.941080] RDX: ffff90c7fbc27ae0 RSI: ffff90c7fbc19110 RDI: ffff90c7fbc19110 > > [ 2449.941467] RBP: ffff90c7911d4000 R08: 0000000000000000 R09: 0000000000000000 > > [ 2449.941853] R10: ffff9f24c1637b48 R11: ffffffff8b9723e8 R12: 0000000000000000 > > [ 2449.942243] R13: 0000000000000000 R14: 000000000000a000 R15: 000000004263a000 > > [ 2449.942632] FS: 0000000000000000(0000) GS:ffff90c7fbc00000(0000) > > knlGS:0000000000000000 > > [ 2449.943072] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > > [ 2449.943386] CR2: 00005575163c3080 CR3: 000000010ad6c004 CR4: 0000000000370ef0 > > [ 2449.943772] Call Trace: > > [ 2449.943915] ? lock_release+0x1c3/0x290 > > [ 2449.944135] run_one_async_done+0x3a/0x60 > > [ 2449.944360] btrfs_work_helper+0x136/0x520 > > [ 2449.944588] process_one_work+0x26e/0x570 > > [ 2449.944812] worker_thread+0x55/0x3c0 > > [ 2449.945016] ? process_one_work+0x570/0x570 > > [ 2449.945250] kthread+0x137/0x150 > > [ 2449.945430] ? __kthread_bind_mask+0x60/0x60 > > [ 2449.945666] ret_from_fork+0x1f/0x30 > > > > it happens when you run btrfs/060. Please make sure to run xfstests against > > patches before you submit them upstream. Thanks, > > > > Josef > > Umm... I ran the xftests against v1 patch and didn't get that panic. It could have been caused by my fixups to v2 and I can reproduce the crash now too. I can't see any difference besides the u64/int switch and the 'goto out' removal in btrfs_bio_fits_in_stripe.