summaryrefslogtreecommitdiffstats
path: root/drivers/base/bus.c
diff options
context:
space:
mode:
authorFlorian Schmaus <flo@geekplace.eu>2018-05-23 17:59:11 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-05-25 18:18:45 +0200
commit0dda2bb6242361afd68332bf19bd67cd5981eb26 (patch)
treea1f9063eefed025fae2d04257877d4439523bec4 /drivers/base/bus.c
parentdriver core: add __printf verification to device_create_groups_vargs (diff)
downloadlinux-0dda2bb6242361afd68332bf19bd67cd5981eb26.tar.xz
linux-0dda2bb6242361afd68332bf19bd67cd5981eb26.zip
driver-core: return EINVAL error instead of BUG_ON()
I triggerd the BUG_ON() in driver_register() when booting a domU Xen domain. Since there was no contextual information logged, I needed to attach kgdb to determine the culprit (the wmi-bmof driver in my case). The BUG_ON() was added in commit f48f3febb2cb ("driver-core: do not register a driver with bus_type not registered"). Instead of running into a BUG_ON() we print an error message identifying the, likely faulty, driver but continue booting. Signed-off-by: Florian Schmaus <flo@geekplace.eu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/base/bus.c')
0 files changed, 0 insertions, 0 deletions