Linux bluetooth development
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Adrian Bunk <bunk@stusta.de>,
	Patrick Caulfield <pcaulfie@redhat.com>,
	David Teigland <teigland@redhat.com>,
	bluez-devel@lists.sourceforge.net,
	Marcel Holtmann <marcel@holtmann.org>,
	Jiri Kosina <jkosina@suse.cz>,
	Dmitry Torokhov <dtor@insightbb.com>
Subject: Re: 2.6.22-rc7: known regressions with patches v2
Date: Sat, 7 Jul 2007 16:07:15 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707071557160.16503@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <6bffcb0e0707070959m12ba9b66n8587605eb1f6c21e@mail.gmail.com>

On Sat, 7 Jul 2007, Michal Piotrowski wrote:

> > If you're looking for someone to blame, consider the fact that this has
> > gone away now I've switched back to slab. :)
> Yup, I forgot to add Christoph to CC  :)

Hmmmm.. Cannot see the corruption in the dump since it only includes 128 
bytes and it seems to have occurred way into the object. If you want to 
dump 32k to your syslog to see the corruption then look at the 
print_trailer() function and change the parameter of the call to 
print_section

	print_section("Object", p, min(s->objsize, 128));


This is a 32k sized slab and SLAB does not allow debugging on power of two 
slabs > pagesize.... No surprise that SLAB does not complain.

What are these functions "malloc" and "free"? Would be good if those 
would be using kmalloc_track_caller() so that we can figure out who called 
them.

       reply	other threads:[~2007-07-07 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <468FBA20.8060509@googlemail.com>
     [not found] ` <1183825391.3066.59.camel@shinybook.infradead.org>
     [not found]   ` <6bffcb0e0707070959m12ba9b66n8587605eb1f6c21e@mail.gmail.com>
2007-07-07 23:07     ` Christoph Lameter [this message]
2007-07-07 23:38       ` 2.6.22-rc7: known regressions with patches v2 Linus Torvalds

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=Pine.LNX.4.64.0707071557160.16503@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bunk@stusta.de \
    --cc=dtor@insightbb.com \
    --cc=dwmw2@infradead.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=pcaulfie@redhat.com \
    --cc=teigland@redhat.com \
    --cc=torvalds@linux-foundation.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