Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1788498imm; Wed, 6 Jun 2018 23:57:00 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJsq5eAoG+qyk50Ou2yo+if/iBO/BqxJYR0HIVucyCj5QVkG8rwpE4u+jHTksz0b+1f+U6w X-Received: by 2002:a17:902:9b8f:: with SMTP id y15-v6mr747855plp.187.1528354620612; Wed, 06 Jun 2018 23:57:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528354620; cv=none; d=google.com; s=arc-20160816; b=fTn7UPtmKYvZSrIFiFbEFcSFDbbcVBoQPUuswgl4qg1hjnGlDmH4hQjrvtmALEIG2t a3bNovuFZ6wJtv2WVrYZ6N7Tbf7VVQP1iOT3mXiiHffiR/0Bgh+BMaPv4dAN5Jtt7wWc BHdA9nOCC16GVfKTebXy+x05M4kw425lcHZVbL8PMLd0x0fMgNgc5jGJ1ZaYhe5T/qYt ecm+C4Ho0FS4ITa6+eG5M3VohOT6iPqoKzUKopuqo+ZPFkqq3Up8V4fogO6Lk/Gs9KH4 JRNuIO07gbXyq3i817/E8IKrwjsitPs8Z2zZv15c6zg6WPmykpWPCrcnsr4/B4SdoeJK xR6g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :content-language:accept-language:references:message-id:date :thread-index:thread-topic:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=lpZx8U9EuThh9BAzyyM7PjD7at/zt11f0chnf3Xpp1Y=; b=zrGSiJ36uI7wQieIzBo5XUUNYFoZdFHdGUhjnLZARPUNCEwj5u/ceu21xwpgdUCHOF wZXy4mNE5cUwhS3nJvM7BNh2PyA1EbzwM8LNtP/VoKi8FYliYyNVGRm9aW4Ratzf3f5k KxiOHro1JwgRPNqiL9jYvVVcTTo4VYXlrCp/O/ICa42dAkTNu6AI5l0lvR99u7tK7dPX Fx+lGbLGLD90RYvEhPyoaQuLeTYnq0q5a1MTGoqXst5WK1fg+eNyn3xUqdC8qVL/MJWd 7NhzzImQOTFT50xoFM9l2keLSDB3XxpDR8Ad1Pn6ae8I913llyAr2XLnuJZ9oWiP8SKO ETlw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@synopsys.com header.s=mail header.b=cxl33Uvu; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=synopsys.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f127-v6si39490410pgc.503.2018.06.06.23.56.45; Wed, 06 Jun 2018 23:57:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@synopsys.com header.s=mail header.b=cxl33Uvu; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=synopsys.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752669AbeFGG4Y (ORCPT + 99 others); Thu, 7 Jun 2018 02:56:24 -0400 Received: from smtprelay6.synopsys.com ([198.182.37.59]:42497 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751797AbeFGG4W (ORCPT ); Thu, 7 Jun 2018 02:56:22 -0400 Received: from mailhost.synopsys.com (mailhost1.synopsys.com [10.12.238.239]) by smtprelay.synopsys.com (Postfix) with ESMTP id DAD7F1E03E8; Thu, 7 Jun 2018 08:56:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=synopsys.com; s=mail; t=1528354581; bh=U/B/vEGZzSoiW3M/fjxBTgAGW+pLRtonYKME16fX5Ds=; h=From:To:CC:Subject:Date:References:From; b=cxl33UvuJLuH3SEFdUbCTdhOifYcRFM4jyT4O/I85EQMihHTEpLbySnn6moaKxC8x 00sDbUNqKRWHwmq9KoMb7mVfQyPYUQgoMoefPHKvLKkcOPeIQYcjPOwltEE5BMhAdQ 497YxcBc8Adwel0JyoKwvWBN8ejIQdewzzriR0brT4lefKH8U2Aru7tqbZqA2/TmR4 ei9bw9hdBeal1yDygKgdVD265yeNoU+yfAGMSMbbt9jksdYUhkGyZtXUOiyBZhB3No t2iYn1HULeOE0Z8INnZA4Lj4Xw1m8ZONntmueAcFCJBmYjk8lS/bMnhHpaV8EUlBk9 lsWmC/MecAMpQ== Received: from us01wehtc1.internal.synopsys.com (us01wehtc1.internal.synopsys.com [10.12.239.235]) by mailhost.synopsys.com (Postfix) with ESMTP id 7D8975B1D; Wed, 6 Jun 2018 23:56:19 -0700 (PDT) Received: from IN01WEHTCB.internal.synopsys.com (10.144.199.106) by us01wehtc1.internal.synopsys.com (10.12.239.235) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 6 Jun 2018 23:55:53 -0700 Received: from IN01WEMBXA.internal.synopsys.com ([fe80::ed6f:22d3:d35:4833]) by IN01WEHTCB.internal.synopsys.com ([::1]) with mapi id 14.03.0361.001; Thu, 7 Jun 2018 12:25:43 +0530 From: Ladvine D Almeida To: Jens Axboe , Ladvine D Almeida , Christoph Hellwig CC: Hannes Reinecke , "ming.lei@redhat.com" , "linux-block@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Manjunath M Bettegowda , Prabu Thangamuthu , Tejas Joglekar , Joao Pinto , Johannes Thumshirn , "Milan Broz" , Alasdair Kergon , Mike Snitzer , device-mapper development , "Eric Biggers" , Theodore Ts'o , Jaegeuk Kim Subject: Re: [PATCH] block: Add block level changes for inline encryption Thread-Topic: [PATCH] block: Add block level changes for inline encryption Thread-Index: AQHT+YBsRN+yoa9w10qCAP3oXXj0ew== Date: Thu, 7 Jun 2018 06:55:42 +0000 Message-ID: References: <20180601081330.GA13067@infradead.org> <918609fa-8721-0ee1-801e-4c29b64ac9ae@kernel.dk> Accept-Language: en-US, en-IN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.12.239.235] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 07 June 2018 02:53 AM, Jens Axboe wrote:=0A= > On 6/6/18 1:35 AM, Ladvine D Almeida wrote:=0A= >> On Friday 01 June 2018 09:13 AM, Christoph Hellwig wrote:=0A= >>> On Mon, May 28, 2018 at 02:43:09PM +0100, Ladvine D Almeida wrote:=0A= >>>> This patch introduces new variable under bio structure to=0A= >>>> facilitate inline encryption. This variable is used to=0A= >>>> associate I/O requests to crypto information.=0A= >>> This seems to be missing a whole lot of context. Where is the whole=0A= >>> series showing what you are trying to do?=0A= >>>=0A= >> Christoph,=0A= >>=0A= >> The patches are generated in the below > manner, with a thought of=0A= >> sending separately to the MAINTAINERS responsible for each.=0A= > What both Christoph and I have said is that it's _impossible_ to review= =0A= > changes when you don't know what is being built on top of it. The block= =0A= > change, by itself, is utterly useless. The use case needs to be seen.=0A= > But apart from that, my comments on why it's doing it completely=0A= > backwards still apply, and I've outlined how you need to fix it. The=0A= > patch, in its current form, isn't going anywhere.=0A= >=0A= Jens,=0A= =0A= Since there are implementation level concerns on both device mapper layer a= nd block layer, I will investigate=0A= =0A= more and work on those lines. I can send the full patch series to the relev= ant maintainers after addressing the=0A= =0A= issues.=0A= =0A= Regards,=0A= =0A= Ladvine=0A= =0A=