From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752037AbaJEXY7 (ORCPT ); Sun, 5 Oct 2014 19:24:59 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:34736 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751752AbaJEXY6 (ORCPT ); Sun, 5 Oct 2014 19:24:58 -0400 Date: Sun, 5 Oct 2014 16:24:57 -0700 From: Greg KH To: Jason Noakes Cc: linux-kernel Subject: Re: kobject_init and the zeroed-out-memory requirement Message-ID: <20141005232457.GA22525@kroah.com> References: <20141005202843.GA1282@kroah.com> <20141005215100.GA20426@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Oct 05, 2014 at 06:13:05PM -0400, Jason Noakes wrote: > > No driver should be working with "raw" kobjects. > > I don't agree, but it's irrelevant. Not at all. I'd wager that if a driver is messing around with a "raw" kobject, it is doing something seriously wrong. Of course there are exceptions, but those are very rare, and exceptions. A driver should be using the driver core, and the functions and objects provided there, and provided by the bus it lives on. So, have a pointer to some driver code that is calling kobject_initialize()? I'd love to see it. thanks, greg k-h