linux-kernel - Re: [patch 0/5] object debugging infrastructure V2

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]

Message-ID: <alpine.LFD.1.00.0803060828180.3099@apollo.tec.linutronix.de>
Date:	Thu, 6 Mar 2008 08:54:13 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Greg KH <greg@...ah.com>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [patch 0/5] object debugging infrastructure V2

On Wed, 5 Mar 2008, Greg KH wrote:
> Here's a patch adding kobjects to this infrastructure (I didn't use a
> new CONFIG option, which it probably should be.)
> 
> Does this look correct?  I can't tell if this is going to catch
> anything, as my trees all seem to have these kinds of bugs worked out
> now, as we are already catching a number of these types of things
> already with kobjects.
> 
> Should I be doing more checks?  Different things based on the state of
> the object?

Depends on the kind of state of objects you have. Right now you only
track the initialized and the destroyed state. The question is whether
there is some other state like "access". I have a look.

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/