No description
  • C 98.2%
  • Assembly 1%
  • Makefile 0.3%
  • Shell 0.2%
  • Python 0.1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Greg Kroah-Hartman 5b6494b7be ANDROID: GKI: fs.h: add Android ABI padding to some structures
Try to mitigate potential future driver core api changes by adding a
padding to a bunch of filesystem structures.

Based on a change made to the RHEL/CENTOS 8 kernel.

Leaf changes summary: 12 artifacts changed
Changed leaf types summary: 12 leaf types changed
Removed/Changed/Added functions summary: 0 Removed, 0 Changed, 0 Added function
Removed/Changed/Added variables summary: 0 Removed, 0 Changed, 0 Added variable

'struct address_space at fs.h:445:1' changed:
  type size changed from 1280 to 1536 (in bits)
  4 data member insertions:
    'u64 address_space::android_kabi_reserved1', at offset 1280 (in bits) at fs.h:472:1
    'u64 address_space::android_kabi_reserved2', at offset 1344 (in bits) at fs.h:473:1
    'u64 address_space::android_kabi_reserved3', at offset 1408 (in bits) at fs.h:474:1
    'u64 address_space::android_kabi_reserved4', at offset 1472 (in bits) at fs.h:475:1

'struct address_space_operations at fs.h:362:1' changed:
  type size changed from 1344 to 1600 (in bits)
  4 data member insertions:
    'u64 address_space_operations::android_kabi_reserved1', at offset 1344 (in bits) at fs.h:412:1
    'u64 address_space_operations::android_kabi_reserved2', at offset 1408 (in bits) at fs.h:413:1
    'u64 address_space_operations::android_kabi_reserved3', at offset 1472 (in bits) at fs.h:414:1
    'u64 address_space_operations::android_kabi_reserved4', at offset 1536 (in bits) at fs.h:415:1

'struct block_device at fs.h:473:1' changed:
  type size changed from 1728 to 1984 (in bits)
  4 data member insertions:
    'u64 block_device::android_kabi_reserved1', at offset 1728 (in bits) at fs.h:521:1
    'u64 block_device::android_kabi_reserved2', at offset 1792 (in bits) at fs.h:522:1
    'u64 block_device::android_kabi_reserved3', at offset 1856 (in bits) at fs.h:523:1
    'u64 block_device::android_kabi_reserved4', at offset 1920 (in bits) at fs.h:524:1

'struct file_lock at fs.h:1080:1' changed:
  type size changed from 1728 to 1984 (in bits)
  3 data member insertions:
    'list_head file_lock::android_reserved1', at offset 1728 (in bits) at fs.h:1142:1
    'u64 file_lock::android_kabi_reserved1', at offset 1856 (in bits) at fs.h:1143:1
    'u64 file_lock::android_kabi_reserved2', at offset 1920 (in bits) at fs.h:1144:1

'struct file_lock_operations at fs.h:1030:1' changed:
  type size changed from 128 to 256 (in bits)
  2 data member insertions:
    'u64 file_lock_operations::android_kabi_reserved1', at offset 128 (in bits) at fs.h:1053:1
    'u64 file_lock_operations::android_kabi_reserved2', at offset 192 (in bits) at fs.h:1054:1

'struct file_operations at fs.h:1843:1' changed:
  type size changed from 2048 to 2304 (in bits)
  4 data member insertions:
    'u64 file_operations::android_kabi_reserved1', at offset 2048 (in bits) at fs.h:1918:1
    'u64 file_operations::android_kabi_reserved2', at offset 2112 (in bits) at fs.h:1919:1
    'u64 file_operations::android_kabi_reserved3', at offset 2176 (in bits) at fs.h:1920:1
    'u64 file_operations::android_kabi_reserved4', at offset 2240 (in bits) at fs.h:1921:1

'struct file_system_type at fs.h:2245:1' changed:
  type size changed from 640 to 896 (in bits)
  4 data member insertions:
    'u64 file_system_type::android_kabi_reserved1', at offset 640 (in bits) at fs.h:2322:1
    'u64 file_system_type::android_kabi_reserved2', at offset 704 (in bits) at fs.h:2323:1
    'u64 file_system_type::android_kabi_reserved3', at offset 768 (in bits) at fs.h:2324:1
    'u64 file_system_type::android_kabi_reserved4', at offset 832 (in bits) at fs.h:2325:1

'struct inode at fs.h:628:1' changed:
  type size changed from 4800 to 5184 (in bits)
  2 data member insertions:
    'u64 inode::android_kabi_reserved1', at offset 5056 (in bits) at fs.h:756:1
    'u64 inode::android_kabi_reserved2', at offset 5120 (in bits) at fs.h:757:1

'struct inode_operations at fs.h:1885:1' changed:
  type size changed from 1536 to 2048 (in bits)
  4 data member insertions:
    'u64 inode_operations::android_kabi_reserved1', at offset 1472 (in bits) at fs.h:1955:1
    'u64 inode_operations::android_kabi_reserved2', at offset 1536 (in bits) at fs.h:1956:1
    'u64 inode_operations::android_kabi_reserved3', at offset 1600 (in bits) at fs.h:1957:1
    'u64 inode_operations::android_kabi_reserved4', at offset 1664 (in bits) at fs.h:1958:1

'struct lock_manager_operations at fs.h:1035:1' changed:
  type size changed from 448 to 576 (in bits)
  2 data member insertions:
    'u64 lock_manager_operations::android_kabi_reserved1', at offset 448 (in bits) at fs.h:1066:1
    'u64 lock_manager_operations::android_kabi_reserved2', at offset 512 (in bits) at fs.h:1067:1

'struct super_block at fs.h:1431:1' changed:
  type size changed from 11776 to 12288 (in bits)
  4 data member insertions:
    'u64 super_block::android_kabi_reserved1', at offset 11648 (in bits) at fs.h:1592:1
    'u64 super_block::android_kabi_reserved2', at offset 11712 (in bits) at fs.h:1593:1
    'u64 super_block::android_kabi_reserved3', at offset 11776 (in bits) at fs.h:1594:1
    'u64 super_block::android_kabi_reserved4', at offset 11840 (in bits) at fs.h:1595:1

'struct super_operations at fs.h:1966:1' changed:
  type size changed from 1920 to 2176 (in bits)
  4 data member insertions:
    'u64 super_operations::android_kabi_reserved1', at offset 1920 (in bits) at fs.h:2048:1
    'u64 super_operations::android_kabi_reserved2', at offset 1984 (in bits) at fs.h:2049:1
    'u64 super_operations::android_kabi_reserved3', at offset 2048 (in bits) at fs.h:2050:1
    'u64 super_operations::android_kabi_reserved4', at offset 2112 (in bits) at fs.h:2051:1

Bug: 151154716
Change-Id: Ida6d98d30f292c980ab07e0250fec5268c4c87ed
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
2020-03-25 18:20:02 +01:00
arch This is the 5.4.28 stable release 2020-03-25 16:12:11 +01:00
block This is the 5.4.28 stable release 2020-03-25 16:12:11 +01:00
certs
crypto
Documentation This is the 5.4.28 stable release 2020-03-25 16:12:11 +01:00
drivers This is the 5.4.28 stable release 2020-03-25 16:12:11 +01:00
fs This is the 5.4.28 stable release 2020-03-25 16:12:11 +01:00
include ANDROID: GKI: fs.h: add Android ABI padding to some structures 2020-03-25 18:20:02 +01:00
init ANDROID: GKI: Add CONFIG_SOC_BUS to gki_defconfig 2020-03-24 09:17:27 +00:00
ipc
kernel This is the 5.4.28 stable release 2020-03-25 16:12:11 +01:00
lib
LICENSES
mm This is the 5.4.28 stable release 2020-03-25 16:12:11 +01:00
net This is the 5.4.27 stable release 2020-03-21 10:07:42 +01:00
samples
scripts This is the 5.4.28 stable release 2020-03-25 16:12:11 +01:00
security This is the 5.4.25 stable release 2020-03-12 17:09:04 +01:00
sound This is the 5.4.28 stable release 2020-03-25 16:12:11 +01:00
tools This is the 5.4.27 stable release 2020-03-21 10:07:42 +01:00
usr
virt
.clang-format
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore
.mailmap
abi_gki_aarch64.xml ANDROID: GKI: fs.h: add Android ABI padding to some structures 2020-03-25 18:20:02 +01:00
abi_gki_aarch64_cuttlefish_whitelist ANDROID: update abi_gki_aarch64_cuttlefish_whitelist 2020-03-12 14:34:21 +00:00
abi_gki_aarch64_db845c_whitelist ANDROID: ABI/Whitelist: update for db845c 2020-03-24 15:39:03 +00:00
abi_gki_aarch64_hikey960_whitelist ANDROID: ABI/Whitelist: update for hikey960 2020-03-23 23:39:45 +00:00
abi_gki_aarch64_unisoc_whitelist ANDROID: ABI/Whitelist: update whitelist of unisoc 2020-03-25 15:14:02 +08:00
abi_gki_aarch64_whitelist
build.config.aarch64
build.config.allmodconfig
build.config.allmodconfig.aarch64
build.config.allmodconfig.arm ANDROID: Add build.config files for ARM 32-bit 2020-03-15 22:51:11 +00:00
build.config.allmodconfig.x86_64
build.config.arm ANDROID: Add build.config files for ARM 32-bit 2020-03-15 22:51:11 +00:00
build.config.common
build.config.cuttlefish.aarch64
build.config.cuttlefish.x86_64
build.config.db845c
build.config.gki
build.config.gki-debug.aarch64 ANDROID: Add build.config.gki-debug.aarch64 2020-03-16 09:20:25 +00:00
build.config.gki-debug.x86_64 ANDROID: Add build.config.gki-debug.x86_64 2020-03-16 14:27:00 +00:00
build.config.gki.aarch64 ANDROID: ABI/Whitelist: update for hikey960 2020-03-23 23:39:45 +00:00
build.config.gki.x86_64
build.config.hikey960 ANDROID: hikey960: Add external mali driver support to build.config.hikey960 2020-03-23 22:55:17 +00:00
build.config.x86_64
COPYING
CREDITS
cuttlefish.fragment ANDROID: Add TPM support and the vTPM proxy to Cuttlefish. 2020-03-13 15:01:14 +00:00
Kbuild
Kconfig
MAINTAINERS
Makefile This is the 5.4.28 stable release 2020-03-25 16:12:11 +01:00
README
README.md

