From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752618AbcF1Tnd (ORCPT ); Tue, 28 Jun 2016 15:43:33 -0400 Received: from mail-bl2on0104.outbound.protection.outlook.com ([65.55.169.104]:18296 "EHLO na01-bl2-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752357AbcF1Tna (ORCPT ); Tue, 28 Jun 2016 15:43:30 -0400 From: "Kani, Toshimitsu" To: "snitzer@redhat.com" CC: "linux-raid@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-nvdimm@lists.01.org" , "dm-devel@redhat.com" , "agk@redhat.com" Subject: Re: [PATCH 0/2] fix dm-snap for dax Thread-Topic: [PATCH 0/2] fix dm-snap for dax Thread-Index: AQHR0XVWaRyCE2PkvkGiddSSiWL/+g== Date: Tue, 28 Jun 2016 19:43:26 +0000 Message-ID: <1467143000.3504.431.camel@hpe.com> References: <1467142636-21094-1-git-send-email-toshi.kani@hpe.com> In-Reply-To: <1467142636-21094-1-git-send-email-toshi.kani@hpe.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=toshi.kani@hpe.com; x-originating-ip: [15.219.163.9] x-ms-office365-filtering-correlation-id: 1deb80b1-e86b-4dc1-d146-08d39f8c7960 x-microsoft-exchange-diagnostics: 1;CS1PR84MB0005;6:KhUioU/0xUaKOwQJ2CKiQNWgAc+u220nMBYl3w5h62v4n7hm8/LBB+leMZDA5Cvr/S9uxaOTSL5hDKMMbW9GiePw8ZtKBmg7XxgPE9Isd1EpaDarUzlAkEvziKxMZ1w8dOhubyMb0dkSHq4gErdBLUuna5oM4lOK2N5iHSsuFpRVOfcvj721W9jcoDDdqmLk/iobkMbdbGRLi21uEmp6hyQ+l4pYrscrefRDr3yNlSg1EC/pMYeQPyBa0ujqUjtZQpk1oHZxWGyr0uRcvxYz1uqP43HW9cWfPx5++WjGSCE=;5:DPCeSQU3ZhwARL+Myq9kQUwuWJTXvM1iaRJVbuFv3tOy57OoCvcTP/9jTIX6++rliuHKmBcBlndQf7BkN2gwRk0s1LItSt4iDFSH8UGoBUvPnG6ewaDVx9zKvCALR1AoOvZMkzdKyaPKBZXhyiEXWw==;24:mqFbmXU6hh6Ec+nWzsJnuGPqdghrF/+zjvMyIEHxUhuJDRdKZVpH4gPIpXvqPgrksi4520mXze5+m8GWa5ZNwhJYuHVKG0nA/pMTNW/a0/M=;7:HfX3w8k0PSpaSCpGDACHkmYTBjYtnPIl0NJWpne0hDyBKv8zSvPbdke3UW2Q5LAU8RQMWGaWhWuQqDdKztkrInkFTg3I2OAbr/2A41m5wssOqAZQ04web/bVq9gNtVsyAO2FHCNiPKuTSypLgFkvFZ1iF9c3soVQaUc/y3aOkWvUva2ubceINMo4SdjVr/Nq8Ws6KSOwR0ptARh3Od5geXLa6NZN2fn3D3JqOvR5ixUqtSvD4Eh3Z7RjbIM7lwYy x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CS1PR84MB0005; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(162533806227266); x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046);SRVR:CS1PR84MB0005;BCL:0;PCL:0;RULEID:;SRVR:CS1PR84MB0005; x-forefront-prvs: 0987ACA2E2 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(7916002)(199003)(24454002)(189002)(377424004)(33646002)(50986999)(8936002)(76176999)(54356999)(6116002)(102836003)(3846002)(586003)(2501003)(110136002)(2950100001)(68736007)(92566002)(19580395003)(7846002)(7736002)(86362001)(5640700001)(189998001)(97736004)(2900100001)(2906002)(3660700001)(3280700002)(4326007)(305945005)(8676002)(19580405001)(15975445007)(87936001)(77096005)(99286002)(5002640100001)(1730700003)(81166006)(81156014)(101416001)(122556002)(105586002)(10400500002)(66066001)(103116003)(36756003)(2351001)(106356001)(106116001);DIR:OUT;SFP:1102;SCL:1;SRVR:CS1PR84MB0005;H:CS1PR84MB0005.NAMPRD84.PROD.OUTLOOK.COM;FPR:;SPF:None;PTR:InfoNoRecords;A:1;MX:1;LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: <49AF3059A3F22F43BC6FCF0B51BAEEB0@NAMPRD84.PROD.OUTLOOK.COM> MIME-Version: 1.0 X-OriginatorOrg: hpe.com X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jun 2016 19:43:26.7425 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc X-MS-Exchange-Transport-CrossTenantHeadersStamped: CS1PR84MB0005 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u5SJhcBo015254 Sorry, subject line should be "[PATCH 0/2] fix dm-snap for dax" -Toshi On Tue, 2016-06-28 at 13:37 -0600, Toshi Kani wrote: > I noticed that dm-snap reloads DM table of target mapped-device, which > fails for dax-capable device after dax support is added.  Ideally, > adding dax support to dm-snap solves the issue, but it cannot be done > easily.  This patch-set allows dm-snap to work with dax-capable target > devices when bio-based operation is used. > > dax operation is unsupported with dm-snap, such that: >  a) After snapshot is taken, mount with dax option to a target device >     or a snapshot device fails.  They can be mounted without dax. >  b) After snapshot is taken to a dax-mounted target device, any writes  >     to the target device fails (EIO). > > b) can be protected by changing lvcreate to fail when snapshot is > requested to a dax-mounted target device.  > > - Patch 1 solves an error when lvremove is made to a snapshot device. > - Patch 2 solves an error when lvcreate --snapshot is made to a dax- >   capable device. > > --- > Toshi Kani (2): >  1/2 dm: update table type check for dax >  2/2 dm snap: add fake origin_direct_access > > --- >  drivers/md/dm-ioctl.c | 11 ++++++++++- >  drivers/md/dm-snap.c  |  8 ++++++++ >  2 files changed, 18 insertions(+), 1 deletion(-) > _______________________________________________ > Linux-nvdimm mailing list > Linux-nvdimm@lists.01.org > https://lists.01.org/mailman/listinfo/linux-nvdimm