From: "Nish Aravamudan" <nish.aravamudan@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <clameter@sgi.com>,
linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>,
Andy Whitcroft <apw@shadowen.org>,
Martin Bligh <mbligh@mbligh.org>
Subject: Re: SLUB: Use ilog2 instead of series of constant comparisons.
Date: Wed, 6 Jun 2007 13:29:25 -0700 [thread overview]
Message-ID: <29495f1d0706061329o457d3c97q3a93c4ab2581a1c@mail.gmail.com> (raw)
In-Reply-To: <20070606131121.a8f7be78.akpm@linux-foundation.org>
On 6/6/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 6 Jun 2007 11:36:07 -0700 (PDT) Christoph Lameter <clameter@sgi.com> wrote:
>
> > On Wed, 6 Jun 2007, Andrew Morton wrote:
> >
> > > This caused test.kernel.org's power4 build to blow up:
> > >
> > > http://test.kernel.org/abat/93315/debug/test.log.0
> > >
> > > fs/built-in.o(.text+0x148420): In function `.CalcNTLMv2_partial_mac_key':
> > > : undefined reference to `.____ilog2_NaN'
> >
> > Hmmm... Weird message that does not allow too much analysis.
> > The __ilog2_NaN comes about if 0 or a negative number is passed to ilog.
> > There is no way for that to happen since we check for KMALLOC_MIN_SIZE
> > and KMALLOC_MAX_SIZE in kmalloc_index() and an unsigned value is used.
> >
> > There is also nothing special in CalcNTLMv2_partial_mac_key(). Two
> > kmallocs of 33 bytes and 132 bytes each.
>
> Yes, the code all looks OK. I suspect this is another case of the compiler
> failing to remove unreachable stuff.
>
> > Buggy compiler (too much stress on constant folding)? Or hardware? Can we
> > rerun the test?
>
> It happened multiple times:
> http://test.kernel.org/functional/pSeries-101_2.html
>
> I'm sure there's a way of extracting the compiler version out of
> test.kernel.org but I can't see it there. Andy, maybe we should toss a gcc
> --version in there or something?
I went and looked at one of the GOOD jobs and acc'g to that, the gcc is
gcc version 3.3.3 (SuSE Linux)
(http://test.kernel.org/abat/93029/summary)
I agree, seems like it would be handy to spit that out somewhere nicer
and easier to get to. Maybe the machine links at the top should point
to a summary page which has a link to the .config, machine info, etc?
(more indirection, but may be ok).
Thanks,
Nish
--
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:[~2007-06-06 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 19:51 Christoph Lameter
2007-05-22 8:45 ` Pekka Enberg
2007-06-06 17:08 ` Andrew Morton
2007-06-06 18:36 ` Christoph Lameter
2007-06-06 20:11 ` Andrew Morton
2007-06-06 20:28 ` Christoph Lameter
2007-06-06 20:34 ` Andrew Morton
2007-06-06 20:41 ` Martin Bligh
2007-06-06 20:52 ` Christoph Lameter
2007-06-06 23:19 ` Andrew Morton
2007-06-06 23:50 ` Christoph Lameter
2007-06-07 0:01 ` Nish Aravamudan
2007-06-07 3:49 ` Christoph Lameter
2007-06-06 23:31 ` Nish Aravamudan
2007-06-07 7:40 ` Andy Whitcroft
2007-06-06 20:43 ` Christoph Lameter
2007-06-06 20:29 ` Nish Aravamudan [this message]
2007-06-07 7:48 ` Andy Whitcroft
2007-06-07 7:58 ` Andy Whitcroft
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=29495f1d0706061329o457d3c97q3a93c4ab2581a1c@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=penberg@cs.helsinki.fi \
/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