From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754696AbaIHUr6 (ORCPT ); Mon, 8 Sep 2014 16:47:58 -0400 Received: from mail-oa0-f49.google.com ([209.85.219.49]:51643 "EHLO mail-oa0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754146AbaIHUr4 (ORCPT ); Mon, 8 Sep 2014 16:47:56 -0400 Message-ID: <540E15F8.2030900@converseincode.com> Date: Mon, 08 Sep 2014 15:47:52 -0500 From: Behan Webster User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Mimi Zohar CC: Dmitry Kasatkin , Thomas Gleixner , james.l.morris@oracle.com, linux-ima-devel@lists.sourceforge.net, linux-ima-user@lists.sourceforge.net, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, serge@hallyn.com, torvalds@linux-foundation.org, Mark Charlebois , =?UTF-8?B?SmFuLVNpbW9uIE3DtmxsZXI=?= , Linux Crypto Mailing List , Herbert Xu Subject: Re: [PATCH] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c References: <1409958360-8061-1-git-send-email-behanw@converseincode.com> <540A590F.1030407@converseincode.com> <540BBD9E.6050708@converseincode.com> <540D73C9.3000906@samsung.com> <540DA051.2030701@converseincode.com> <1410183821.8054.27.camel@dhcp-9-2-203-236.watson.ibm.com> In-Reply-To: <1410183821.8054.27.camel@dhcp-9-2-203-236.watson.ibm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/08/14 08:43, Mimi Zohar wrote: > > Behan, thank you for the explanation. No worries. I should have explained better. My apologies. > The same snippet of code used > here, and elsewhere in the kernel, is taken from the crypto subsystem. > Once it is resolved in the crypto subsystem, the same solution should be > propogated. > > Mimi Indeed that is my intention. I have tglx's suggested solution coded already. Just doing a bunch of allyesconfig builds to confirm all is compiling correctly. I will post all patches as a single patch set this time (posted to all concerned). I will repeat the explanation as well with the new patch set so everyone else in other subsystems sees those reasons as well. If this works for everyone I'll also go back and update the crypto patches for the subsystems that have already accepted my previous patches. Thanks, Behan -- Behan Webster behanw@converseincode.com