public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Silent data corruption caused by XPC.
Date: Mon, 07 Aug 2006 17:27:00 +0000	[thread overview]
Message-ID: <20060807172700.GA24663@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <20060807154608.GC15674@lnx-holt.americas.sgi.com>

On Mon, Aug 07, 2006 at 08:57:51AM -0700, Luck, Tony wrote:
> > and verified it works.  I also added DBUG_ON statements to help catch
> > this if a similar situation is encountered.
> 
> Can you just do this once at alloc time rather than at every use?

Dean and I liked the idea at first, but hashed it over more.  My intent
with putting them right before the bte_copy was to trap the event where
a copy was going to be initiated that would corrupt memory.  If I put
them at allocation time only, any changes in the allocation would not
necessarily be caught.  I think we would like to leave them where they
are at unless you have a strong objection.  They are DBUG_ON() instead
of BUG_ON() so they should not have a performance impact normally.

If you would like it moved to allocation time, it will make
the patch smaller and more clean as we will move it into
xpc_kmalloc_cacheline_aligned.  Dean said he will handle that if you
desire.

Thanks,
Robin

  parent reply	other threads:[~2006-08-07 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 15:46 Silent data corruption caused by XPC Robin Holt
2006-08-07 15:57 ` Luck, Tony
2006-08-07 17:27 ` Robin Holt [this message]
2006-08-07 17:51 ` Luck, Tony

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=20060807172700.GA24663@lnx-holt.americas.sgi.com \
    --to=holt@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox