From: Dave Jones <davej@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mateusz Guzik <mguzik@redhat.com>,
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 11:54:15 -0400 [thread overview]
Message-ID: <20140515155415.GA326@redhat.com> (raw)
In-Reply-To: <20140515150412.GP30445@twins.programming.kicks-ass.net>
On Thu, May 15, 2014 at 05:04:12PM +0200, Peter Zijlstra wrote:
> > > 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()
> > >
> > > 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.
>
> I hadn't looked that far.. I just manged to hit it two times in a row
> while waiting for my bug to trigger.
There's a ton of 'noise' like this that fuzzing turns up.
I've been collecting some of the stuff to shut it up..
http://codemonkey.org.uk/junk/silence-fuzz-testing-noise.patch
http://codemonkey.org.uk/junk/silence-noisy-deprecated-warnings-while-fuzzing.patch
I'm of the opinion that a user-triggerable WARN is a bug, but aparently
not everyone else feels that way.
Dave
next prev parent reply other threads:[~2014-05-15 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 13:38 WARN in do_rt_tgsigqueueinfo() Peter Zijlstra
2014-05-15 14:27 ` Mateusz Guzik
2014-05-15 15:04 ` Peter Zijlstra
2014-05-15 15:54 ` Dave Jones [this message]
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=20140515155415.GA326@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mguzik@redhat.com \
--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