From: "Tobin C. Harding" <me@tobin.cc>
To: Fengguang Wu <fengguang.wu@intel.com>
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
Date: Tue, 5 Dec 2017 14:58:23 +1100 [thread overview]
Message-ID: <20171205035823.GN21565@eros> (raw)
In-Reply-To: <20171205033912.du4a4c5vcmlptody@wfg-t540p.sh.intel.com>
On Tue, Dec 05, 2017 at 11:39:12AM +0800, Fengguang Wu wrote:
> 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.
Awesome.
> >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.
Ok cool, sign me up. I'm keen as mustard.
thanks,
Tobin
prev parent reply other threads:[~2017-12-05 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 23:36 running leaking_addresses.pl Tobin C. Harding
2017-12-05 3:39 ` Fengguang Wu
2017-12-05 3:58 ` Tobin C. Harding [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171205035823.GN21565@eros \
--to=me@tobin.cc \
--cc=casey.schaufler@intel.com \
--cc=elena.reshetova@intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philip.li@intel.com \
--cc=william.c.roberts@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).