From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754820AbaEOPys (ORCPT ); Thu, 15 May 2014 11:54:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41312 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753401AbaEOPyq (ORCPT ); Thu, 15 May 2014 11:54:46 -0400 Date: Thu, 15 May 2014 11:54:15 -0400 From: Dave Jones To: Peter Zijlstra Cc: Mateusz Guzik , Oleg Nesterov , Thomas Gleixner , linux-kernel@vger.kernel.org Subject: Re: WARN in do_rt_tgsigqueueinfo() Message-ID: <20140515155415.GA326@redhat.com> Mail-Followup-To: Dave Jones , Peter Zijlstra , Mateusz Guzik , Oleg Nesterov , Thomas Gleixner , linux-kernel@vger.kernel.org References: <20140515133834.GN13658@twins.programming.kicks-ass.net> <20140515142723.GB22041@mguzik.redhat.com> <20140515150412.GP30445@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140515150412.GP30445@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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