From: Vasiliy Kulikov <segoon@openwall.com>
To: Greg KH <gregkh@suse.de>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: base: core: do not put noninitialized devices
Date: Fri, 19 Nov 2010 19:17:05 +0000 [thread overview]
Message-ID: <20101119191705.GA12558@albatros> (raw)
In-Reply-To: <20101119191424.GA12273@albatros>
On Fri, Nov 19, 2010 at 22:14 +0300, Vasiliy Kulikov wrote:
> No, I've just analized the code. Without device_initialize() ->kobj is
> not initialized:
I mean 'not set' instead of 'not initialized' - it is already kzalloc()'ed :)
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
WARNING: multiple messages have this Message-ID (diff)
From: Vasiliy Kulikov <segoon@openwall.com>
To: Greg KH <gregkh@suse.de>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: base: core: do not put noninitialized devices
Date: Fri, 19 Nov 2010 22:17:05 +0300 [thread overview]
Message-ID: <20101119191705.GA12558@albatros> (raw)
In-Reply-To: <20101119191424.GA12273@albatros>
On Fri, Nov 19, 2010 at 22:14 +0300, Vasiliy Kulikov wrote:
> No, I've just analized the code. Without device_initialize() ->kobj is
> not initialized:
I mean 'not set' instead of 'not initialized' - it is already kzalloc()'ed :)
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
next prev parent reply other threads:[~2010-11-19 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 18:41 [PATCH] drivers: base: core: do not put noninitialized devices Vasiliy Kulikov
2010-11-19 18:41 ` Vasiliy Kulikov
2010-11-19 19:02 ` Greg KH
2010-11-19 19:02 ` Greg KH
2010-11-19 19:14 ` Vasiliy Kulikov
2010-11-19 19:14 ` Vasiliy Kulikov
2010-11-19 19:17 ` Vasiliy Kulikov [this message]
2010-11-19 19:17 ` Vasiliy Kulikov
2010-11-19 20:57 ` Greg KH
2010-11-19 20:57 ` Greg KH
2010-11-20 9:00 ` Vasiliy Kulikov
2010-11-20 9:00 ` Vasiliy Kulikov
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=20101119191705.GA12558@albatros \
--to=segoon@openwall.com \
--cc=gregkh@suse.de \
--cc=kernel-janitors@vger.kernel.org \
--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.