linux-stable.git/drivers/base/bus.c, branch linux-3.8.y

Driver core: treat unregistered bus_types as having no devices

2013-02-28T13:38:31+00:00

commit 4fa3e78be7e985ca814ce2aa0c09cbee404efcf7 upstream.

A bus_type has a list of devices (klist_devices), but the list and the
subsys_private structure that contains it are not initialized until the
bus_type is registered with bus_register().

The panic/reboot path has fixups that look up devices in pci_bus_type.  If
we panic before registering pci_bus_type, the bus_type exists but the list
does not, so mach_reboot_fixups() trips over a null pointer and panics
again:

    mach_reboot_fixups
      pci_get_device
        ..
          bus_find_device(&pci_bus_type, ...)
            bus->p is NULL

Joonsoo reported a problem when panicking before PCI was initialized.
I think this patch should be sufficient to replace the patch he posted
here: https://lkml.org/lkml/2012/12/28/75 ("[PATCH] x86, reboot: skip
reboot_fixups in early boot phase")

Reported-by: Joonsoo Kim 
Signed-off-by: Bjorn Helgaas 
Signed-off-by: Greg Kroah-Hartman

driver core: remove CONFIG_HOTPLUG ifdefs

2012-11-28T18:33:03+00:00

Remove conditional code based on CONFIG_HOTPLUG being false.  It's
always on now in preparation of it going away as an option.

Signed-off-by: Bill Pemberton 
Signed-off-by: Greg Kroah-Hartman

driver core: move uevent call to driver_register

2012-07-17T01:04:25+00:00

Device driver attribute groups are created after userspace is notified
via an add event. Fix this by moving the kobject_uevent call to
driver_register after the attribute groups are added.

Signed-off-by: Sebastian Ott 
Signed-off-by: Greg Kroah-Hartman

Revert "driver core: check start node in klist_iter_init_node"

2012-04-20T02:17:30+00:00

This reverts commit a15d49fd3094cff90e5410ca454a870e0a722fe1 as that
patch broke the build.

Cc: Hannes Reinecke 
Reported-by: Stephen Rothwell 
Signed-off-by: Greg Kroah-Hartman

driver core: check start node in klist_iter_init_node

2012-04-18T22:39:52+00:00

klist_iter_init_node() takes a node as a start argument.
However, this node might not be valid anymore.
This patch updates the klist_iter_init_node() and
dependent functions to return an error if so.
All calling functions have been audited to check
for a return code here.

Signed-off-by: Hannes Reinecke 
Cc: Greg Kroah-Hartmann 
Cc: Kay Sievers 
Cc: Stable Kernel 
Cc: Linux Kernel 
Signed-off-by: Greg Kroah-Hartman

drivers/base/bus.c: local variables should not be exposed globally

2012-04-18T22:39:52+00:00

The variable 'system_kset' is only referenced in this file and
should be marked static to prevent it from being exposed globally.

This quiets the sparse waring:

warning: symbol 'system_kset' was not declared. Should it be static?

Also, remove the comment since drivers/base/sys.c has now been
deleted.

Signed-off-by: H Hartley Sweeten 
Cc: Greg Kroah-Hartman 
Signed-off-by: Greg Kroah-Hartman

Merge 3.3-rc2 into the driver-core-next branch.

2012-02-02T19:24:44+00:00

This was done to resolve a merge and build problem with the
drivers/acpi/processor_driver.c file.

Reported-by: Stephen Rothwell 
Signed-off-by: Greg Kroah-Hartman

driver-core: Fix possible null reference in subsys_interface_unregister

2012-01-24T23:59:19+00:00

Check if the sif is not NULL before de-referencing it

Signed-off-by: Jonghwan Choi 
Signed-off-by: Greg Kroah-Hartman

kernel-doc: fix new warnings in driver-core

2012-01-23T16:44:53+00:00

Fix new kernel-doc warnings:

Warning(drivers/base/bus.c:925): No description found for parameter 'key'
Warning(drivers/base/bus.c:1241): No description found for parameter 'subsys'
Warning(drivers/base/bus.c:1241): No description found for parameter 'groups'

Signed-off-by: Randy Dunlap 
Cc: Greg Kroah-Hartman 
Signed-off-by: Linus Torvalds

driver-core: implement 'sysdev' functionality for regular devices and buses

2011-12-14T22:29:38+00:00

All sysdev classes and sysdev devices will converted to regular devices
and buses to properly hook userspace into the event processing.

There is no interesting difference between a 'sysdev' and 'device' which
would justify to roll an entire own subsystem with different userspace
export semantics. Userspace relies on events and generic sysfs subsystem
infrastructure from sysdev devices, which are currently not properly
available.

Every converted sysdev class will create a regular device with the class
name in /sys/devices/system and all registered devices will becom a children
of theses devices.

For compatibility reasons, the sysdev class-wide attributes are created
at this parent device. (Do not copy that logic for anything new, subsystem-
wide properties belong to the subsystem, not to some fake parent device
created in /sys/devices.)

Every sysdev driver is implemented as a simple subsystem interface now,
and no longer called a driver.

After all sysdev classes are ported to regular driver core entities, the
sysdev implementation will be entirely removed from the kernel.

Signed-off-by: Kay Sievers 
Signed-off-by: Greg Kroah-Hartman