Re: [PATCH v2] driver-core: Return EBUSY error instead of BUG_ON()

2018-05-04 Thread Greg Kroah-Hartman
On Fri, May 04, 2018 at 03:23:57PM +0200, Florian Schmaus wrote: > I triggerd the BUG_ON() in driver_register(), which was added in > f48f3febb2cbfd0f2ecee7690835ba745c1034a4, when booting a domU Xen > domain. Since there was no contextual information logged, I needed to > attach kgdb to determine

Re: [PATCH v2] driver-core: Return EBUSY error instead of BUG_ON()

2018-05-04 Thread Greg Kroah-Hartman
On Fri, May 04, 2018 at 03:23:57PM +0200, Florian Schmaus wrote: > I triggerd the BUG_ON() in driver_register(), which was added in > f48f3febb2cbfd0f2ecee7690835ba745c1034a4, when booting a domU Xen > domain. Since there was no contextual information logged, I needed to > attach kgdb to determine

Re: [PATCH v2] driver-core: Return EBUSY error instead of BUG_ON()

2018-05-04 Thread Greg Kroah-Hartman
On Fri, May 04, 2018 at 03:23:57PM +0200, Florian Schmaus wrote: > I triggerd the BUG_ON() in driver_register(), which was added in > f48f3febb2cbfd0f2ecee7690835ba745c1034a4, when booting a domU Xen > domain. Since there was no contextual information logged, I needed to > attach kgdb to determine

Re: [PATCH v2] driver-core: Return EBUSY error instead of BUG_ON()

2018-05-04 Thread Greg Kroah-Hartman
On Fri, May 04, 2018 at 03:23:57PM +0200, Florian Schmaus wrote: > I triggerd the BUG_ON() in driver_register(), which was added in > f48f3febb2cbfd0f2ecee7690835ba745c1034a4, when booting a domU Xen > domain. Since there was no contextual information logged, I needed to > attach kgdb to determine