commit | 7deb450472da108745ef1f6f60c09aeb7e49496f | [log] [tgz] |
---|---|---|
author | Jocelyn Dang <jocelyndang@google.com> | Fri Aug 16 23:41:26 2019 +0000 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Aug 16 23:41:26 2019 +0000 |
tree | c25203af23bbf897239f9b7e6c93019c5be59342 | |
parent | 81675dc42f77afa894455b1d426e3520ec3e1b85 [diff] |
[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
Pink + Purple == Fuchsia (a new operating system)
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.
See Getting Started.
See fuchsia.dev.