From: Greg KH <greg@kroah.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: subsystem_unregister() breakage in -mm
Date: Tue, 25 Sep 2007 17:36:52 -0700 [thread overview]
Message-ID: <20070926003652.GA26781@kroah.com> (raw)
In-Reply-To: <E1IaJQL-00053O-00@dorka.pomaz.szeredi.hu>
On Wed, Sep 26, 2007 at 01:02:37AM +0200, Miklos Szeredi wrote:
> > On Wed, Sep 26, 2007 at 12:27:14AM +0200, Miklos Szeredi wrote:
> > > I get "BUG: failure at mm/slab.c:591/page_get_cache()!" in latest -mm
> > > when removing the fuse module.
> > >
> > > This patch titled "kobject: remove the static array for the name"
> > > looks like it's responsible. Reverting it cures the problem.
> > >
> > > The root of the problem seems to be, that decl_subsys() initializes
> > > k_name with a string constant. Then subsystem_unregister() will put
> > > the kobject, which will free the k_name.
> > >
> > > So, what's the right way to deal with this?
> >
> > How is the static kobject created by decl_subsys() getting it's release
> > function called when it is never really "released" as it is a static
> > kobject?
>
> Don't know.
>
> This is the stack trace I get:
>
> BUG: failure at mm/slab.c:591/page_get_cache()!
> Kernel panic - not syncing: BUG!
>
> EIP: 0023:[<400e7f84>] CPU: 0 Not tainted ESP: 002b:bf77e018 EFLAGS: 00000246
> Not tainted
> EAX: ffffffda EBX: bf77e040 ECX: 00000880 EDX: bf780884
> ESI: 00000003 EDI: bf77e040 EBP: bf7808d8 DS: 002b ES: 002b
> 08eefd2c: [<0806ec8c>] show_regs+0x104/0x106
> 08eefd48: [<0805b96a>] panic_exit+0x2c/0x4b
> 08eefd58: [<0808fcab>] notifier_call_chain+0x36/0x61
> 08eefd78: [<0808fd83>] __atomic_notifier_call_chain+0x30/0x32
> 08eefd94: [<0808fdb4>] atomic_notifier_call_chain+0x2f/0x31
> 08eefdb0: [<08075cf0>] panic+0x75/0x126
> 08eefdd4: [<080bc3f5>] kfree+0xb1/0xc6
> 08eefdf8: [<08137de9>] kobject_cleanup+0x37/0x6a
> 08eefe10: [<08137e30>] kobject_release+0x14/0x16
> 08eefe1c: [<08138711>] kref_put+0x30/0xaf
> 08eefe3c: [<08137e52>] kobject_put+0x20/0x22
> 08eefe4c: [<08137d8b>] kobject_unregister+0x2e/0x34
Hm, this make sense from an object lifecycle type of thing, and it makes
sense why it is dying. I think I know how to fix it up, give me a few
hours (dinner time here...)
thanks,
greg k-h
next prev parent reply other threads:[~2007-09-26 0:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 22:27 subsystem_unregister() breakage in -mm Miklos Szeredi
2007-09-25 22:53 ` Greg KH
2007-09-25 23:02 ` Miklos Szeredi
2007-09-26 0:36 ` Greg KH [this message]
2007-09-26 2:41 ` Greg KH
2007-09-26 7:21 ` Cornelia Huck
2007-09-26 15:14 ` Greg KH
2007-09-26 8:17 ` Miklos Szeredi
2007-09-26 15:15 ` Greg KH
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=20070926003652.GA26781@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.