Received: by 10.223.185.116 with SMTP id b49csp839745wrg; Tue, 20 Feb 2018 08:41:22 -0800 (PST) X-Google-Smtp-Source: AH8x224r+b/wXwuYYo5d2XR+A+T1QuNiTgPInjAroLjLDWH52L8jo7equfIyfQgmFTGQcJjXWl8Y X-Received: by 10.98.34.139 with SMTP id p11mr198742pfj.119.1519144882394; Tue, 20 Feb 2018 08:41:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519144882; cv=none; d=google.com; s=arc-20160816; b=aJP/dD3K1PYFB4fNevWVRSPUrIEMyLxClJg9Ps+hDJEfwlNdedNIY6/lqnZdaeWEQP 82dwq91Cvc5HmX9+XujY4ar4RqCJ/JeaiNmVstQBJlkzysZ6hjMhfbPleVDmPA32X5a8 2s4T9HrKxUyd9YaN+KpS7BzpDA4RtogOZ/7dIAtDj+VEYAONvtSRiv0zidk5sCNS9ew3 Ahj/bbb/N61jo2PmqOG/KQXGmEE1dtHfOvxr5CW8Zc4oHG1ElYvJUTJ9NiNBSnyyavNH qq/boAbvCzHFP5ha4jmso92OXhw1ckYmcXyA3yrv4GS5nFhSzjbX5Puxf5GqNLeuwf9n qwWg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=Rc8p6AuhAxUZakZuHhyXjOew7lfKcMQZihAb191TmQA=; b=KdxbHDbOby5xDgmGVokj7zmHQrRLNVUD6aUSBpdY0ZZFokWce2tnfBkN0woGsatU3c 8l2C/6tERxIng68UBRNgqySwqJ1OZ+W8bTldHikf9YpnxBmKowDPrfThgflbQGHTgHbW GJHKfkIlzlXvYAq428k18oU1TMO1A/BI/9OLd9PRdNeaDOwvI80o5EXdL7YT70UYOb0A lacukylzX+PKs8xUB0Hxz87iscM4tmn6UbD+tvCn9GxNDEWCLe2/gmQDnNYQq+4yMOve /zLEE5MGX+D0sRBP7tntrgYEs3wZueIWCtgr5I1VTKpUJDNuSn/OHJCD/LIN4Bc3FVLp NiNg== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m87si5939730pfk.383.2018.02.20.08.41.08; Tue, 20 Feb 2018 08:41:22 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753189AbeBTQke (ORCPT + 99 others); Tue, 20 Feb 2018 11:40:34 -0500 Received: from lhrrgout.huawei.com ([194.213.3.17]:26891 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753038AbeBTQk3 (ORCPT ); Tue, 20 Feb 2018 11:40:29 -0500 Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id AF89066C49D9B; Tue, 20 Feb 2018 16:40:25 +0000 (GMT) Received: from [10.122.225.51] (10.122.225.51) by smtpsuk.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 20 Feb 2018 16:40:27 +0000 Subject: Re: [PATCH 5/6] Pmalloc: self-test To: Kees Cook CC: Matthew Wilcox , Randy Dunlap , Jonathan Corbet , Michal Hocko , Laura Abbott , Jerome Glisse , Christoph Hellwig , "Christoph Lameter" , linux-security-module , Linux-MM , LKML , Kernel Hardening References: <20180212165301.17933-1-igor.stoppa@huawei.com> <20180212165301.17933-6-igor.stoppa@huawei.com> From: Igor Stoppa Message-ID: Date: Tue, 20 Feb 2018 18:40:04 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.122.225.51] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13/02/18 01:43, Kees Cook wrote: > On Mon, Feb 12, 2018 at 8:53 AM, Igor Stoppa wrote: [...] >> +obj-$(CONFIG_PROTECTABLE_MEMORY_SELFTEST) += pmalloc-selftest.o > > Nit: self-test modules are traditionally named "test_$thing.o" > (outside of the tools/ directory). ok [...] > I wonder if lkdtm should grow a test too, to validate the RO-ness of > the allocations at the right time in API usage? sorry for being dense ... are you proposing that I do something to lkdtm_rodata.c ? An example would probably help me understand. -- igor