public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: kvm-devel@lists.sourceforge.net,
	Balaji Rao <balajirrao@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Mark kobjects as unitialized
Date: Mon, 10 Mar 2008 10:20:02 -0700	[thread overview]
Message-ID: <20080310172002.GA28146@suse.de> (raw)
In-Reply-To: <18387.49334.235230.751065@harpo.it.uu.se>

On Sun, Mar 09, 2008 at 11:49:26AM +0100, Mikael Pettersson wrote:
> Balaji Rao writes:
>  > Yes the idea works. One more memset is needed in sysdev_register. Here's the final patch.
>  > 
>  > diff --git a/drivers/base/sys.c b/drivers/base/sys.c
>  > index 2f79c55..7c839d9 100644
>  > --- a/drivers/base/sys.c
>  > +++ b/drivers/base/sys.c
>  > @@ -133,6 +133,7 @@ int sysdev_class_register(struct sysdev_class * cls)
>  >         pr_debug("Registering sysdev class '%s'\n",
>  >                  kobject_name(&cls->kset.kobj));
>  >         INIT_LIST_HEAD(&cls->drivers);
>  > +       memset(&cls->kset.kobj, 0x00, sizeof(struct kobject));
>  >         cls->kset.kobj.parent = &system_kset->kobj;
>  >         cls->kset.kobj.ktype = &ktype_sysdev_class;
>  >         cls->kset.kobj.kset = system_kset;
>  > @@ -227,6 +228,7 @@ int sysdev_register(struct sys_device * sysdev)
>  >  
>  >         pr_debug("Registering sys device '%s'\n", kobject_name(&sysdev->kobj));
>  >  
>  > +       memset(&sysdev->kobj, 0x00, sizeof(struct kobject));
>  >         /* Make sure the kset is set */
>  >         sysdev->kobj.kset = &cls->kset;
>  > 
> 
> Thanks, 2.6.25-rc4 + these two memset()s is finally stable for
> me with no warnings, BUG()s, or panics.
> 
> (However, the patch is whitespace damaged with initial tabs
> converted to spaces.)
> 
> If you want to pass this on to Linus, you can add a
> 
> Tested-by: Mikael Pettersson <mikpe@it.uu.se>

Thanks for testing.

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-10 17:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 16:53 [PATCH] Mark kobjects as unitialized Balaji Rao
2008-03-06 17:05 ` Greg KH
2008-03-06 17:50   ` Balaji Rao
2008-03-06 18:05     ` Greg KH
2008-03-07  8:56       ` Avi Kivity
2008-03-08 22:07       ` Balaji Rao
2008-03-09  5:06         ` Greg KH
2008-03-09  6:16           ` Greg KH
2008-03-09  6:17           ` Balaji Rao
2008-03-09  6:33         ` Greg KH
2008-03-09  6:36           ` Balaji Rao
2008-03-09  7:03             ` Greg KH
2008-03-09  7:21               ` Balaji Rao
2008-03-09 10:49                 ` Mikael Pettersson
2008-03-10 17:20                   ` Greg KH [this message]
2008-03-10 15:52                 ` Greg KH
2008-03-10 16:05                   ` Balaji Rao
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=20080310172002.GA28146@suse.de \
    --to=gregkh@suse.de \
    --cc=balajirrao@gmail.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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