Skip to content
Snippets Groups Projects
Select Git revision
  • android-7.1.2_r28_klist
  • master default protected
  • pie-cts-release
  • pie-vts-release
  • pie-cts-dev
  • oreo-mr1-iot-release
  • sdk-release
  • oreo-m6-s4-release
  • oreo-m4-s12-release
  • pie-release
  • pie-r2-release
  • pie-r2-s1-release
  • oreo-vts-release
  • oreo-cts-release
  • oreo-dev
  • oreo-mr1-dev
  • pie-gsi
  • pie-platform-release
  • pie-dev
  • oreo-cts-dev
  • android-o-mr1-iot-release-1.0.4
  • android-9.0.0_r8
  • android-9.0.0_r7
  • android-9.0.0_r6
  • android-9.0.0_r5
  • android-8.1.0_r46
  • android-8.1.0_r45
  • android-n-iot-release-smart-display-r2
  • android-vts-8.1_r5
  • android-cts-8.1_r8
  • android-cts-8.0_r12
  • android-cts-7.1_r20
  • android-cts-7.0_r24
  • android-o-mr1-iot-release-1.0.3
  • android-cts-9.0_r1
  • android-8.1.0_r43
  • android-8.1.0_r42
  • android-n-iot-release-smart-display
  • android-p-preview-5
  • android-9.0.0_r3
40 results

AndroidSystemSEPolicy

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    padarshr authored
    Allow init the ability to relabel recovery block devices. In the case
    where we have recovery as a chain partition, due to its presence in
    early mount node, init, in first stage itself would require relabel
    permissions for the restorecon operation on recovery block device.
    
    Bug: 73642793
    Test: On bootup, recovery partition gets the appropriate se-label.
          Perform OTA on non-A/B device with recovery as chain partition,
          now the recovery partition gets upgraded successfully, now that
          it has the correct se-label.
    
    Change-Id: I370c510320e78ab78c9c55573073415b4983d0f6
    Merged-In: I370c510320e78ab78c9c55573073415b4983d0f6
    (cherry picked from commit bc14ee3c)
    ecab4010
    History
    Name Last commit Last update