diff options
author | Mika Westerberg <mika.westerberg@linux.intel.com> | 2018-09-24 13:20:44 +0300 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-10-02 10:51:16 -0700 |
commit | 86da809dda64a63fc27e05a215475325c3aaae92 (patch) | |
tree | 319f800e3890bd076292ad97cc3a212d9a934db4 /Documentation/nvdimm | |
parent | 7012040576c6ae25a47035659ee48673612c2c27 (diff) | |
download | linux-stable-86da809dda64a63fc27e05a215475325c3aaae92.tar.gz linux-stable-86da809dda64a63fc27e05a215475325c3aaae92.tar.bz2 linux-stable-86da809dda64a63fc27e05a215475325c3aaae92.zip |
thunderbolt: Do not handle ICM events after domain is stopped
If there is a long chain of devices connected when the driver is loaded
ICM sends device connected event for each and those are put to tb->wq
for later processing. Now if the driver gets unloaded in the middle, so
that the work queue is not yet empty it gets flushed by tb_domain_stop().
However, by that time the root switch is already removed so the driver
crashes when it tries to dereference it in ICM event handling callbacks.
Fix this by checking whether the root switch is already removed. If it
is we know that the domain is stopped and we should merely skip handling
the event.
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/nvdimm')
0 files changed, 0 insertions, 0 deletions