From: Or Gerlitz <ogerlitz@voltaire.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Or Gerlitz <or.gerlitz@gmail.com>, Andrew Morton <akpm@osdl.org>,
open-iscsi@googlegroups.com, linux-kernel@vger.kernel.org,
openib-general@openib.org, Christoph Lameter <clameter@sgi.com>
Subject: Re: [openib-general] Re: possible bug in kmem_cache related code
Date: Mon, 01 May 2006 16:40:48 +0300 [thread overview]
Message-ID: <44560FE0.2000004@voltaire.com> (raw)
In-Reply-To: <1146293055.11279.2.camel@localhost>
Pekka Enberg wrote:
> On Fri, 2006-04-28 at 21:24 +0200, Or Gerlitz wrote:
>> Yes, i can reproduce this at will, no local modifications, my system
>> is amd dual x86_64, i have attached my .config to the first email of
>> this thread, and also mentioned that some CONFIG_DEBUG_ options are
>> set, including one related to slab debugging.
>>
> Yeah, arch/um/. Unfortunately I don't have a SMP box, so I probably
> can't reproduce this. You could try git bisect to isolate the offending
> changeset.
mmm, I might be able to do git bisection later this week or next week.
However, for the mean time can more people of the openib and open iscsi
communities set 2.6.17-rcX to see that the issue reproduces with my
synthetic module and with ib/iscsi code (you know this kernel will be
out in few weeks from now...)
Or.
next prev parent reply other threads:[~2006-05-01 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 8:40 possible bug in kmem_cache related code Or Gerlitz
2006-04-27 11:19 ` Pekka Enberg
2006-04-27 22:22 ` Christoph Lameter
2006-04-28 6:03 ` Pekka J Enberg
2006-04-28 8:10 ` Pekka J Enberg
2006-04-28 19:24 ` [openib-general] " Or Gerlitz
2006-04-29 6:44 ` Pekka Enberg
2006-05-01 13:40 ` Or Gerlitz [this message]
2006-05-03 22:04 ` Ard van Breemen
[not found] <OF74DEDEC9.CB33A0DB-ON8725715E.0023266E-8825715E.002874C1@us.ibm.com>
2006-04-28 6:46 ` Christoph Lameter
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=44560FE0.2000004@voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=open-iscsi@googlegroups.com \
--cc=openib-general@openib.org \
--cc=or.gerlitz@gmail.com \
--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