From: Mateusz Guzik <mguzik@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: WARN in do_rt_tgsigqueueinfo()
Date: Thu, 15 May 2014 16:27:24 +0200 [thread overview]
Message-ID: <20140515142723.GB22041@mguzik.redhat.com> (raw)
In-Reply-To: <20140515133834.GN13658@twins.programming.kicks-ass.net>
On Thu, May 15, 2014 at 03:38:34PM +0200, Peter Zijlstra wrote:
> Hi Thomas, Oleg,
>
>
> trinity$ MALLOC_CHECK_=0 ./trinity -xinit_module -xreboot -xshutdown -xunshare -xnfsservctl -xclock_nanosleep -xuselib -xumount -xmount -m --quiet -C 400 -l off -xmremap
>
> [watchdog] kernel became tainted! (512/0) Last seed was 4072360471
>
> [15908.562512] ------------[ cut here ]------------
> [15908.567245] WARNING: CPU: 22 PID: 3312 at /usr/src/linux-2.6/kernel/signal.c:3060 do_rt_tgsigqueueinfo+0xb4/0xc0()
> [15908.577715] Modules linked in:
> [15908.580857] CPU: 22 PID: 3312 Comm: trinity-c198 Not tainted 3.15.0-rc5-01700-g505011124ad0-dirty #1070
> [15908.590412] Hardware name: Supermicro X8DTN/X8DTN, BIOS 4.6.3 01/08/2010
> [15908.597228] 0000000000000009 ffff880428715e40 ffffffff81682052 0000000000000000
> [15908.604834] ffff880428715e78 ffffffff8109808c 0000000000000001 000000000000ffff
> [15908.612402] 00000000efdcefbf 00000000efdcefbf 0000000000000129 ffff880428715e88
> [15908.619941] Call Trace:
> [15908.622423] [<ffffffff81682052>] dump_stack+0x4e/0x7a
> [15908.627600] [<ffffffff8109808c>] warn_slowpath_common+0x8c/0xc0
> [15908.633658] [<ffffffff810980da>] warn_slowpath_null+0x1a/0x20
> [15908.639535] [<ffffffff810a9914>] do_rt_tgsigqueueinfo+0xb4/0xc0
> [15908.645591] [<ffffffff810a99f1>] SYSC_rt_tgsigqueueinfo+0x61/0x80
> [15908.651851] [<ffffffff810abb2e>] SyS_rt_tgsigqueueinfo+0xe/0x10
> [15908.657946] [<ffffffff8168a842>] system_call_fastpath+0x16/0x1b
> [15908.664036] ---[ end trace 02450728e2526283 ]---
>
>
> This is apparently a very common thing to hit according to google.
Well, it warns about an argument received from userland, so nothing fishy
going on as far as kernel consistency is concerned if that's what you mean.
--
Mateusz Guzik
next prev parent reply other threads:[~2014-05-15 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 13:38 Peter Zijlstra
2014-05-15 14:27 ` Mateusz Guzik [this message]
2014-05-15 15:04 ` Peter Zijlstra
2014-05-15 15:54 ` Dave Jones
2014-05-15 15:56 ` Peter Zijlstra
2014-05-15 16:09 ` Mateusz Guzik
2014-05-15 18:04 ` Oleg Nesterov
2014-05-15 16:46 ` Thomas Gleixner
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=20140515142723.GB22041@mguzik.redhat.com \
--to=mguzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®