Tags give the ability to mark specific points in history as being important
-
ASB-2018-11-05_4.4-o-release
f9d21e72 · ·https://source.android.com/security/bulletin/2018-11-01 No kernel security patches for ASB-2018-11, however there were some from previous ASBs that are now upstream and in android common kernels CVE-2018-9363 from ASB-2018-06 CVE-2017-0749 from ASB-2017-08 CVE-2017-0627 from ASB-2017-05 CVE-2017-0564 from ASB-2017-04 CVE-2017-13293 from ASB-2018-04
-
ASB-2018-11-05_4.4-n-release
93203550 · ·https://source.android.com/security/bulletin/2018-11-01 No kernel security patches for ASB-2018-11, however there were some from previous ASBs that are now upstream and in android common kernels CVE-2018-9363 from ASB-2018-06 CVE-2017-0749 from ASB-2017-08 CVE-2017-0627 from ASB-2017-05 CVE-2017-0564 from ASB-2017-04 CVE-2017-13293 from ASB-2018-04
-
ASB-2018-11-05_4.4-p
0c50cd92 · ·https://source.android.com/security/bulletin/2018-11-01 No kernel security patches for ASB-2018-11, however there were some from previous ASBs that are now upstream and in android common kernels CVE-2018-9363 from ASB-2018-06 CVE-2017-0749 from ASB-2017-08 CVE-2017-0627 from ASB-2017-05 CVE-2017-0564 from ASB-2017-04 CVE-2017-13293 from ASB-2018-04
-
ASB-2018-11-05_4.4-o
2adf9ae9 · ·https://source.android.com/security/bulletin/2018-11-01 No kernel security patches for ASB-2018-11, however there were some from previous ASBs that are now upstream and in android common kernels CVE-2018-9363 from ASB-2018-06 CVE-2017-0749 from ASB-2017-08 CVE-2017-0627 from ASB-2017-05 CVE-2017-0564 from ASB-2017-04 CVE-2017-13293 from ASB-2018-04
-
ASB-2018-11-05_4.4-n
67099b53 · ·https://source.android.com/security/bulletin/2018-11-01 No kernel security patches for ASB-2018-11, however there were some from previous ASBs that are now upstream and in android common kernels CVE-2018-9363 from ASB-2018-06 CVE-2017-0749 from ASB-2017-08 CVE-2017-0627 from ASB-2017-05 CVE-2017-0564 from ASB-2017-04 CVE-2017-13293 from ASB-2018-04
-
ASB-2018-11-05_4.4
3411c22e · ·https://source.android.com/security/bulletin/2018-11-01 No kernel security patches for ASB-2018-11, however there were some from previous ASBs that are now upstream and in android common kernels CVE-2018-9363 from ASB-2018-06 CVE-2017-0749 from ASB-2017-08 CVE-2017-0627 from ASB-2017-05 CVE-2017-0564 from ASB-2017-04 CVE-2017-13293 from ASB-2018-04
-
ASB-2018-11-05_3.18-o-mr1
e5daca71 · ·https://source.android.com/security/bulletin/2018-11-01 No kernel security patches for ASB-2018-11, however there were some from previous ASBs that are now upstream and in android common kernels CVE-2018-9363 from ASB-2018-06 CVE-2017-0749 from ASB-2017-08 CVE-2017-0627 from ASB-2017-05 CVE-2017-0564 from ASB-2017-04 CVE-2017-13293 from ASB-2018-04
-
ASB-2018-11-05_3.18-o-release
fedc3f35 · ·https://source.android.com/security/bulletin/2018-11-01 No kernel security patches for ASB-2018-11, however there were some from previous ASBs that are now upstream and in android common kernels CVE-2018-9363 from ASB-2018-06 CVE-2017-0749 from ASB-2017-08 CVE-2017-0627 from ASB-2017-05 CVE-2017-0564 from ASB-2017-04 CVE-2017-13293 from ASB-2018-04
-
ASB-2018-11-05_3.18-n-release
60615ded · ·https://source.android.com/security/bulletin/2018-11-01 No kernel security patches for ASB-2018-11, however there were some from previous ASBs that are now upstream and in android common kernels CVE-2018-9363 from ASB-2018-06 CVE-2017-0749 from ASB-2017-08 CVE-2017-0627 from ASB-2017-05 CVE-2017-0564 from ASB-2017-04 CVE-2017-13293 from ASB-2018-04
-
ASB-2018-11-05_3.18
4623ec41 · ·https://source.android.com/security/bulletin/2018-11-01 No kernel security patches for ASB-2018-11, however there were some from previous ASBs that are now upstream and in android common kernels CVE-2018-9363 from ASB-2018-06 CVE-2017-0749 from ASB-2017-08 CVE-2017-0627 from ASB-2017-05 CVE-2017-0564 from ASB-2017-04 CVE-2017-13293 from ASB-2018-04
-
xfs-4.20-merge-2
bf4a1fcf · ·vfs: rework data cloning infrastructure Rework the vfs_clone_file_range and vfs_dedupe_file_range infrastructure to use a common .remap_file_range method and supply generic bounds and sanity checking functions that are shared with the data write path. The current VFS infrastructure has problems with rlimit, LFS file sizes, file time stamps, maximum filesystem file sizes, stripping setuid bits, etc and so they are addressed in these commits. We also introduce the ability for the ->remap_file_range methods to return short clones so that clones for vfs_copy_file_range() don't get rejected if the entire range can't be cloned. It also allows filesystems to sliently skip deduplication of partial EOF blocks if they are not capable of doing so without requiring errors to be thrown to userspace. All existing filesystems are converted to user the new .remap_file_range method, and both XFS and ocfs2 are modified to make use of the new generic checking infrastructure.
-
pm-4.20-rc1-2
c4ac6889 · ·More power management updates for 4.20-rc1 - Fix build regression in the intel_pstate driver that doesn't build without CONFIG_ACPI after recent changes (Dominik Brodowski). - One of the heuristics in the menu cpuidle governor is based on a function returning 0 most of the time, so drop it and clean up the scheduler code related to it (Daniel Lezcano). - Prevent the arm_big_little cpufreq driver from being used on ARM64 which is not suitable for it and drop the arm_big_little_dt driver that is not used any more (Sudeep Holla). - Prevent the hung task watchdog from triggering during resume from system-wide sleep states by disabling it before freezing tasks and enabling it again after they have been thawed (Vitaly Kuznetsov).