GitLab

The cros-disks equivalent for MountType (MountSourceType) has a third
option (MOUNT_SOURCE_NETWORK_STORAGE) without a matching enumerator in
MountType; this value is now used for generic fuse mounts. VolumeManager
falls-through switches due to the unexpected value.

Add MOUNT_TYPE_NETWORK_SOURCE on the chrome side to avoid this problem.
Since this is currently a catch-all value for all generic fuse mount
types, VolumeManager isn't capable of handling their mounts reasonably.
Instead, ignore mount events with type MOUNT_TYPE_NETWORK_SOURCE in
VolumeManager; the mounters will handle their mount events individually.

Bug: 829274,832507
Change-Id: I18dc0b5b68120c94da2ebbe05ee863a6f471b81c
Reviewed-on: https://chromium-review.googlesource.com/1053621Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Joel Hockey <joelhockey@chromium.org>
Commit-Queue: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558169}