[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080128192947.GA6720@cvg>
Date: Mon, 28 Jan 2008 22:29:47 +0300
From: Cyrill Gorcunov <gorcunov@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
Yinghai Lu <yhlu.kernel@...il.com>,
Jacob Shin <jacob.shin@....com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alexander Viro <viro@....linux.org.uk>
Subject: Re: [PATCH 2/5] x86: fix runtime error in
arch/x86/kernel/cpu/mcheck/mce_amd_64.c
[Ingo Molnar - Mon, Jan 28, 2008 at 08:01:49PM +0100]
|
| * Greg KH <gregkh@...e.de> wrote:
|
| > > Are kobjects protected against accidental copying? If not add &kobj
| > > to the 'magic value' too, and check that - it becomes
| > > copying-resistent that way and has the same cost to check. (which is
| > > negligible anyway)
| >
| > Oh, that's a very cool idea, I like it :)
|
| hey, you are welcome :-)
|
| [ I guess i should not mention that i've implemented list debugging for
| Linux that checksums the struct list contents and stores the checksum
| in it (offset by a magic value plus to address of the list head), and
| thus protects it against accidental corruption? It was capable of
| reliably detecting mixed up list_add() arguments for example, it
| detected list corruption of _every_ sort, it detected double
| list_del() and list_add() of an already active list member as well. It
| was even capable of detecting SMP races: two parallel unserialized
| list_del()'s on the same list head were detected and warned about as
| well. I guess i should release it one of these days? =B-) ]
|
interesting... something like hash checks in lockdep?
[...snip...]
- Cyrill -
--
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/
Powered by blists - more mailing lists