public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Robin Holt <holt@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: [Patch] Incoming XPC channel messages can come in after the channel's partition structures have been torn down.
Date: Mon, 18 Oct 2010 14:52:27 -0500	[thread overview]
Message-ID: <20101018195227.GK14064@sgi.com> (raw)
In-Reply-To: <20101018124055.26325ea5.akpm@linux-foundation.org>

On Mon, Oct 18, 2010 at 12:40:55PM -0700, Andrew Morton wrote:
> On Mon, 18 Oct 2010 08:35:08 -0500
> Robin Holt <holt@sgi.com> wrote:
> 
> > Under some workloads, some channel messages have been observed being
> > delayed on the sending side past the point where the receiving side
> > has been able to tear down its partition structures.  This condition is
> > already detected in xpc_handle_activate_IRQ_uv(), but that information
> > is not given to xpc_handle_activate_mq_msg_uv().  As a result,
> > xpc_handle_activate_mq_msg_uv() assumes the structures still exist and
> > references them.
> 
> With what result?  Machine goes boom?
> 
> Would you consider this a 2.6.36 fix?  Backport to -stable?

I would consider it a backport to stable.  It is a NULL pointer deref.
This pach applies back to 2.6.32.  I did not try older kernels than
that.

Robin

      reply	other threads:[~2010-10-18 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 13:35 [Patch] Incoming XPC channel messages can come in after the channel's partition structures have been torn down Robin Holt
2010-10-18 19:40 ` Andrew Morton
2010-10-18 19:52   ` Robin Holt [this message]

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=20101018195227.GK14064@sgi.com \
    --to=holt@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@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