diff options
| author | Florian Schmaus <[email protected]> | 2018-05-23 15:59:11 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2018-05-25 16:18:45 +0000 |
| commit | 0dda2bb6242361afd68332bf19bd67cd5981eb26 (patch) | |
| tree | a1f9063eefed025fae2d04257877d4439523bec4 /fs/proc/array.c | |
| parent | driver core: add __printf verification to device_create_groups_vargs (diff) | |
| download | kernel-0dda2bb6242361afd68332bf19bd67cd5981eb26.tar.gz kernel-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 <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'fs/proc/array.c')
0 files changed, 0 insertions, 0 deletions