Viresh Kumar 928f2abd5f greybus: Tear down devices in the reverse order ...

Normally, its a good practice to free resources in the reverse order in
which they are allocated, so that all the dependencies can be sorted out
properly.

This is true while creating/destroying devices as well. For example
consider this scenario (I faced a crash with control protocol due to
this). For a new module, we will first create a bundle+connection for
the control cport and then create other bundles/connections after
parsing manifest.

And while destroying interface on module hot unplug, we are removing the
devices in the order they are added. And so the bundle/connection for
the control cport are destroyed first. But, control cport was still
required while destroying other bundles/connections.

To solve this problem, lets destroy the resources in the reverse order
in which they are added.

Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Alex Elder <elder@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>

2015-06-09 13:31:23 -07:00

drivers/staging/greybus

greybus: Tear down devices in the reverse order

2015-06-09 13:31:23 -07:00

S

Description

No description provided

5.7 GiB

Languages

C 96.9%

Assembly 0.9%

Rust 0.6%

Shell 0.6%

Python 0.5%

Other 0.3%