diff options
author | 2012-12-04 15:59:55 +0000 | |
---|---|---|
committer | 2013-01-07 14:22:37 -0800 | |
commit | 7d3135af399e92cf4c9bbc5f86b6c140aab3b88c (patch) | |
tree | f0f08ba341a42d521ca4149df60eb4bc5d2acc27 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | staging: comedi: fix minimum AO period for NI 625x and NI 628x (diff) | |
download | linux-dev-7d3135af399e92cf4c9bbc5f86b6c140aab3b88c.tar.xz linux-dev-7d3135af399e92cf4c9bbc5f86b6c140aab3b88c.zip |
staging: comedi: prevent auto-unconfig of manually configured devices
When a low-level comedi driver auto-configures a device, a `struct
comedi_dev_file_info` is allocated (as well as a `struct
comedi_device`) by `comedi_alloc_board_minor()`. A pointer to the
hardware `struct device` is stored as a cookie in the `struct
comedi_dev_file_info`. When the low-level comedi driver
auto-unconfigures the device, `comedi_auto_unconfig()` uses the cookie
to find the `struct comedi_dev_file_info` so it can detach the comedi
device from the driver, clean it up and free it.
A problem arises if the user manually unconfigures and reconfigures the
comedi device using the `COMEDI_DEVCONFIG` ioctl so that is no longer
associated with the original hardware device. The problem is that the
cookie is not cleared, so that a call to `comedi_auto_unconfig()` from
the low-level driver will still find it, detach it, clean it up and free
it.
Stop this problem occurring by always clearing the `hardware_device`
cookie in the `struct comedi_dev_file_info` whenever the
`COMEDI_DEVCONFIG` ioctl call is successful.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions