All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Thompson <norsk5@yahoo.com>
To: Arthur Jones <ajones@riverbed.com>, Greg KH <greg@kroah.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Doug Thompson <norsk5@yahoo.com>,
	"bluesmoke-devel@lists.sourceforge.net" 
	<bluesmoke-devel@lists.sourceforge.net>
Subject: Re: on static kobjects and double frees...
Date: Tue, 10 Jun 2008 14:14:30 -0700 (PDT)	[thread overview]
Message-ID: <879085.21951.qm@web50106.mail.re2.yahoo.com> (raw)
In-Reply-To: <20080610163800.GA28572@ajones-laptop.nbttech.com>


--- Arthur Jones <ajones@riverbed.com> wrote:

> Hi Greg, ...
> 
> On Tue, Jun 10, 2008 at 09:23:41AM -0700, Greg KH wrote:
> > On Tue, Jun 10, 2008 at 08:58:50AM -0700, Arthur Jones wrote:
> > > Hi Greg,  The edac pci sysfs generic layer uses a static
> > > kobject as a placeholder parent where edac pci drivers
> > > are inserted.
> > 
> > Hm, stop right there.
> > 
> > kobjects are not supposed to be static, bad things happen if you do that
> > (including the kernel itself will warn you about them, unless you gave
> > it an empty release function, and if so, then see
> > Documentation/kobject.txt and prepare to be mocked...)

The edac_pci was my first coding with kobjects sometime ago and I have not reviewed them for quite
awhile, since I have been working more on memory controllers. Thus it was my bad.

Arthur, thanks for tracking that down and reviewing it. All the memory controller kobjects are all
dynamic. The edac PCI code needed to be refactored and it looks like you did it.

thanks again

doug t


For the patch:

Acked-by:    doug thompson <dougthompson@xmission.com>




W1DUG

  parent reply	other threads:[~2008-06-10 21:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 15:58 on static kobjects and double frees Arthur Jones
2008-06-10 16:23 ` Greg KH
2008-06-10 16:38   ` Arthur Jones
2008-06-10 16:42     ` Greg KH
2008-06-10 16:58       ` Arthur Jones
2008-06-10 21:14     ` Doug Thompson [this message]
2008-06-10 21:39       ` Arthur Jones

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=879085.21951.qm@web50106.mail.re2.yahoo.com \
    --to=norsk5@yahoo.com \
    --cc=ajones@riverbed.com \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=greg@kroah.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.