From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Tue, 5 Jul 2016 23:04:02 +0200 (CEST) Received: by mail-wm0-x243.google.com with SMTP id c82so31348360wme.3 for ; Tue, 05 Jul 2016 14:04:02 -0700 (PDT) References: From: Milan Broz Message-ID: <40d55a0f-b675-f947-c205-78d1bbbcec86@gmail.com> Date: Tue, 5 Jul 2016 23:03:59 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] dm-crypt.ko external kernel module List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Tapas Sarangi Cc: dm-crypt On 07/05/2016 07:53 PM, Tapas Sarangi wrote: > Is there a way to build external kernel module dm-crypt.ko that is > not included by default in the kernel configs ? Is there any > instruction on where to get the source tarball etc=85 ? While is possible (in some configurations) to build kernel module separately with the help of simple makefile and some kernel headers, it is not the way= dmcrypt should be used. The reason is that code is directly dependent on internal kernel structures and also requires some other config options (like device-mapper infrastruct= ure, kernel crypto API and particular kernel block layer settings). The dmcrypt is included in the mainline kernel, there is no need for separa= te source tarball, just use mainline kernel source (drivers/md/dmcrypt.c is the module core). Your distro must have these sources available if they are distributing bina= ries (it is GPL code), so you can always compile modules from it. Milan