[dev][usb-function] Fix test case where device is released.

If we close the cachecontrol_ device handle during the disconnect
in the ums-test, this will trigger the release function of the
ums-function device.

In ums-function bind, it looks like the writeback_cache_ check
will never be true, since we just set it to false at the start of bind.
This means we are always using the static vmo for ums->storage.

In ums-function release, we check for whether writeback_cache_ is true,
to figure out if we should release the child vmo. However, this is
actually releasing the static vmo, as we never made the copy in bind.

Next time ums-function binds again, vmar_map will fail since the static
vmo has been released.

TEST= runtests -t usb-virtual-bus-ums-test
Updated test fails before ums-function changes, passes with changes.

Change-Id: I32939cface3887c9c897a608331e1823b502db9d
2 files changed
tree: c25203af23bbf897239f9b7e6c93019c5be59342
  1. boards/
  2. build/
  3. bundles/
  4. docs/
  5. examples/
  6. garnet/
  7. peridot/
  8. products/
  9. scripts/
  10. sdk/
  11. src/
  12. third_party/
  13. tools/
  14. zircon/
  15. .clang-format
  16. .clang-tidy
  17. .dir-locals.el
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .style.yapf
  22. AUTHORS
  23. BUILD.gn
  24. CODE_OF_CONDUCT.md
  25. CONTRIBUTING.md
  26. LICENSE
  27. OWNERS
  28. PATENTS
  29. README.md
  30. rustfmt.toml
README.md

Fuchsia

Pink + Purple == Fuchsia (a new operating system)

What is Fuchsia?

Fuchsia is a modular, capability-based operating system. Fuchsia runs on modern 64-bit Intel and ARM processors.

Fuchsia is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.