If a driver's probe function returns -ENXIO or -ENODEV, driver_probe_device() will translate that to return 0 (comments argue it is not an error). Consequently driver_bind() will return 0 resulting in the write system-call that initiated all of this in returning 0 as well. If one uses "echo" to write to a "bind" attribute, echo will continuously call write() trying to write to the attribute and always get 0 as a result and thus find itself in a loop trying to do the write. Perhaps the translation of -ENZIO to -ENODEV to success in driver_probe_device() is not approriate here? -- Michal Ostrowski
Attachment:
pgpMccHKKNLD1.pgp
Description: PGP signature
- Prev by Date: Re: Debugging kernel semaphore contention and priority inversion
- Next by Date: Re: Schedulers benchmark - Was: [ANNOUNCE][RFC] PlugSched-5.2.4 for 2.6.12 and 2.6.13-rc6
- Previous by thread: Debugging kernel semaphore contention and priority inversion
- Next by thread: [PATCH 1/7] rename locking functions - do the rename
- Index(es):
