forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/linux-samsung-klte/APKBUILD

108 lines
5.5 KiB
Text
Raw Normal View History

linux-samsung-klte: modernize, update sources (!94) Use latest sources from LineageOS, instead of the ones from andip71. The APKBUILD is modernized to use the devicepkg-dev but unfortunately compiling with gcc8 it doesn't boot. The kernel config is updated with the required options to start the lxc-android container and xf86-video-hwcomposer works (tested with xfce4). My plan was to add the firmware-samsung-klte with the subpackages for the wifi blobs and a precompiled android system.img to use with libhybris, but my device just died and I'm not able to power it on (I've probably burnt the Power IC 😢)
2018-12-04 00:35:27 +00:00
# Reference: <https://postmarketos.org/vendorkernel>
# Kernel config based on: arch/arm/configs/msm8974_sec_defconfig
# arch/arm/configs/msm8974pro_sec_klte_eur_defconfig
# arch/arm/configs/selinux_defconfig
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
pkgname="linux-samsung-klte"
linux-samsung-klte: modernize, update sources (!94) Use latest sources from LineageOS, instead of the ones from andip71. The APKBUILD is modernized to use the devicepkg-dev but unfortunately compiling with gcc8 it doesn't boot. The kernel config is updated with the required options to start the lxc-android container and xf86-video-hwcomposer works (tested with xfce4). My plan was to add the firmware-samsung-klte with the subpackages for the wifi blobs and a precompiled android system.img to use with libhybris, but my device just died and I'm not able to power it on (I've probably burnt the Power IC 😢)
2018-12-04 00:35:27 +00:00
pkgver=3.4.113
samsung-klte: backport memfd_create() syscall (!479) This brings in several patches needed to add support for a memfd_create() syscall into kernel version 3.4 from kernel version 3.17. This is required for running lxc >= 3.1.0-r1 with security patch that fixes CVE-2019-5736. In short, security issue was: in a privileged container root process could overwrite lxc-start executable by opening its file descriptor and rewriting executable contents. This is where memfd comes to help: you can create an in-memory file, copy your executable there, and place a set of SEALS to protect it from modifying at a deep level. Then you fexecve() that fd and you're safe. For example, pulseaudio also can benefit from having memfd_create() implemented. This backports the following commits from upstream linux: - dd37978c50bc8b354e5c4633f69387f16572fdac: cache the value of file_inode() in struct file commit from linux-3.10 to have an f_inode member inside struct file and a helper function file_inode() that is used in some of the following commits - 40e041a2c858b3caefc757e26cb85bfceae5062b shm: add sealing API from 3.17: security measure called SEALS, that you can put on memfd file to restrict operations on it - 9183df25fe7b194563db3fec6dc3202a5855839c shm: add memfd_create() syscall also from 3.17 - 503e6636b6f96056210062be703356f4253b6db9 asm-generic: add memfd_create system call to unistd.h - e57e41931134e09fc6c03c8d4eb19d516cc6e59b ARM: wire up memfd_create syscall The last two are needed to make the syscall visible/usable from userspace, one in generic context, other for ARM arch. The test program (https://github.com/minlexx/test_memfd/) was written to verify that this works. [ci:skip-build]: already built successfully in CI
2019-07-01 00:29:30 +00:00
pkgrel=5
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
pkgdesc="Samsung Galaxy S5 kernel fork"
samsung-klte: Switch to armv7 (!272) Tested. Works fine on klte. Boots to weston. [ci:skip-build]: already built successfully
2019-03-11 08:41:05 +00:00
arch="armv7"
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
_carch="arm"
_flavor="samsung-klte"
linux-samsung-klte: modernize, update sources (!94) Use latest sources from LineageOS, instead of the ones from andip71. The APKBUILD is modernized to use the devicepkg-dev but unfortunately compiling with gcc8 it doesn't boot. The kernel config is updated with the required options to start the lxc-android container and xf86-video-hwcomposer works (tested with xfce4). My plan was to add the firmware-samsung-klte with the subpackages for the wifi blobs and a precompiled android system.img to use with libhybris, but my device just died and I'm not able to power it on (I've probably burnt the Power IC 😢)
2018-12-04 00:35:27 +00:00
url="https://kernel.org"
license="GPL-2.0-only"
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
options="!strip !check !tracedeps"
linux-samsung-klte: modernize, update sources (!94) Use latest sources from LineageOS, instead of the ones from andip71. The APKBUILD is modernized to use the devicepkg-dev but unfortunately compiling with gcc8 it doesn't boot. The kernel config is updated with the required options to start the lxc-android container and xf86-video-hwcomposer works (tested with xfce4). My plan was to add the firmware-samsung-klte with the subpackages for the wifi blobs and a precompiled android system.img to use with libhybris, but my device just died and I'm not able to power it on (I've probably burnt the Power IC 😢)
2018-12-04 00:35:27 +00:00
makedepends="perl sed installkernel bash gmp-dev bc linux-headers elfutils-dev xz dtbtool devicepkg-dev gcc6"
device/linux-*: make all kernels compile again All kernels compile again, after the GCC 8 upgrade. All 3.x kernels have been changed to use GCC 6 now, because we can't say for sure that they boot with GCC 8 even if we made them compile with that newer GCC. If someone wants to test a kernel for a newer device which they can test, see the instructions on <https://postmarketos.org/vendorkernel>. The linux-sony-castor-windy 4.x kernel did not compile out of the box with the latest GCC, so we set it to GCC 6 as well. This can probably be fixed easily. linux-teclast-x80-pro: removed Werror and updated to latest 4.14 kernel from kernel.org, otherwise this would not compile anymore (tested with both GCC 6 and 8, probably incompatibility with the latest binutils or something). This commit will take too long to compile in CI, so let's [skip ci]. I've compiled all kernels multiple times and fixed them up until all of them were working again. Related: #103
2018-10-01 06:44:18 +00:00
linux-samsung-klte: modernize, update sources (!94) Use latest sources from LineageOS, instead of the ones from andip71. The APKBUILD is modernized to use the devicepkg-dev but unfortunately compiling with gcc8 it doesn't boot. The kernel config is updated with the required options to start the lxc-android container and xf86-video-hwcomposer works (tested with xfce4). My plan was to add the firmware-samsung-klte with the subpackages for the wifi blobs and a precompiled android system.img to use with libhybris, but my device just died and I'm not able to power it on (I've probably burnt the Power IC 😢)
2018-12-04 00:35:27 +00:00
# Compiler: GCC 6 (doesn't boot when compiled with newer versions)
device/linux-*: make all kernels compile again All kernels compile again, after the GCC 8 upgrade. All 3.x kernels have been changed to use GCC 6 now, because we can't say for sure that they boot with GCC 8 even if we made them compile with that newer GCC. If someone wants to test a kernel for a newer device which they can test, see the instructions on <https://postmarketos.org/vendorkernel>. The linux-sony-castor-windy 4.x kernel did not compile out of the box with the latest GCC, so we set it to GCC 6 as well. This can probably be fixed easily. linux-teclast-x80-pro: removed Werror and updated to latest 4.14 kernel from kernel.org, otherwise this would not compile anymore (tested with both GCC 6 and 8, probably incompatibility with the latest binutils or something). This commit will take too long to compile in CI, so let's [skip ci]. I've compiled all kernels multiple times and fixed them up until all of them were working again. Related: #103
2018-10-01 06:44:18 +00:00
if [ "${CC:0:5}" != "gcc6-" ]; then
CC="gcc6-$CC"
Revert "linux-*: use upstream gcc6 [skip ci]" This reverts commit ee659a5bb4ad94f33ec47e6ae7bf9e856f627155 and increases the pkgrels of all affected linux pmaports. I have compiled *every single kernel* that was modified with this commit, and it worked. That took 12 hours. So I'm pretty confident that this is a good commit. Let's roll it out and go back to stability \o/ I'll kick off the binary repo building directly after pushing this, but it will take some time until all binary packages are available again. [skip ci]: it wouldn't finish in time.
2018-11-30 20:56:06 +00:00
HOSTCC="gcc6-gcc"
device/linux-*: make all kernels compile again All kernels compile again, after the GCC 8 upgrade. All 3.x kernels have been changed to use GCC 6 now, because we can't say for sure that they boot with GCC 8 even if we made them compile with that newer GCC. If someone wants to test a kernel for a newer device which they can test, see the instructions on <https://postmarketos.org/vendorkernel>. The linux-sony-castor-windy 4.x kernel did not compile out of the box with the latest GCC, so we set it to GCC 6 as well. This can probably be fixed easily. linux-teclast-x80-pro: removed Werror and updated to latest 4.14 kernel from kernel.org, otherwise this would not compile anymore (tested with both GCC 6 and 8, probably incompatibility with the latest binutils or something). This commit will take too long to compile in CI, so let's [skip ci]. I've compiled all kernels multiple times and fixed them up until all of them were working again. Related: #103
2018-10-01 06:44:18 +00:00
CROSS_COMPILE="gcc6-$CROSS_COMPILE"
fi
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
# Source
linux-samsung-klte: modernize, update sources (!94) Use latest sources from LineageOS, instead of the ones from andip71. The APKBUILD is modernized to use the devicepkg-dev but unfortunately compiling with gcc8 it doesn't boot. The kernel config is updated with the required options to start the lxc-android container and xf86-video-hwcomposer works (tested with xfce4). My plan was to add the firmware-samsung-klte with the subpackages for the wifi blobs and a precompiled android system.img to use with libhybris, but my device just died and I'm not able to power it on (I've probably burnt the Power IC 😢)
2018-12-04 00:35:27 +00:00
_repository="android_kernel_samsung_msm8974"
samsung-klte: backport memfd_create() syscall (!479) This brings in several patches needed to add support for a memfd_create() syscall into kernel version 3.4 from kernel version 3.17. This is required for running lxc >= 3.1.0-r1 with security patch that fixes CVE-2019-5736. In short, security issue was: in a privileged container root process could overwrite lxc-start executable by opening its file descriptor and rewriting executable contents. This is where memfd comes to help: you can create an in-memory file, copy your executable there, and place a set of SEALS to protect it from modifying at a deep level. Then you fexecve() that fd and you're safe. For example, pulseaudio also can benefit from having memfd_create() implemented. This backports the following commits from upstream linux: - dd37978c50bc8b354e5c4633f69387f16572fdac: cache the value of file_inode() in struct file commit from linux-3.10 to have an f_inode member inside struct file and a helper function file_inode() that is used in some of the following commits - 40e041a2c858b3caefc757e26cb85bfceae5062b shm: add sealing API from 3.17: security measure called SEALS, that you can put on memfd file to restrict operations on it - 9183df25fe7b194563db3fec6dc3202a5855839c shm: add memfd_create() syscall also from 3.17 - 503e6636b6f96056210062be703356f4253b6db9 asm-generic: add memfd_create system call to unistd.h - e57e41931134e09fc6c03c8d4eb19d516cc6e59b ARM: wire up memfd_create syscall The last two are needed to make the syscall visible/usable from userspace, one in generic context, other for ARM arch. The test program (https://github.com/minlexx/test_memfd/) was written to verify that this works. [ci:skip-build]: already built successfully in CI
2019-07-01 00:29:30 +00:00
_commit="edfd9dd9be89d15c34f653363a9a3c9108146ca0"
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
_config="config-${_flavor}.${arch}"
source="
linux-samsung-klte: modernize, update sources (!94) Use latest sources from LineageOS, instead of the ones from andip71. The APKBUILD is modernized to use the devicepkg-dev but unfortunately compiling with gcc8 it doesn't boot. The kernel config is updated with the required options to start the lxc-android container and xf86-video-hwcomposer works (tested with xfce4). My plan was to add the firmware-samsung-klte with the subpackages for the wifi blobs and a precompiled android system.img to use with libhybris, but my device just died and I'm not able to power it on (I've probably burnt the Power IC 😢)
2018-12-04 00:35:27 +00:00
$pkgname-$_commit.tar.gz::https://github.com/LineageOS/${_repository}/archive/${_commit}.tar.gz
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
$_config
linux-samsung-klte: tidy up patches and add new: (!321) * fix patch file names and reorder them properly * add patch to fix framebuffer memory allocation * add patch to fix compile warning for iptables plugin xt_connbytes * add patch to properly assign MAC address for USB RNDIS * add backport patch from upstream about O_PATH file descriptors [ci:skip-build]: already went through successfully in CI
2019-04-17 07:48:54 +00:00
0001_fix_return_address.patch
0002_gpu-msm-fix-gcc5-compile.patch
0003-Reduce-battery-and-touchscreen-log-spam.patch
0004-fix-video-argb-setting.patch
0005-mdss_fb-Always-allow-to-allocate-map-framebuffer-mem.patch
0006-Fix-xt_connbytes-compile-warning.patch
0007-usb_gadget-set-random-rndis-host-MAC-address-to-prev.patch
0008-Backport-vfs-make-O_PATH-file-descriptors-usable-for.patch
samsung-klte: backport memfd_create() syscall (!479) This brings in several patches needed to add support for a memfd_create() syscall into kernel version 3.4 from kernel version 3.17. This is required for running lxc >= 3.1.0-r1 with security patch that fixes CVE-2019-5736. In short, security issue was: in a privileged container root process could overwrite lxc-start executable by opening its file descriptor and rewriting executable contents. This is where memfd comes to help: you can create an in-memory file, copy your executable there, and place a set of SEALS to protect it from modifying at a deep level. Then you fexecve() that fd and you're safe. For example, pulseaudio also can benefit from having memfd_create() implemented. This backports the following commits from upstream linux: - dd37978c50bc8b354e5c4633f69387f16572fdac: cache the value of file_inode() in struct file commit from linux-3.10 to have an f_inode member inside struct file and a helper function file_inode() that is used in some of the following commits - 40e041a2c858b3caefc757e26cb85bfceae5062b shm: add sealing API from 3.17: security measure called SEALS, that you can put on memfd file to restrict operations on it - 9183df25fe7b194563db3fec6dc3202a5855839c shm: add memfd_create() syscall also from 3.17 - 503e6636b6f96056210062be703356f4253b6db9 asm-generic: add memfd_create system call to unistd.h - e57e41931134e09fc6c03c8d4eb19d516cc6e59b ARM: wire up memfd_create syscall The last two are needed to make the syscall visible/usable from userspace, one in generic context, other for ARM arch. The test program (https://github.com/minlexx/test_memfd/) was written to verify that this works. [ci:skip-build]: already built successfully in CI
2019-07-01 00:29:30 +00:00
0009-Backport-cache-the-value-of-file_inode-in-struct-file.patch
0010-Backport-shm-add-sealing-API.patch
0011-Backport-shm-add-memfd_create-syscall.patch
0012-Backport-asm-generic-add-memfd_create-system-call-to-unistd.h.patch
0013-Backport-ARM-wire-up-memfd_create-syscall.patch
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
"
samsung-klte: backport memfd_create() syscall (!479) This brings in several patches needed to add support for a memfd_create() syscall into kernel version 3.4 from kernel version 3.17. This is required for running lxc >= 3.1.0-r1 with security patch that fixes CVE-2019-5736. In short, security issue was: in a privileged container root process could overwrite lxc-start executable by opening its file descriptor and rewriting executable contents. This is where memfd comes to help: you can create an in-memory file, copy your executable there, and place a set of SEALS to protect it from modifying at a deep level. Then you fexecve() that fd and you're safe. For example, pulseaudio also can benefit from having memfd_create() implemented. This backports the following commits from upstream linux: - dd37978c50bc8b354e5c4633f69387f16572fdac: cache the value of file_inode() in struct file commit from linux-3.10 to have an f_inode member inside struct file and a helper function file_inode() that is used in some of the following commits - 40e041a2c858b3caefc757e26cb85bfceae5062b shm: add sealing API from 3.17: security measure called SEALS, that you can put on memfd file to restrict operations on it - 9183df25fe7b194563db3fec6dc3202a5855839c shm: add memfd_create() syscall also from 3.17 - 503e6636b6f96056210062be703356f4253b6db9 asm-generic: add memfd_create system call to unistd.h - e57e41931134e09fc6c03c8d4eb19d516cc6e59b ARM: wire up memfd_create syscall The last two are needed to make the syscall visible/usable from userspace, one in generic context, other for ARM arch. The test program (https://github.com/minlexx/test_memfd/) was written to verify that this works. [ci:skip-build]: already built successfully in CI
2019-07-01 00:29:30 +00:00
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
builddir="$srcdir/${_repository}-${_commit}"
prepare() {
default_prepare
linux-samsung-klte: modernize, update sources (!94) Use latest sources from LineageOS, instead of the ones from andip71. The APKBUILD is modernized to use the devicepkg-dev but unfortunately compiling with gcc8 it doesn't boot. The kernel config is updated with the required options to start the lxc-android container and xf86-video-hwcomposer works (tested with xfce4). My plan was to add the firmware-samsung-klte with the subpackages for the wifi blobs and a precompiled android system.img to use with libhybris, but my device just died and I'm not able to power it on (I've probably burnt the Power IC 😢)
2018-12-04 00:35:27 +00:00
downstreamkernel_prepare "$srcdir" "$builddir" "$_config" "$_carch" "$HOSTCC"
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
}
build() {
unset LDFLAGS
make ARCH="$_carch" CC="${CC:-gcc}" \
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS"
# Generate master DTB
dtbTool -s 2048 -p "scripts/dtc/" -o "arch/arm/boot/dt.img" "arch/arm/boot/"
}
package() {
# kernel.release
install -D "$builddir/include/config/kernel.release" \
"$pkgdir/usr/share/kernel/$_flavor/kernel.release"
# zImage (find the right one)
cd "$builddir/arch/$_carch/boot"
_target="$pkgdir/boot/vmlinuz-$_flavor"
for _zimg in zImage-dtb Image.gz-dtb *zImage Image; do
[ -e "$_zimg" ] || continue
msg "zImage found: $_zimg"
install -Dm644 "$_zimg" "$_target"
break
done
if ! [ -e "$_target" ]; then
error "Could not find zImage in $PWD!"
return 1
fi
# Master DTB
install -Dm644 "$builddir/arch/arm/boot/dt.img" \
"$pkgdir/boot/dt.img"
linux-samsung-klte: modernize, update sources (!94) Use latest sources from LineageOS, instead of the ones from andip71. The APKBUILD is modernized to use the devicepkg-dev but unfortunately compiling with gcc8 it doesn't boot. The kernel config is updated with the required options to start the lxc-android container and xf86-video-hwcomposer works (tested with xfce4). My plan was to add the firmware-samsung-klte with the subpackages for the wifi blobs and a precompiled android system.img to use with libhybris, but my device just died and I'm not able to power it on (I've probably burnt the Power IC 😢)
2018-12-04 00:35:27 +00:00
# External modules install
cd "$builddir"
make ARCH="$_carch" CC="${CC:-gcc}" \
KBUILD_BUILD_VERSION="$((pkgrel + 1 ))-postmarketOS" \
INSTALL_MOD_PATH="$pkgdir" modules_install
Add device Samsung Galaxy S5 (samsung-klte) (#1163)
2018-02-02 19:59:14 +00:00
}
samsung-klte: backport memfd_create() syscall (!479) This brings in several patches needed to add support for a memfd_create() syscall into kernel version 3.4 from kernel version 3.17. This is required for running lxc >= 3.1.0-r1 with security patch that fixes CVE-2019-5736. In short, security issue was: in a privileged container root process could overwrite lxc-start executable by opening its file descriptor and rewriting executable contents. This is where memfd comes to help: you can create an in-memory file, copy your executable there, and place a set of SEALS to protect it from modifying at a deep level. Then you fexecve() that fd and you're safe. For example, pulseaudio also can benefit from having memfd_create() implemented. This backports the following commits from upstream linux: - dd37978c50bc8b354e5c4633f69387f16572fdac: cache the value of file_inode() in struct file commit from linux-3.10 to have an f_inode member inside struct file and a helper function file_inode() that is used in some of the following commits - 40e041a2c858b3caefc757e26cb85bfceae5062b shm: add sealing API from 3.17: security measure called SEALS, that you can put on memfd file to restrict operations on it - 9183df25fe7b194563db3fec6dc3202a5855839c shm: add memfd_create() syscall also from 3.17 - 503e6636b6f96056210062be703356f4253b6db9 asm-generic: add memfd_create system call to unistd.h - e57e41931134e09fc6c03c8d4eb19d516cc6e59b ARM: wire up memfd_create syscall The last two are needed to make the syscall visible/usable from userspace, one in generic context, other for ARM arch. The test program (https://github.com/minlexx/test_memfd/) was written to verify that this works. [ci:skip-build]: already built successfully in CI
2019-07-01 00:29:30 +00:00
sha512sums="d0ccc0cde26e6cad7e2b4cffa9d92b4cd7d11e159738935d87cc044a07679e7aed891379fb0e096b12cd1ba7e1855dd72c94ec6da96ff8e936479c59b4d4eb6c linux-samsung-klte-edfd9dd9be89d15c34f653363a9a3c9108146ca0.tar.gz
linux-samsung-klte: base downstream kernel source on lineage-14.1 branch (!321) @drebrez originally based klte port on lineage-16.0 branch (Android 9), but we need compatibility with Android 7.1, so use lineage-14.1 branch. Also tidy up downstream kernel config a little bit (pass it through pmbootstrap kconfig edit, change nothing, exit with saving).
2019-04-17 07:43:26 +00:00
2e660d0ac4ffdd5f1a63660a8b61cf83e94122f15126b134a27f58b84fc5424ce4935ef43ca5bff1ec956047b77f7fb7f67e5c1ec976c67712444b370ae6373e config-samsung-klte.armv7
linux-samsung-klte: tidy up patches and add new: (!321) * fix patch file names and reorder them properly * add patch to fix framebuffer memory allocation * add patch to fix compile warning for iptables plugin xt_connbytes * add patch to properly assign MAC address for USB RNDIS * add backport patch from upstream about O_PATH file descriptors [ci:skip-build]: already went through successfully in CI
2019-04-17 07:48:54 +00:00
3b4913415bcfe0ff222969f993890c656c7e12b6ee06532bded485d5201c9855b2c87996c5b63423702b89b6b0ca214b5aceeb402571d9c5af084093c157ccb4 0001_fix_return_address.patch
0fc4b1782dfd3bd94fa9ae8ab74b19713f25e9f4a48dcf830072634f247aa3dd8847f001a3e87e9728e057657efd4ae751510e7c408d9b960c907665ca64e61f 0002_gpu-msm-fix-gcc5-compile.patch
b55fc9ab3e21bc85d66ee08d7e1cd7fdc3b236249212fbcd0055e60ed3e6cef3e4d2b8058a4b7d70c78b2bbc7a11111b55d4d82490b4e3579b8e61657806ac09 0003-Reduce-battery-and-touchscreen-log-spam.patch
a48336bbfead6ad0c84d2fce0c40a3f5530aebdff356a6835cceaf59a50a6f860d2f8027703a92927955fbb18857ba78788e010d017bf67730f069b36e96fe87 0004-fix-video-argb-setting.patch
e3a9b75de461313ee6ba0e547d7fb97d77a749a11416c44b28110673d3a6f7b01305e74f67c06c8cfea97bde5d3d0cd98a457a03a63560125f5bb84f82f116e1 0005-mdss_fb-Always-allow-to-allocate-map-framebuffer-mem.patch
6bdb3acd4a2d10d59ea16a2147735b94f17070aecebfe55fff724c03335bf1a02cc7539c9fe0a59cb944b6835135fe64956617c8b29847397b2f4df68b602063 0006-Fix-xt_connbytes-compile-warning.patch
27f890cf82027649ba742b606a87ce6a82f9685b075bb7b50bffec77221e70434ee78d118d39048350537c5ecdad208658967e492eeeb997e7f6884fa78ac696 0007-usb_gadget-set-random-rndis-host-MAC-address-to-prev.patch
samsung-klte: backport memfd_create() syscall (!479) This brings in several patches needed to add support for a memfd_create() syscall into kernel version 3.4 from kernel version 3.17. This is required for running lxc >= 3.1.0-r1 with security patch that fixes CVE-2019-5736. In short, security issue was: in a privileged container root process could overwrite lxc-start executable by opening its file descriptor and rewriting executable contents. This is where memfd comes to help: you can create an in-memory file, copy your executable there, and place a set of SEALS to protect it from modifying at a deep level. Then you fexecve() that fd and you're safe. For example, pulseaudio also can benefit from having memfd_create() implemented. This backports the following commits from upstream linux: - dd37978c50bc8b354e5c4633f69387f16572fdac: cache the value of file_inode() in struct file commit from linux-3.10 to have an f_inode member inside struct file and a helper function file_inode() that is used in some of the following commits - 40e041a2c858b3caefc757e26cb85bfceae5062b shm: add sealing API from 3.17: security measure called SEALS, that you can put on memfd file to restrict operations on it - 9183df25fe7b194563db3fec6dc3202a5855839c shm: add memfd_create() syscall also from 3.17 - 503e6636b6f96056210062be703356f4253b6db9 asm-generic: add memfd_create system call to unistd.h - e57e41931134e09fc6c03c8d4eb19d516cc6e59b ARM: wire up memfd_create syscall The last two are needed to make the syscall visible/usable from userspace, one in generic context, other for ARM arch. The test program (https://github.com/minlexx/test_memfd/) was written to verify that this works. [ci:skip-build]: already built successfully in CI
2019-07-01 00:29:30 +00:00
a2bd1b925ba0e1ba0a68dcb134604abbaddf456426a468662d77bc02f0d09d4d07c0c89001c0973e690e1f7eb9c1cfdd37c2d99ed4cc62f3398582d6b51a7013 0008-Backport-vfs-make-O_PATH-file-descriptors-usable-for.patch
47894281412f1c9d4266812f089c3f2434c1636d74245f392d4b0b7532096f8f5bd698715d9e10c7be6c70892af45de2d2c657bd276332442890b94e1159f8f8 0009-Backport-cache-the-value-of-file_inode-in-struct-file.patch
54d71b32b456a3d0abd090c820214240688484f4cadbbde0304bf3cb5246b1aa3893dd85736dc5db2f3d6f9de1f5e84a1adcf5a661a62586452f1002360dc691 0010-Backport-shm-add-sealing-API.patch
c62d67a5fb28082e86a585b4c64891525db640ce694445f0fb19e67fb8dcd9ccbfbcb6fba8692964fac8b026c39cfa558cf316a7e22828ac13f58f5b9938ef09 0011-Backport-shm-add-memfd_create-syscall.patch
cbf6e4bdf53b02f897923d0f6eea5320acc6760c3f3ed762e69928ced7e3b6f2a5355df4a2fccf560f010a4a1968e7ae1a3f62c2db299857d6bcc9715d932822 0012-Backport-asm-generic-add-memfd_create-system-call-to-unistd.h.patch
2f256f6ec9fa7b240dd1f9417622bfd5a8ca4a9ea12cd2ef171540e1425d4171122c0597fe12af913ef60979ef9a3dce8a6c1c523c91020cb9481560901cc92b 0013-Backport-ARM-wire-up-memfd_create-syscall.patch"
Reference in a new issue Copy permalink