Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multirom: Fix /data/media/0 media linkage for SDCardFS #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AdrianDC
Copy link
Member

@AdrianDC AdrianDC commented May 22, 2017

  • In a MultiROM environment, /data is owned by the
    booted secondary ROM, specifically it can even be
    part of an external MicroSD (for example with EXT4)

  • By using a ROM supporting SDCardFS, the interal
    media storage will be accessed through its driver,
    but the fact /data/media/0 could be used under
    specific conditions means the /data/media mounts
    used by the emulated storage loop through:

    • /data/media (external ROM)
    • /data/media/0 (internal storage)
  • SDCardFS prevents "cross-device" linkage by
    returning -EXDEV, breaking internal storage access

  • Always use the proper /data/media path on newer APIs
    to avoid any cross-device linkage of internal storage,
    and preserve old handling up to API 22 (Android 5.1)

Change-Id: Ib49db68eede289d3943b9537d542eef5082e3118
Signed-off-by: Adrian DC radian.dc@gmail.com

 * In a MultiROM environment, /data is owned by the
    booted secondary ROM, specifically it can even be
    part of an external MicroSD (for example with EXT4)

 * By using a ROM supporting SDCardFS, the interal
    media storage will be accessed through its driver,
    but the fact /data/media/0 could be used under
    specific conditions means the /data/media mounts
    used by the emulated storage loop through:
     - /data/media (external ROM)
     - /data/media/0 (internal storage)

 * SDCardFS prevents "cross-device" linkage by
    returning -EXDEV, breaking internal storage access

 * Always use the proper /data/media path on newer APIs
    to avoid any cross-device linkage of internal storage,
    and preserve old handling up to API 22 (Android 5.1)

Change-Id: Ib49db68eede289d3943b9537d542eef5082e3118
Signed-off-by: Adrian DC <radian.dc@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant