linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Dave Jones <davej@redhat.com>
Cc: 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 06:57:11 +0000	[thread overview]
Message-ID: <200511240657.11480.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <20051124044009.GE30849@redhat.com>

On Thursday 24 November 2005 04:40, Dave Jones wrote:
> On Wed, Nov 23, 2005 at 11:35:15PM +0000, Alistair John Strachan wrote:
>  > On Wednesday 23 November 2005 23:24, Con Kolivas wrote:
>  > > Chen, Kenneth W writes:
>  > > > Has people seen this BUG_ON before?  On 2.6.15-rc2, x86-64.
>  > > >
>  > > > Pid: 16500, comm: cc1 Tainted: G    B 2.6.15-rc2 #3
>  > > >
>  > > > Pid: 16651, comm: sh Tainted: G    B 2.6.15-rc2 #3
>  > >
>  > >                        ^^^^^^^^^^
>  > >
>  > > Please try to reproduce it without proprietary binary modules linked
>  > > in.
>  >
>  > AFAIK "G" means all loaded modules are GPL, P is for proprietary
>  > modules.
>
> 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 ' ' ?

I don't understand the reasons for making the tainted string all the same 
length anyway. Why not just remove all the extra spaces?

Unless you know what you're looking for, I can assure you that:

Tainted: G    B SOMEOTHERTEXT

Is not intuitively readable (which text does B belong to?).

Tainted:    B SOMEOTHERTEXT

Is better, but still not very good. Why not drop the spaces?

3rd party parsing purposes?

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

--
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>

  parent reply	other threads:[~2005-11-24  6:57 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
2005-11-24 18:08         ` Zwane Mwaikambo
2005-11-24  6:57       ` Alistair John Strachan [this message]
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=200511240657.11480.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --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 \
    /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