public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: running leaking_addresses.pl
Date: Tue, 5 Dec 2017 10:36:13 +1100	[thread overview]
Message-ID: <20171204233613.GI21565@eros> (raw)

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?

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.

thanks,
Tobin.

             reply	other threads:[~2017-12-04 23:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 23:36 Tobin C. Harding [this message]
2017-12-05  3:39 ` running leaking_addresses.pl Fengguang Wu
2017-12-05  3:58   ` Tobin C. Harding

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=20171204233613.GI21565@eros \
    --to=me@tobin.cc \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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