mirror of
https://github.com/hardkernel/linux.git
synced 2026-06-07 11:26:02 +09:00
352619da21
Set KMI_GENERATION=1 for 3/1 KMI update Location: "Kernel ABI difference" Analyzer Description: Report STG ABI changes between builds (stgdiff on .stg). Owner: gki-eng-team@google.com ABI for 'kernel_abi_aarch64' on 'aosp_kernel-common-android14-5.15' has changed. [old=ab/9668063/kernel_abi_aarch64; new=ab/P51085744/kernel_abi_aarch64; file=abi.stg; tool=stgdiff_stg; version=AyeAye - CL 512944641 android-build.ayeaye-python-dispatcher_20230228.05_p0; rc=4] For more information, please visit go/kernel-abi-monitoring. function symbol 'int aead_register_instance(struct crypto_template*, struct aead_instance*)' changed CRC changed from 0x4842bcc to 0x523040da function symbol 'int ahash_register_instance(struct crypto_template*, struct ahash_instance*)' changed CRC changed from 0xa4ff2220 to 0x1ea3dc79 function symbol 'int crypto_aead_decrypt(struct aead_request*)' changed CRC changed from 0xd5621133 to 0x40117c2 ... 65 omitted; 68 symbols have only CRC changes type 'struct aead_instance' changed byte size changed from 768 to 576 member changed from 'union { struct { char head[128]; struct crypto_instance base; } s; struct aead_alg alg; }' to 'union { struct { char head[64]; struct crypto_instance base; } s; struct aead_alg alg; }' offset changed from 1024 to 512 type changed from 'union { struct { char head[128]; struct crypto_instance base; } s; struct aead_alg alg; }' to 'union { struct { char head[64]; struct crypto_instance base; } s; struct aead_alg alg; }' byte size changed from 640 to 512 member changed from 'struct { char head[128]; struct crypto_instance base; } s' to 'struct { char head[64]; struct crypto_instance base; } s' type changed from 'struct { char head[128]; struct crypto_instance base; }' to 'struct { char head[64]; struct crypto_instance base; }' byte size changed from 640 to 512 member changed from 'char head[128]' to 'char head[64]' type changed from 'char[128]' to 'char[64]' number of elements changed from 128 to 64 member 'struct crypto_instance base' changed offset changed by -512 type 'struct ahash_instance' changed byte size changed from 896 to 704 member changed from 'union { struct { char head[256]; struct crypto_instance base; } s; struct ahash_alg alg; }' to 'union { struct { char head[192]; struct crypto_instance base; } s; struct ahash_alg alg; }' offset changed from 1024 to 512 type changed from 'union { struct { char head[256]; struct crypto_instance base; } s; struct ahash_alg alg; }' to 'union { struct { char head[192]; struct crypto_instance base; } s; struct ahash_alg alg; }' byte size changed from 768 to 640 member changed from 'struct { char head[256]; struct crypto_instance base; } s' to 'struct { char head[192]; struct crypto_instance base; } s' type changed from 'struct { char head[256]; struct crypto_instance base; }' to 'struct { char head[192]; struct crypto_instance base; }' byte size changed from 768 to 640 member changed from 'char head[256]' to 'char head[192]' type changed from 'char[256]' to 'char[192]' number of elements changed from 256 to 192 member 'struct crypto_instance base' changed offset changed by -512 type 'struct crypto_aead' changed byte size changed from 256 to 128 member 'struct crypto_tfm base' changed offset changed by -512 type 'struct crypto_ahash' changed byte size changed from 256 to 192 type 'struct crypto_tfm' changed byte size changed from 128 to 64 member 'void* __crt_ctx[0]' changed offset changed by -512 type 'struct crypto_rng' changed byte size changed from 128 to 64 type 'struct crypto_shash' changed byte size changed from 256 to 128 member 'struct crypto_tfm base' changed offset changed by -512 type 'struct crypto_skcipher' changed byte size changed from 256 to 128 member 'struct crypto_tfm base' changed offset changed by -512 type 'struct crypto_sync_skcipher' changed byte size changed from 256 to 128 type 'struct crypto_cipher' changed byte size changed from 128 to 64 type 'struct crypto_comp' changed byte size changed from 128 to 64 type 'struct crypto_instance' changed byte size changed from 512 to 448 member 'void* __ctx[0]' changed offset changed by -512 type 'struct aead_alg' changed byte size changed from 512 to 448 member 'struct crypto_alg base' changed offset changed by -512 type 'struct ahash_alg' changed byte size changed from 640 to 576 type 'struct rng_alg' changed byte size changed from 512 to 448 member 'struct crypto_alg base' changed offset changed by -512 type 'struct shash_alg' changed byte size changed from 640 to 576 member 'struct crypto_alg base' changed offset changed by -512 type 'struct skcipher_alg' changed byte size changed from 512 to 448 member 'struct crypto_alg base' changed offset changed by -512 type 'struct shash_instance' changed byte size changed from 896 to 704 member changed from 'union { struct { char head[256]; struct crypto_instance base; } s; struct shash_alg alg; }' to 'union { struct { char head[192]; struct crypto_instance base; } s; struct shash_alg alg; }' offset changed from 1024 to 512 type changed from 'union { struct { char head[256]; struct crypto_instance base; } s; struct shash_alg alg; }' to 'union { struct { char head[192]; struct crypto_instance base; } s; struct shash_alg alg; }' byte size changed from 768 to 640 member changed from 'struct { char head[256]; struct crypto_instance base; } s' to 'struct { char head[192]; struct crypto_instance base; } s' type changed from 'struct { char head[256]; struct crypto_instance base; }' to 'struct { char head[192]; struct crypto_instance base; }' byte size changed from 768 to 640 member changed from 'char head[256]' to 'char head[192]' type changed from 'char[256]' to 'char[192]' number of elements changed from 256 to 192 member 'struct crypto_instance base' changed offset changed by -512 type 'struct skcipher_instance' changed byte size changed from 768 to 576 member changed from 'union { struct { char head[128]; struct crypto_instance base; } s; struct skcipher_alg alg; }' to 'union { struct { char head[64]; struct crypto_instance base; } s; struct skcipher_alg alg; }' offset changed from 1024 to 512 type changed from 'union { struct { char head[128]; struct crypto_instance base; } s; struct skcipher_alg alg; }' to 'union { struct { char head[64]; struct crypto_instance base; } s; struct skcipher_alg alg; }' byte size changed from 640 to 512 member changed from 'struct { char head[128]; struct crypto_instance base; } s' to 'struct { char head[64]; struct crypto_instance base; } s' type changed from 'struct { char head[128]; struct crypto_instance base; }' to 'struct { char head[64]; struct crypto_instance base; }' byte size changed from 640 to 512 member changed from 'char head[128]' to 'char head[64]' type changed from 'char[128]' to 'char[64]' number of elements changed from 128 to 64 member 'struct crypto_instance base' changed offset changed by -512 type 'struct hash_alg_common' changed byte size changed from 512 to 448 member 'struct crypto_alg base' changed offset changed by -512 Bug: 271188187 Change-Id: I0f5a5967bda2df567d26d9bb5acef4c16b31cfc9 Signed-off-by: Todd Kjos <tkjos@google.com>
How do I submit patches to Android Common Kernels
-
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.
- Do not send patches upstream that contain only symbol exports. To be considered for upstream Linux,
additions of
EXPORT_SYMBOL_GPL()require an in-tree modular driver that uses the symbol -- so include the new driver or changes to an existing driver in the same patchset as the export. - When sending patches upstream, the commit message must contain a clear case for why the patch is needed and beneficial to the community. Enabling out-of-tree drivers or functionality is not not a persuasive case.
- Do not send patches upstream that contain only symbol exports. To be considered for upstream Linux,
additions of
-
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
scripts/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:, orANDROID:. - 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 commit ...)line - Example:
- if the upstream commit message is
- tag the patch subject with
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 commit 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 ofUPSTREAM:.- use the same tags as
UPSTREAM: - add comments about the changes under the
(cherry picked from commit ...)line - Example:
- use the same tags as
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 commit c31e73121f4c1ec41143423ac6ce3ce6dafdcec1)
[joe: 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 uselinux-nextfor example). - if changes were required, use
BACKPORT: FROMGIT: - Example:
- if the commit message in the maintainer tree is
- tag the patch subject with
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 - add a
Bug:tag with the Android bug (required for patches not accepted into a maintainer tree) - if changes were required, use
BACKPORT: FROMLIST: - Example:
- tag the patch subject with
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:
- tag the patch subject with
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)
- tag the patch subject with