mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Pierre-Yves Paulus <py@idlum.be>
Cc: linux-kernel@vger.kernel.org, Chuck Ebbert <cebbert@redhat.com>,
	BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: Warnings and Oops on 2.6.23-rc6 while activily using rfcomm links (mm/slab.c)
Date: Fri, 28 Sep 2007 08:54:38 +0200	[thread overview]
Message-ID: <20070928085438.4eb5a38f@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <46FBF17A.6030009@idlum.be>

On Thu, 27 Sep 2007 20:07:54 +0200,
Pierre-Yves Paulus <py@idlum.be> wrote:

> Another one below, complete log from power-up to reboot, with some bugs 
> and one Oops. I only trimmed the numerous "l2cap_recv_acldata" and "ACL 
> packet for unknown connection handle" lines which always fill up the log.

Hmm, looked at it, but currently I can't see what's wrong from a driver
core perspective...


> =============================================================================
> BUG kmalloc-128: Poison overwritten
> -----------------------------------------------------------------------------
> 
> INFO: 0xc5734f28-0xc5734f40. First byte 0x6a instead of 0x6b
> INFO: Allocated in rfcomm_dev_ioctl+0xbd/0x4e6 [rfcomm] age=6110 cpu=0 
> pid=3677
> INFO: Freed in rfcomm_dev_destruct+0x59/0x65 [rfcomm] age=3157 cpu=0 
> pid=3927
> INFO: Slab 0xc10ae680 used=21 fp=0xc5734f20 flags=0x400000c2
> INFO: Object 0xc5734f20 @offset=3872 fp=0xc57342c0
> 
> Bytes b4 0xc5734f10:  05 00 00 00 f8 23 0f 00 5a 5a 5a 5a 5a 5a 5a 5a 
> ....ø#..ZZZZZZZZ
>    Object 0xc5734f20:  6b 6b 6b 6b 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b 
                                                 ^^

This looks suspiciously like someone tried to decrease a refcount on a
freed kobject. Unfortunately, we only see this after the fact with slub
debugging turned on :( So could you please turn it off again (but leave
kobject debugging on) and try with the following silly debug patch:

---
 lib/kobject.c |    6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

--- linux-2.6.orig/lib/kobject.c
+++ linux-2.6/lib/kobject.c
@@ -502,8 +502,12 @@ static void kobject_release(struct kref 
  */
 void kobject_put(struct kobject * kobj)
 {
-	if (kobj)
+	if (kobj) {
+		if (!atomic_read(&kobj->kref.refcount))
+			pr_debug("%s: kobject %s@%p already has zero refcount!\n",
+				 __FUNCTION__, kobj->name, kobj);
 		kref_put(&kobj->kref, kobject_release);
+	}
 }
 
 

  reply	other threads:[~2007-09-28  6:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25 15:04 Pierre-Yves Paulus
2007-09-25 15:32 ` Cornelia Huck
2007-09-25 18:26 ` Chuck Ebbert
2007-09-26 13:27   ` Pierre-Yves Paulus
2007-09-27  6:56     ` Cornelia Huck
2007-09-27 14:43       ` Pierre-Yves Paulus
2007-09-27 18:07         ` Pierre-Yves Paulus
2007-09-28  6:54           ` Cornelia Huck [this message]
2007-09-28 14:38             ` Pierre-Yves Paulus
2007-09-28 14:57               ` Pierre-Yves Paulus
2007-09-28 16:32                 ` Pierre-Yves Paulus
2007-10-01 12:32                   ` Cornelia Huck
2007-11-06  2:46                     ` Dave Young
2007-09-26 22:16 ` [Bluez-devel] " Marcel Holtmann

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=20070928085438.4eb5a38f@gondolin.boeblingen.de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=py@idlum.be \
    /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

all inboxes | Powered by JetHome®