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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A452BC4167B for ; Tue, 8 Dec 2020 13:39:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7E77523A53 for ; Tue, 8 Dec 2020 13:39:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729020AbgLHNiy (ORCPT ); Tue, 8 Dec 2020 08:38:54 -0500 Received: from mx2.suse.de ([195.135.220.15]:37250 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728318AbgLHNiy (ORCPT ); Tue, 8 Dec 2020 08:38:54 -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 D7F11AD41; Tue, 8 Dec 2020 13:38:11 +0000 (UTC) Date: Tue, 8 Dec 2020 14:38:11 +0100 From: Daniel Wagner To: Christoph Hellwig Cc: Qian Cai , Jens Axboe , Tejun Heo , Coly Li , Song Liu , dm-devel@redhat.com, linux-bcache@vger.kernel.org, linux-raid@vger.kernel.org, linux-s390@vger.kernel.org, linux-block@vger.kernel.org, Stephen Rothwell , Linux Next Mailing List Subject: Re: store a pointer to the block_device in struct bio (again) Message-ID: <20201208133811.5versqznlcqvmkro@beryllium.lan> References: <20201201165424.2030647-1-hch@lst.de> <920899710c9e8dcce16e561c6d832e4e9c03cd73.camel@redhat.com> <20201208110403.GA22179@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201208110403.GA22179@lst.de> Precedence: bulk List-ID: X-Mailing-List: linux-bcache@vger.kernel.org On Tue, Dec 08, 2020 at 12:04:03PM +0100, Christoph Hellwig wrote: > can you send me details of your device mapper setup, e.g. which targets > are used, are they used on top of whole device or partitions. Do you > use partitions on top of the dm devices? Are any other stacking devices > involved? FWIW, I tried linux-next yesterday and got the root fs (btrfs) corrupted. It is a very simple setup, just plain FS on SCSI device. 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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 76F32C4361B for ; Tue, 8 Dec 2020 13:54:33 +0000 (UTC) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id C1AF9206DB for ; Tue, 8 Dec 2020 13:54:32 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C1AF9206DB Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=tempfail smtp.mailfrom=dm-devel-bounces@redhat.com Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-17-j8T-B0f1OyODw3lwAiCACw-1; Tue, 08 Dec 2020 08:54:29 -0500 X-MC-Unique: j8T-B0f1OyODw3lwAiCACw-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0CAC28049F1; Tue, 8 Dec 2020 13:53:49 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 087CC60C05; Tue, 8 Dec 2020 13:53:48 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id EA767180954D; Tue, 8 Dec 2020 13:53:44 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 0B8Drh2I020451 for ; Tue, 8 Dec 2020 08:53:43 -0500 Received: by smtp.corp.redhat.com (Postfix) id 4F0652166B2B; Tue, 8 Dec 2020 13:53:43 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast06.extmail.prod.ext.rdu2.redhat.com [10.11.55.22]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4A1172166B27 for ; Tue, 8 Dec 2020 13:53:41 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 0567E1871CC5 for ; Tue, 8 Dec 2020 13:53:41 +0000 (UTC) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-433-j5zIGdC_NH6QxRGU5i7pNQ-1; Tue, 08 Dec 2020 08:53:38 -0500 X-MC-Unique: j5zIGdC_NH6QxRGU5i7pNQ-1 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 D7F11AD41; Tue, 8 Dec 2020 13:38:11 +0000 (UTC) Date: Tue, 8 Dec 2020 14:38:11 +0100 From: Daniel Wagner To: Christoph Hellwig Message-ID: <20201208133811.5versqznlcqvmkro@beryllium.lan> References: <20201201165424.2030647-1-hch@lst.de> <920899710c9e8dcce16e561c6d832e4e9c03cd73.camel@redhat.com> <20201208110403.GA22179@lst.de> MIME-Version: 1.0 In-Reply-To: <20201208110403.GA22179@lst.de> X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-loop: dm-devel@redhat.com Cc: Jens Axboe , linux-s390@vger.kernel.org, Stephen Rothwell , Qian Cai , linux-bcache@vger.kernel.org, Coly Li , linux-raid@vger.kernel.org, Song Liu , dm-devel@redhat.com, Linux Next Mailing List , linux-block@vger.kernel.org, Tejun Heo Subject: Re: [dm-devel] store a pointer to the block_device in struct bio (again) X-BeenThere: dm-devel@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: device-mapper development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dm-devel-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Tue, Dec 08, 2020 at 12:04:03PM +0100, Christoph Hellwig wrote: > can you send me details of your device mapper setup, e.g. which targets > are used, are they used on top of whole device or partitions. Do you > use partitions on top of the dm devices? Are any other stacking devices > involved? FWIW, I tried linux-next yesterday and got the root fs (btrfs) corrupted. It is a very simple setup, just plain FS on SCSI device. -- dm-devel mailing list dm-devel@redhat.com https://www.redhat.com/mailman/listinfo/dm-devel