From: Lee Revell <rlrevell@joe-job.com>
To: Dave Jones <davej@redhat.com>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Con Kolivas <con@kolivas.org>,
Kenneth W <kenneth.w.chen@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG at mm/rmap.c:491
Date: Thu, 24 Nov 2005 00:34:58 -0500 [thread overview]
Message-ID: <1132810499.1921.93.camel@mindpipe> (raw)
In-Reply-To: <20051124044009.GE30849@redhat.com>
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-11-24 5:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 22:56 Chen, Kenneth W
2005-11-23 23:24 ` Con Kolivas
2005-11-23 23:33 ` Chen, Kenneth W
2005-11-23 23:35 ` Con Kolivas
2005-11-23 23:38 ` Alistair John Strachan
2005-11-23 23:40 ` Con Kolivas
2005-11-24 4:38 ` Dave Jones
2005-11-23 23:36 ` Randy.Dunlap
2005-11-23 23:39 ` Randy.Dunlap
2005-11-23 23:35 ` Alistair John Strachan
2005-11-24 4:40 ` Dave Jones
2005-11-24 5:34 ` Lee Revell [this message]
2005-11-24 18:08 ` Zwane Mwaikambo
2005-11-24 6:57 ` Alistair John Strachan
2005-11-24 7:50 ` Hugh Dickins
2005-11-24 11:33 ` Lee Revell
2005-11-24 18:59 ` Dave Jones
2005-11-24 23:47 ` Keith Owens
2005-11-24 23:50 ` Con Kolivas
2005-11-25 10:43 ` Hugh Dickins
2005-11-25 10:45 ` Con Kolivas
2005-11-24 8:04 ` Hugh Dickins
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=1132810499.1921.93.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=con@kolivas.org \
--cc=davej@redhat.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=s0348365@sms.ed.ac.uk \
/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