From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752196AbdLEDjQ (ORCPT <rfc822;w@1wt.eu>);
        Mon, 4 Dec 2017 22:39:16 -0500
Received: from mga14.intel.com ([192.55.52.115]:14773 "EHLO mga14.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751756AbdLEDjP (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 4 Dec 2017 22:39:15 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.45,362,1508828400"; 
   d="scan'208";a="9121432"
Date: Tue, 5 Dec 2017 11:39:12 +0800
From: Fengguang Wu <fengguang.wu@intel.com>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: LKML <linux-kernel@vger.kernel.org>,
        "Roberts, William C" <william.c.roberts@intel.com>,
        "Schaufler, Casey" <casey.schaufler@intel.com>,
        "Reshetova, Elena" <elena.reshetova@intel.com>,
        Philip Li <philip.li@intel.com>
Subject: Re: running leaking_addresses.pl
Message-ID: <20171205033912.du4a4c5vcmlptody@wfg-t540p.sh.intel.com>
References: <20171204233613.GI21565@eros>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20171204233613.GI21565@eros>
User-Agent: NeoMutt/20170609 (1.8.3)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Tobin,

On Tue, Dec 05, 2017 at 10:36:13AM +1100, Tobin C. Harding wrote:
>Hi,
>
>Recently scripts/leaking_addresses.pl was merged into the mainline with
>the hope of catching leaking kernel addresses.
>
>Would it be in scope for this script to be run by the kbuild test robot?
>Excuse my very little knowledge of the kbuild test robot but would this
>lead to the script being run on a number of kernels with varying
>configuration?

Yes it's in our plan. Bill Roberts also requested testing leaking_addresses.pl
and Philip has scheduled it to next quarter.

>In the event that this may be a possibility can I add that I do not have
>a suggestion for what to do with the output, can it go to LKML? I'm
>happy to be CC'd on the output to help investigate.

That'd be great! In general we are mainly responsible for catching
regressions. Due to limit of time and expertise, we leave the analyze
and bug fixing works to the first bad commit's authors and anyone who
are interested in looking into a class of problems. For example, we'll
CC some smatch and coccinelle regressions (possibly false positive) to
Dan and Julia.

Thanks,
Fengguang