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.7 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_PASS autolearn=unavailable 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 164C9C04AAD for ; Mon, 6 May 2019 23:54:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D230720830 for ; Mon, 6 May 2019 23:54:38 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="Z9f22nwD" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727159AbfEFXyh (ORCPT ); Mon, 6 May 2019 19:54:37 -0400 Received: from merlin.infradead.org ([205.233.59.134]:60382 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726236AbfEFXyh (ORCPT ); Mon, 6 May 2019 19:54:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=8JRNJiv/VbYM71AEUd80ItdkLhtYyNFmfNzyleo5x8k=; b=Z9f22nwD+1hikEnxcUVZ6/kdY6 ceY5R7/daKmMoZyF0FZg0Qq1nOIbFA3/3Aivi1hXpVA8R4eTj42EpYmMaIDMsD2VG5MdFKk1u36qe l84Hn/dhZU7Ktl7tx/1a3SC2NGAMJeTqCOJfCjaONCeoYGjgrK+Bog5A2OkbTCAHLUPQLBzDqVThE N/iYkZjMPH7jGT1okIxtUOckG1RKtBsag2xM+tjI1trM9IoyHGio9jJ7ReE2ZMA1jmSPEBxVvvtTF l/NIvS/28uaXgFtXA29RHSkhfqgDXUrzCNPSpljSQVjtSVt199d4Zk9wRoRSOdUh4ey+xAAHQkeLs QzNtUtUw==; Received: from static-50-53-52-16.bvtn.or.frontiernet.net ([50.53.52.16] helo=midway.dunlab) by merlin.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1hNnRH-0001uM-Jw; Mon, 06 May 2019 23:54:32 +0000 Subject: Re: [RFC PATCH 1/4] block: Block Layer changes for Inline Encryption Support To: Satya Tangirala , linux-block@vger.kernel.org, linux-scsi@vger.kernel.org, linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org Cc: Parshuram Raju Thombare , Ladvine D Almeida , Barani Muthukumaran , Kuohong Wang References: <20190506223544.195371-1-satyat@google.com> <20190506223544.195371-2-satyat@google.com> From: Randy Dunlap Message-ID: Date: Mon, 6 May 2019 16:54:30 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190506223544.195371-2-satyat@google.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On 5/6/19 3:35 PM, Satya Tangirala wrote: > diff --git a/block/Kconfig b/block/Kconfig > index 028bc085dac8..65213769d2a2 100644 > --- a/block/Kconfig > +++ b/block/Kconfig > @@ -187,6 +187,22 @@ config BLK_SED_OPAL > Enabling this option enables users to setup/unlock/lock > Locking ranges for SED devices using the Opal protocol. > > +config BLK_CRYPT_CTX > + bool > + > +config BLK_KEYSLOT_MANAGER > + bool > + > +config BLK_CRYPTO > + bool "Enable encryption in block layer" > + select BLK_CRYPT_CTX > + select BLK_KEYSLOT_MANAGER > + help > + Build the blk-crypto subsystem. > + Enabling this lets the block layer handle encryption, > + so users can take advantage of inline encryption > + hardware if present. Last 4 lines should be indented with 1 tab + 2 spaces, please. -- ~Randy