How do I submit patches to Android Common Kernels

  1. BEST: Make all of your changes to upstream Linux. If appropriate, backport to the stable releases. These patches will be merged automatically in the corresponding common kernels. If the patch is already in upstream Linux, post a backport of the patch that conforms to the patch requirements below.

  2. LESS GOOD: Develop your patches out-of-tree (from an upstream Linux point-of-view). Unless these are fixing an Android-specific bug, these are very unlikely to be accepted unless they have been coordinated with kernel-team@android.com. If you want to proceed, post a patch that conforms to the patch requirements below.

Common Kernel patch requirements

  • All patches must conform to the Linux kernel coding standards and pass script/checkpatch.pl
  • Patches shall not break gki_defconfig or allmodconfig builds for arm, arm64, x86, x86_64 architectures (see https://source.android.com/setup/build/building-kernels)
  • If the patch is not merged from an upstream branch, the subject must be tagged with the type of patch: UPSTREAM:, BACKPORT:, FROMGIT:, FROMLIST:, or ANDROID:.
  • All patches must have a Change-Id: tag (see https://gerrit-review.googlesource.com/Documentation/user-changeid.html)
  • If an Android bug has been assigned, there must be a Bug: tag.
  • All patches must have a Signed-off-by: tag by the author and the submitter

Additional requirements are listed below based on patch type

Requirements for backports from mainline Linux: UPSTREAM:, BACKPORT:

  • If the patch is a cherry-pick from Linux mainline with no changes at all
    • tag the patch subject with UPSTREAM:.
    • add upstream commit information with a (cherry-picked from ...) line
    • Example:
      • if the upstream commit message is
        important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>
    - then Joe Smith would upload the patch for the common kernel as
        UPSTREAM: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        (cherry-picked from c31e73121f4c1ec41143423ac6ce3ce6dafdcec1)
        Signed-off-by: Joe Smith <joe.smith@foo.org>
  • If the patch requires any changes from the upstream version, tag the patch with BACKPORT: instead of UPSTREAM:.
    • use the same tags as UPSTREAM:
    • add comments about the changes under the (cherry-picked from ...) line
    • Example:
        BACKPORT: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        (cherry-picked from c31e73121f4c1ec41143423ac6ce3ce6dafdcec1)
        [ Resolved minor conflict in drivers/foo/bar.c ]
        Signed-off-by: Joe Smith <joe.smith@foo.org>

Requirements for other backports: FROMGIT:, FROMLIST:,

  • If the patch has been merged into an upstream maintainer tree, but has not yet been merged into Linux mainline
    • tag the patch subject with FROMGIT:
    • add info on where the patch came from as (cherry picked from commit <sha1> <repo> <branch>). This must be a stable maintainer branch (not rebased, so don't use linux-next for example).
    • if changes were required, use BACKPORT: FROMGIT:
    • Example:
      • if the commit message in the maintainer tree is
        important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>
    - then Joe Smith would upload the patch for the common kernel as
        FROMGIT: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        (cherry picked from commit 878a2fd9de10b03d11d2f622250285c7e63deace
         https://git.kernel.org/pub/scm/linux/kernel/git/foo/bar.git test-branch)
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        Signed-off-by: Joe Smith <joe.smith@foo.org>
  • If the patch has been submitted to LKML, but not accepted into any maintainer tree
    • tag the patch subject with FROMLIST:
    • add a Link: tag with a link to the submittal on lore.kernel.org
    • if changes were required, use BACKPORT: FROMLIST:
    • Example:
        FROMLIST: important patch from upstream

        This is the detailed description of the important patch

        Signed-off-by: Fred Jones <fred.jones@foo.org>

        Bug: 135791357
        Link: https://lore.kernel.org/lkml/20190619171517.GA17557@someone.com/
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        Signed-off-by: Joe Smith <joe.smith@foo.org>

Requirements for Android-specific patches: ANDROID:

  • If the patch is fixing a bug to Android-specific code
    • tag the patch subject with ANDROID:
    • add a Fixes: tag that cites the patch with the bug
    • Example:
        ANDROID: fix android-specific bug in foobar.c

        This is the detailed description of the important fix

        Fixes: 1234abcd2468 ("foobar: add cool feature")
        Change-Id: I4caaaa566ea080fa148c5e768bb1a0b6f7201c01
        Signed-off-by: Joe Smith <joe.smith@foo.org>
  • If the patch is a new feature
    • tag the patch subject with ANDROID:
    • add a Bug: tag with the Android bug (required for android-specific features)