linux-kernel - Re: 2.6.22-rc2-mm1

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]

Message-ID: <Pine.LNX.4.64.0705240938070.27844@schroedinger.engr.sgi.com>
Date:	Thu, 24 May 2007 09:40:38 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.22-rc2-mm1

On Thu, 24 May 2007, Ingo Molnar wrote:

> 
> when constructing debug output it's a good idea to make it as 
> 'context-free' as possible. I.e. instead of saying 'Filler' and 
> explaining it somewhere in Documentation/*, just say:
> 
>   Expected memory values at 0xc90f6d50:  5a 5a 5a 5a 5a 5a 5a 5a
>   ... but found the following values:    12 34 56 78 90 12 34 56

Meaning just print the corrupted values? Otherwise the text will take up 
a lot of real estate and will make it impossible to view the actual object 
contents.

I think I can skip the filler etc if its not corrupted. Maybe that will 
help?

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