From: Greg KH <gregkh@suse.de>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [broken-out-2007-07-20-00-22] kernel bug at kernel/params:570
Date: Fri, 20 Jul 2007 15:50:47 -0700 [thread overview]
Message-ID: <20070720225047.GA17520@suse.de> (raw)
In-Reply-To: <6bffcb0e0707200932p2b905e21g7970172ca7eb4da7@mail.gmail.com>
On Fri, Jul 20, 2007 at 06:32:21PM +0200, Michal Piotrowski wrote:
> Hi Greg,
>
> This looks like a sysfs bug
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/broken-out-2007-07-20-00-22/00003.jpg
>
> l *kernel_param_sysfs_setup+0x75
> 0xc13c0894 is in kernel_param_sysfs_setup (kernel/params.c:570).
> 565 mk->mod = THIS_MODULE;
> 566 kobj_set_kset_s(mk, module_subsys);
> 567 kobject_set_name(&mk->kobj, name);
> 568 kobject_init(&mk->kobj);
> 569 ret = kobject_add(&mk->kobj);
> 570 BUG_ON(ret < 0);
> 571 param_sysfs_setup(mk, kparam, num_params, name_skip);
> 572 kobject_uevent(&mk->kobj, KOBJ_ADD);
> 573 }
> 574
>
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/broken-out-2007-07-20-00-22/mm-config
What kernel version is this happening on? The -mm tree? Can you try
Linus's tree instead?
It looks like there was some needed information right before the first
stack dump, showing exactly what kobject was trying to be added that was
already present. Odds are this is a kernel parameter with the same name
as a duplicate one within the same module, but the trick is going to be
trying to figure out what module is causing this.
So it's not a sysfs bug, but rather a driver issue that this is
catching.
Does that make sense?
greg k-h
next prev parent reply other threads:[~2007-07-20 22:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 16:32 [broken-out-2007-07-20-00-22] kernel bug at kernel/params:570 Michal Piotrowski
2007-07-20 22:50 ` Greg KH [this message]
2007-07-20 22:59 ` Andrew Morton
2007-07-20 23:10 ` Greg KH
2007-07-20 23:37 ` Randy Dunlap
2007-07-20 23:43 ` Satyam Sharma
2007-07-21 0:03 ` Satyam Sharma
2007-07-21 0:28 ` Michal Piotrowski
2007-07-21 1:02 ` Greg KH
2007-07-21 1:37 ` Andrew Morton
2007-07-21 1:44 ` Greg KH
2007-07-21 3:21 ` Satyam Sharma
2007-07-21 3:57 ` Satyam Sharma
2007-07-21 6:00 ` Satyam Sharma
2007-07-21 6:39 ` [BUG] " Satyam Sharma
2007-07-21 8:11 ` Michal Piotrowski
2007-07-21 8:00 ` Michal Piotrowski
2007-07-21 8:36 ` Satyam Sharma
2007-07-21 8:41 ` Michal Piotrowski
2007-07-21 16:00 ` Michal Piotrowski
2007-07-21 16:41 ` Andi Kleen
2007-07-21 16:52 ` Michal Piotrowski
2007-07-21 16:55 ` Michal Piotrowski
2007-07-21 18:11 ` Michal Piotrowski
2007-07-21 18:24 ` Andi Kleen
2007-07-22 17:51 ` Satyam Sharma
2007-07-21 19:13 ` Andrew Morton
2007-07-21 19:31 ` Michal Piotrowski
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=20070720225047.GA17520@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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