From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, Yinghai Lu <yhlu.kernel@gmail.com>,
Jacob Shin <jacob.shin@amd.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alexander Viro <viro@ftp.linux.org.uk>
Subject: Re: [PATCH 2/5] x86: fix runtime error in arch/x86/kernel/cpu/mcheck/mce_amd_64.c
Date: Mon, 28 Jan 2008 22:42:20 +0300 [thread overview]
Message-ID: <20080128194220.GB6720@cvg> (raw)
In-Reply-To: <20080128190149.GA24424@elte.hu>
[Ingo Molnar - Mon, Jan 28, 2008 at 08:01:49PM +0100]
|
| * Greg KH <gregkh@suse.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-) ]
|
did miss some words while reading this... ;)
really sorry, drop the mail i sent please
- Cyrill -
next prev parent reply other threads:[~2008-01-28 19:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 23:37 [GIT PATCH] driver core fixes against 2.6.24 Greg KH
2008-01-27 23:38 ` [PATCH 1/5] Driver core: Fix up build when CONFIG_BLOCK=N Greg Kroah-Hartman
2008-01-27 23:38 ` [PATCH 2/5] x86: fix runtime error in arch/x86/kernel/cpu/mcheck/mce_amd_64.c Greg Kroah-Hartman
2008-01-28 12:24 ` Ingo Molnar
2008-01-28 17:37 ` Greg KH
2008-01-28 17:57 ` Ingo Molnar
2008-01-28 18:32 ` Greg KH
2008-01-28 19:01 ` Ingo Molnar
2008-01-28 19:29 ` Cyrill Gorcunov
2008-01-28 19:42 ` Cyrill Gorcunov [this message]
2008-01-27 23:38 ` [PATCH 3/5] Module: check to see if we have a built in module with the same name Greg Kroah-Hartman
2008-01-28 23:54 ` Jan Engelhardt
2008-01-29 6:20 ` Rusty Russell
2008-01-27 23:38 ` [PATCH 4/5] Driver core: add bus_find_device_by_name function Greg Kroah-Hartman
2008-01-27 23:38 ` [PATCH 5/5] PPC: Fix powerpc vio_find_name to not use devices_subsys Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080128194220.GB6720@cvg \
--to=gorcunov@gmail.com \
--cc=gregkh@suse.de \
--cc=jacob.shin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.