On Thu, Oct 19, 2017 at 05:19:49PM +0200, Petr Mladek wrote:
> On Thu 2017-10-19 17:34:44, Tobin C. Harding wrote:
[snip]
Good tips, thank you. Will merge every ones suggestions. V2 to come.
thanks,
Tobin.
On Thu, Oct 19, 2017 at 08:44:31AM -0400, Steven Rostedt wrote:
> On Thu, 19 Oct 2017 17:34:44 +1100
> "Tobin C. Harding" wrote:
>
> >
> > My usual disclaimer; I am a long way from being a Perl monger, any tips,
>
> I'm a semi Perl monger.
>
> > however trivial, most welcome.
> >
> > Parses d
On Thu 2017-10-19 17:34:44, Tobin C. Harding wrote:
> diff --git a/scripts/leaking_addresses.pl b/scripts/leaking_addresses.pl
> new file mode 100755
> index ..940547b716e3
> --- /dev/null
> +++ b/scripts/leaking_addresses.pl
> @@ -0,0 +1,139 @@
> +#!/usr/bin/env perl
> +#
> +# leaking_
On Thu, 19 Oct 2017 17:34:44 +1100
"Tobin C. Harding" wrote:
>
> My usual disclaimer; I am a long way from being a Perl monger, any tips,
I'm a semi Perl monger.
> however trivial, most welcome.
>
> Parses dmesg output first then;
>
> Algorithm walks the directory tree of /proc and /sys, ope
Currently we are leaking addresses from the kernel to user space. This
script as an attempt to find those leakages. Script parses `dmesg`
output and /proc and /sys files for suspicious entries.
Signed-off-by: Tobin C. Harding
---
My usual disclaimer; I am a long way from being a Perl monger, any
5 matches
Mail list logo
