From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: Kernel BUG at mm/rmap.c:491 From: Lee Revell In-Reply-To: <20051124044009.GE30849@redhat.com> References: <200511232256.jANMuGg20547@unix-os.sc.intel.com> <200511232335.15050.s0348365@sms.ed.ac.uk> <20051124044009.GE30849@redhat.com> Content-Type: text/plain Date: Thu, 24 Nov 2005 00:34:58 -0500 Message-Id: <1132810499.1921.93.camel@mindpipe> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Dave Jones Cc: Alistair John Strachan , Con Kolivas , Kenneth W , linux-mm@kvack.org, linux-kernel@vger.kernel.org List-ID: On Wed, 2005-11-23 at 23:40 -0500, Dave Jones wrote: > The 'G' seems to confuse a hell of a lot of people. > (I've been asked about it when people got machine checks a lot over > the last few months). > > Would anyone object to changing it to conform to the style of > the other taint flags ? Ie, change it to ' ' ? While you're at it why not print a big loud warning that says not to post the Oops to LKML, and instructing the user to reproduce with a clean kernel, if the P flag is set? Presumably the reason for the terse output is to get the maximum possible debug information on the screen, but we don't care about stack traces for tainted kernels anyway. Something must need fixing, as the volume of tainted Oops reports shows no sign of diminishing, and the users aren't getting any less pissy when you tell them to come back with a clean bug report. Lee -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org