linux-kernel - Re: [PATCH 0/6] Add a per-dimm structure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120314233225.GA16564@kroah.com>
Date:	Wed, 14 Mar 2012 16:32:25 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Mauro Carvalho Chehab <mchehab@...hat.com>
Cc:	Linux Edac Mailing List <linux-edac@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/6] Add a per-dimm structure

On Wed, Mar 14, 2012 at 07:20:01PM -0300, Mauro Carvalho Chehab wrote:
> > Easy rule to remember, never mix "raw" kobjects and 'struct device',
> > which is what you would be doing here, right?  We can handle many
> > hundreds of thousands of files and devices in a single directory, no
> > problem.
> 
> No. They're all generated with raw kobjects, using kobject_init_and_add() or
> sysfs_create_file() calls.

Ick, no.

Please, never use "raw" kobjects.  Why doesn't 'struct device' work for
you properly here?  You just messed userspace all up in that it can not
properly account for the parts of sysfs here in the device tree.

Anything below /sys/devices/ should be using 'struct device' unless
there is a _very_ good reason not to.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/