linux-kernel - Re: [RFC PATCH 4/5] kmemtrace: SLUB hooks.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 12 Jul 2008 16:36:49 +0300
From:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
To:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
Cc:	Christoph Lameter <cl@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [RFC PATCH 4/5] kmemtrace: SLUB hooks.

On Sat, 12 Jul 2008 16:28:36 +0300
Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro> wrote:

> On Fri, 11 Jul 2008 09:48:03 -0500
> Christoph Lameter <cl@...ux-foundation.org> wrote:
> 
> > Pekka Enberg wrote:
> >  
> > > Christoph, can you please take a look at this?
> > 
> > Yeah. I saw it. Is there some high level description as to how this
> > is going to be used?
> 
> Here is the userspace application's git tree:
> http://repo.or.cz/w/kmemtrace-user.git

Basically, you go like this:
1. Boot the kernel, preferably into 'single' runlevel.
2. Mount debugfs and whatever other filesystems.
3. Run kmemtraced, wait a few seconds and stop it.
4*. Check /debug/kmemtrace/total_overruns (debugfs is mounted on /debug)
to see if there were any buffer overruns.
5*. Run kmemtrace-check on all CPU cpu*.out to see if there are any
erroneous events.
6. Run kmemtrace-report with no parameters to get a short summary of
how the allocator performs.

* - you can optionally skip these steps.

To build the userspace app, launch './configure' when running on that
particular kmemtrace-enabled kernel. It should correctly detect the
headers directory. Otherwise, add KERNEL_SOURCES variable as an
argument to configure. Then run 'make'.

BTW, that repo may change, so don't rely on those commits to be
consistent for a long time. I could delete them all and restructure the
project.

	Eduard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/