All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Balaji Rao <balajirrao@gmail.com>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Mark kobjects as unitialized
Date: Thu, 6 Mar 2008 10:05:59 -0800	[thread overview]
Message-ID: <20080306180559.GA14934@suse.de> (raw)
In-Reply-To: <200803062320.50296.balajirrao@gmail.com>

On Thu, Mar 06, 2008 at 11:20:50PM +0530, Balaji Rao wrote:
> On Thursday 06 March 2008 10:35:14 pm Greg KH wrote:
> <snip>
> > Where exactly in the code does that happen?  kobjects should not be
> > "reused" as that implies that they are static, and not dynamically
> > allocated, right?
> >
> > Which kobject is this?
> Yes, its static. Here's the code from virt/kvm_main.c:1269
> 
> static struct sys_device kvm_sysdev = {
>         .id = 0,
>         .cls = &kvm_sysdev_class,
> };
> 
> this sys_device is being registered/unregistered when kvm-intel is 
> loaded/unloaded.

Ah, ok.  I'll add this patch then.

> > Ugh, is this the sys_device stuff?  I hate that code...
> >
> Yes it is! But, why do you hate it ?

For reasons like this :)

kobjects should not be static.  the sysdevice stuff was a hack when it
was originally created and never touched since the mid 2.5 days.  It
needs to be fixed up a lot, and is on my TODO list, slowly getting
closer to the top...

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: Balaji Rao <balajirrao@gmail.com>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Mark kobjects as unitialized
Date: Thu, 6 Mar 2008 10:05:59 -0800	[thread overview]
Message-ID: <20080306180559.GA14934@suse.de> (raw)
In-Reply-To: <200803062320.50296.balajirrao@gmail.com>

On Thu, Mar 06, 2008 at 11:20:50PM +0530, Balaji Rao wrote:
> On Thursday 06 March 2008 10:35:14 pm Greg KH wrote:
> <snip>
> > Where exactly in the code does that happen?  kobjects should not be
> > "reused" as that implies that they are static, and not dynamically
> > allocated, right?
> >
> > Which kobject is this?
> Yes, its static. Here's the code from virt/kvm_main.c:1269
> 
> static struct sys_device kvm_sysdev = {
>         .id = 0,
>         .cls = &kvm_sysdev_class,
> };
> 
> this sys_device is being registered/unregistered when kvm-intel is 
> loaded/unloaded.

Ah, ok.  I'll add this patch then.

> > Ugh, is this the sys_device stuff?  I hate that code...
> >
> Yes it is! But, why do you hate it ?

For reasons like this :)

kobjects should not be static.  the sysdevice stuff was a hack when it
was originally created and never touched since the mid 2.5 days.  It
needs to be fixed up a lot, and is on my TODO list, slowly getting
closer to the top...

thanks,

greg k-h

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-03-06 18:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 16:53 [PATCH] Mark kobjects as unitialized Balaji Rao
2008-03-06 16:53 ` Balaji Rao
2008-03-06 17:05 ` Greg KH
2008-03-06 17:05   ` Greg KH
2008-03-06 17:50   ` Balaji Rao
2008-03-06 17:50     ` Balaji Rao
2008-03-06 18:05     ` Greg KH [this message]
2008-03-06 18:05       ` Greg KH
2008-03-07  8:56       ` [kvm-devel] " Avi Kivity
2008-03-07  8:56         ` Avi Kivity
2008-03-08 22:07       ` Balaji Rao
2008-03-09  5:06         ` Greg KH
2008-03-09  5:06           ` Greg KH
2008-03-09  6:16           ` Greg KH
2008-03-09  6:16             ` Greg KH
2008-03-09  6:17           ` Balaji Rao
2008-03-09  6:17             ` Balaji Rao
2008-03-09  6:33         ` Greg KH
2008-03-09  6:33           ` Greg KH
2008-03-09  6:36           ` Balaji Rao
2008-03-09  6:36             ` Balaji Rao
2008-03-09  7:03             ` Greg KH
2008-03-09  7:03               ` Greg KH
2008-03-09  7:21               ` Balaji Rao
2008-03-09  7:21                 ` Balaji Rao
2008-03-09 10:49                 ` Mikael Pettersson
2008-03-09 10:49                   ` Mikael Pettersson
2008-03-10 17:20                   ` Greg KH
2008-03-10 17:20                     ` Greg KH
2008-03-10 15:52                 ` Greg KH
2008-03-10 15:52                   ` Greg KH
2008-03-10 16:05                   ` Balaji Rao
2008-03-10 16:05                     ` Balaji Rao
2008-03-10 17:20                     ` Greg KH
2008-03-10 17:20                       ` Greg KH
2008-03-06 18:34 ` patch kobjects-mark-cleaned-up-kobjects-as-unitialized.patch added to gregkh-2.6 tree gregkh
2008-03-09  4:58 ` patch patches/driver-core/kobjects-mark-cleaned-up-kobjects-as-unitialized.patch " gregkh

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=20080306180559.GA14934@suse.de \
    --to=gregkh@suse.de \
    --cc=balajirrao@gmail.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --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.