linux-kernel - Re: [patch 2/5] infrastructure to debug (dynamic) objects

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 21 Mar 2008 22:24:53 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Randy Dunlap <randy.dunlap@...cle.com>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, Greg KH <greg@...ah.com>
Subject: Re: [patch 2/5] infrastructure to debug (dynamic) objects

On Fri, 21 Mar 2008, Randy Dunlap wrote:
> > +	  If you say Y here, additional code will be inserted into the
> > +	  kernel to track the life time of various objects and validate
> 
>                               lifetime

Fixed.
 
> > +	help
> > +	  This enables checks whether a k/v free operation frees an area
> 
> Please say "kfree/vfree" so that we (I, others) don't have to think
> "what the heck is a k/v free operation?".

Ooops. Missed that one. Fixed it in the docs already.
 
> > +/*
> > + * We run out of memory. That means we probably have tons of objects
> 
>          ran

Sigh. This is one of the words which hunt me since school.

> > +/**
> > + * debug_object_init_on_stack - debug checks when an object on stack is
> > + *				initialized
> 
> Unfortunately the first line of kernel-doc notation ("short description")
> is limited to one line.  Even if it exceeds 80 columns.  :(

Fixed
 
Thanks,

	tglx
--
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/