All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Rose <johnrose@austin.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: greg KH <gregkh@us.ibm.com>
Subject: Re: [Bug 2013] New: Oops from create_dir (sysfs)
Date: Wed, 04 Feb 2004 14:27:22 -0600	[thread overview]
Message-ID: <1075926442.3026.37.camel@verve> (raw)

In the last couple of weeks, I've come across this crash a few times. 
In each case, my code was kobject_add()'ing a kobject to a kset that
already contained a kobject of the same name.

Granted that these additions reflected faulty logic on the part of my
code, but I was suprised that kobject_add didn't have a more intelligent
response than crashing while creating the redundant sysfs dir.

Thoughts?
John

http://bugme.osdl.org/show_bug.cgi?id=2013
-- 
John Rose <johnrose@austin.ibm.com>


             reply	other threads:[~2004-02-04 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04 20:27 John Rose [this message]
2004-02-04 20:48 ` [Bug 2013] New: Oops from create_dir (sysfs) Greg KH
2004-02-04 20:54   ` John Rose
2004-02-04 21:22     ` Greg KH
2004-02-04 21:43       ` John Rose
2004-02-04 22:00         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2004-02-04 18:55 Martin J. Bligh

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=1075926442.3026.37.camel@verve \
    --to=johnrose@austin.ibm.com \
    --cc=gregkh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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 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.