These two drivers support every >1 gigabit usb ethernet dongle
I've managed to get my hands on.
In practice already enabled on GKI 5.10+ since S.
$ for i in AND510{S,T} AND515T ANDM; do cd /git/$i; echo; echo $i; git grep '^CONFIG_USB_NET_AQC111=y$' | egrep gki_defconfig; done
AND510S
arch/arm64/configs/gki_defconfig:342:CONFIG_USB_NET_AQC111=y
arch/x86/configs/gki_defconfig:314:CONFIG_USB_NET_AQC111=y
AND510T
arch/arm64/configs/gki_defconfig:354:CONFIG_USB_NET_AQC111=y
arch/x86/configs/gki_defconfig:325:CONFIG_USB_NET_AQC111=y
AND515T
arch/arm64/configs/gki_defconfig:350:CONFIG_USB_NET_AQC111=y
arch/x86/configs/gki_defconfig:320:CONFIG_USB_NET_AQC111=y
ANDM
arch/arm64/configs/gki_defconfig:342:CONFIG_USB_NET_AQC111=y
arch/x86/configs/gki_defconfig:315:CONFIG_USB_NET_AQC111=y
(while CONFIG_USB_NET_CDC_NCM defaults to 'y')
Test: TreeHugger
Bug: 183564444
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I6c9f71288d46c310c96bbfadfcf18a35a30e8511
Can be used for implementing better ingress rate limiting.
In practice already enabled on GKI 5.10+ since S.
$ for i in AND510{S,T} AND515T ANDM; do cd /git/$i; echo; echo $i; git grep '^CONFIG_IFB=y$' | egrep gki_defconfig; done
AND510S
arch/arm64/configs/gki_defconfig:324:CONFIG_IFB=y
arch/x86/configs/gki_defconfig:296:CONFIG_IFB=y
AND510T
arch/arm64/configs/gki_defconfig:337:CONFIG_IFB=y
arch/x86/configs/gki_defconfig:308:CONFIG_IFB=y
AND515T
arch/arm64/configs/gki_defconfig:333:CONFIG_IFB=y
arch/x86/configs/gki_defconfig:303:CONFIG_IFB=y
ANDM
arch/arm64/configs/gki_defconfig:325:CONFIG_IFB=y
arch/x86/configs/gki_defconfig:298:CONFIG_IFB=y
Test: TreeHugger
Bug: 179454839
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I04cf0ca5dae83d73f91b75b99fd6263c7e686aef
Now with GKI, we no longer recommend configs.
Test: TH
Bug: 230144764
Change-Id: I3f3f9401482603eb41d03870b1a233d31b54a367
Merged-In: I3f3f9401482603eb41d03870b1a233d31b54a367
CONFIG_INIT_STACK_ALL_ZERO minimizes the effect of bugs caused by uninitialized locals, so we want to prevent it from being accidentally disabled.
Bug: 204439281
Bug: 205279854
Test: TreeHugger
Change-Id: I2014cd9bc2e3ebb8442ccc632c82619d62645dd4
Turns unbounded recursion in kernel code from being a potentially
exploitable bug into a crash.
This is likely a no-op. CONFIG_VMAP_STACK is already the default
on architectures that support it. CONFIG_VMAP_STACK has been
supported on x86_64 since 4.9 and on arm64 since 4.14. This change
is to prevent it from being accidentally disabled.
Test: On Pixel 5:
adb pull /proc/config.gz gunzip config.gz;
grep CONFIG_VMAP_STACK=y config
Bug: 117194687
Change-Id: I458d7a9d3a28b057b372a7456dbdeb3397423a15
Signed-off-by: Jeff Vander Stoep <jeffv@google.com>
This reverts commit dd46951e69.
Reason for revert: downstream kernel projects failed an unrelated SELinux related test when they
updated from Android Common Kernel, so they rolled back their pull dropping the patches necessary
to make this test pass.
Bug: 210043760
Bug: 214384465
Change-Id: I0f591dfa23017fec00733891dad6ec286a697585
Check that clang is used to assemble the kernel (CONFIG_AS_IS_LLVM).
This is implied by setting LLVM=1 in linux-5.15.y or LLVM_IAS=1 in
linux-5.10.y.
Bug: 209655537
Bug: 210043760
Bug: 213947595
Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
Change-Id: I131460e03a733444cc6167ecdc070db1477c854c
These are already covered by vts_kernel_toolchain. Add the additional
requirements that clang be used as the compiler (CONFIG_CC_IS_CLANG=y)
and lld as the linker (CONFIG_LD_IS_LLD).
For Android:
* CC=clang was required for aarch64 in Q.
* CC=clang was required in R.
* LD=lld was required for S.
A follow up patch with additionally check for CONFIG_AS_IS_LLVM=y once
the dependencies are backported properly.
Bug: 209655537
Bug: 210043760
Test: Treehugger
Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
Change-Id: I0e54800d92323e7a9931914a054dd713eaea03c9
