20.02.2013 22:24, Dave Jones пишет:
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.
Thanks, Dave. I've seen a couple of issues when running trinity in KVM
somewhere in the same place.
Look like message queue itself has been destroyed somewhere in the past.
Have no idea how this can happen yet but still searching and will inform you in
case of any fixes.
Dave
--
Best regards,
Stanislav Kinsbursky
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
