Skip to content
Snippets Groups Projects
  1. Oct 02, 2018
    • Tri Vo's avatar
      Only maintain maps between current and previous selinux versions. · 438684b3
      Tri Vo authored
      New maintenance scheme for mapping files:
      Say, V is the current SELinux platform version, then at any point in time we
      only maintain (V->V-1) mapping. (V->V-n) map is constructed from top (V->V-n+1)
      and bottom (V-n+1->V-n) without changes to previously maintained mapping files.
      
      Caveats:
      - 26.0.cil doesn't technically represent 27.0->26.0 map, but rather
      current->26.0. We'll fully migrate to the scheme with future releases.
      
      Bug: 67510052
      Test: adding new public type only requires changing the latest compat map
      Change-Id: Iab5564e887ef2c8004cb493505dd56c6220c61f8
      438684b3
  2. Sep 29, 2018
    • Tri Vo's avatar
      Don't require private types in mapping file. · e3f4f77d
      Tri Vo authored
      Private types are not visible to vendor/odm policy, so we don't need mapping
      entries for them.
      
      We build platform-only public policy .cil file and give it as input to
      treble_sepolicy_tests. Using this public policy the test can now figure out if
      the newly added type in public or private.
      
      Bug: 116344577
      Test: adding public type triggers mapping test failure, adding private type does
      not.
      Change-Id: I421f335e37274b24aa73109e260653d7b73788b5
      e3f4f77d
  3. Feb 07, 2018
    • Tri Vo's avatar
      Silence expandtypeattribute build-time warning. · 19047a6a
      Tri Vo authored
      treble_sepolicy_tests emit during build time warnings for
      expandtypeattribute statements in the mapping file.
      Silence those warning.
      
      Bug: 72757373
      Test: build sepolicy
      Change-Id: Ia40d80d8172c96c75854d2e1ec0d284ea0724b5c
      19047a6a
  4. Sep 26, 2017
  5. Aug 09, 2017
  6. Aug 08, 2017
    • Dan Cashman's avatar
      Add 26.0 api compatibility check infrastructure. · 7f7c3b82
      Dan Cashman authored
      Add support to the treble_sepolicy_tests suite that explicitly look at
      the old and current policy versions, as well as the compatibility file,
      to determine if any new types have been added without a compatibility
      entry.  This first test catches the most common and likely changes that
      could change the type label of an object for which vendor policy may have
      needed access.  It also should prove the basis for additional compatibility
      checks between old and new policies.
      
      Bug: 36899958
      Test: Policy builds and tests pass.
      Change-Id: I609c913e6354eb10a04cc1a029ddd9fa0e592a4c
      7f7c3b82
Loading