public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: general protection fault in do_msgrcv  [3.8]
Date: Wed, 20 Feb 2013 13:24:32 -0500	[thread overview]
Message-ID: <20130220182432.GA32377@redhat.com> (raw)
In-Reply-To: <512487FA.9090102@parallels.com>

On Wed, Feb 20, 2013 at 12:23:22PM +0400, Stanislav Kinsbursky wrote:

 > > Pid: 887, comm: trinity-child2 Not tainted 3.8.0+ #57 Gigabyte Technology Co., Ltd. GA-MA78GM-S2H/GA-MA78GM-S2H
 > > RIP: 0010:[<ffffffff812aebba>]  [<ffffffff812aebba>] do_msgrcv+0x22a/0x670
 > > ...
 > > Looks like Stanislav recently changed this code, so problem was likely introduced
 > > in those changes.
 > >
 > 
 > Is it easy to reproduce? Do you use KVM?

Only hit it once so far, no KVM

 > There is a NULL selinux handler bug fix by Stephen Smalley here:
 > https://lkml.org/lkml/2013/2/6/663
 > 
 > But anyway, this bug fix affects only the case, when MSG_COPY flag is set.
 > 
 > And this is not your case, I suppose?

>From my reading of the traces, I'd say not. It looks like I'm oopsing before
we even get to the SELinux hooks.

	Dave


  parent reply	other threads:[~2013-02-20 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 18:04 general protection fault in do_msgrcv [3.8] Dave Jones
2013-02-20  8:23 ` Stanislav Kinsbursky
2013-02-20 10:03   ` Gleb Natapov
2013-02-20 10:13     ` Stanislav Kinsbursky
2013-02-20 18:24   ` Dave Jones [this message]
2013-02-21  5:11     ` Stanislav Kinsbursky

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=20130220182432.GA32377@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skinsbursky@parallels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox