Tags give the ability to mark specific points in history as being important
-
ASB-2018-08-05_4.4-p
a38145ab · ·https://source.android.com/security/bulletin/2018-08-01 CVE-2017-18249* CVE-2018-9465 CVE-2018-9439 CVE-2018-1068 * currently no 4.4 backports exist for CVE-2017-18249 on android-4.4 release branches. This affects only devices using f2fs running 4.4 kernels.
-
ASB-2018-08-05_4.4-o
9c23e9b1 · ·https://source.android.com/security/bulletin/2018-08-01 CVE-2017-18249* CVE-2018-9465 CVE-2018-9439 CVE-2018-1068 * currently no 4.4 backports exist for CVE-2017-18249 on android-4.4 release branches. This affects only devices using f2fs running 4.4 kernels.
-
ASB-2018-08-05_4.4-n
bb43173c · ·https://source.android.com/security/bulletin/2018-08-01 CVE-2017-18249* CVE-2018-9465 CVE-2018-9439 CVE-2018-1068 * currently no 4.4 backports exist for CVE-2017-18249 on android-4.4 release branches. This affects only devices using f2fs running 4.4 kernels.
-
ASB-2018-08-05_4.4
13962260 · ·https://source.android.com/security/bulletin/2018-08-01 CVE-2017-18249* CVE-2018-9465 CVE-2018-9439 CVE-2018-1068 * currently no 4.4 backports exist for CVE-2017-18249 on android-4.4 release branches. This affects only devices using f2fs running 4.4 kernels.
-
ASB-2018-08-05_3.18-o-mr1
949c2be5 · ·https://source.android.com/security/bulletin/2018-08-01 CVE-2017-18249* CVE-2018-9465 CVE-2018-9439 CVE-2018-1068 * currently no 4.4 backports exist for CVE-2017-18249 on android-4.4 release branches. This affects only devices using f2fs running 4.4 kernels.
-
ASB-2018-08-05_3.18-o-release
965d70b5 · ·https://source.android.com/security/bulletin/2018-08-01 CVE-2017-18249* CVE-2018-9465 CVE-2018-9439 CVE-2018-1068 * currently no 4.4 backports exist for CVE-2017-18249 on android-4.4 release branches. This affects only devices using f2fs running 4.4 kernels.
-
ASB-2018-08-05_3.18-n-release
c5b4955e · ·https://source.android.com/security/bulletin/2018-08-01 CVE-2017-18249* CVE-2018-9465 CVE-2018-9439 CVE-2018-1068 * currently no 4.4 backports exist for CVE-2017-18249 on android-4.4 release branches. This affects only devices using f2fs running 4.4 kernels.
-
ASB-2018-08-05_3.18
0d4b8de1 · ·https://source.android.com/security/bulletin/2018-08-01 CVE-2017-18249* CVE-2018-9465 CVE-2018-9439 CVE-2018-1068 * currently no 4.4 backports exist for CVE-2017-18249 on android-4.4 release branches. This affects only devices using f2fs running 4.4 kernels.
-
-
-
-
drm-intel-next-fixes-2018-08-06
3237c0db · ·- Fix gvt compilation broken on a silent conflict on fixes vs next merge - Fix runtime PM for LPE audio - Revert on ICL workaround - Interactive RPS mode - Fix for PSR sink status report
-
gpio-v4.18-3
ca876c74 · ·GPIO fixes for v4.18: This is a single fix affecting X86 ACPI, and as such pretty important. It is going to stable as well and have all the high-notch x86 platform developers agreeing on it.
-
-
-
-
-
-
iomap-4.19-merge-1
806a1477 · ·Changes for 4.19: - Add shared iomap infrastructure to handle page cache reads and writeback without buffer heads (xfs). - Add inline data support (gfs2).
-
xfs-4.19-merge-4
a0e336ba · ·Changes for 4.19: - Use extent maps to track pagecache page status instead of bufferhead state. - Refactor pagecache read and write paths to use the new iomap library functions, which enable us to drop the old bufferhead code for pagesize == blocksize filesystems. - Set up parallel per-block-per-page metadata to track subpage information that was tracked by buffer heads, which enables us to drop the old bufferhead code for pagesize > blocksize filesystems. - Tie a deferred ops control structure to a transaction so that we can take advantage of an upper-level dfops without having to plumb pointer passing through the code. - Refactor the deferred ops code to track deferred ops as part of the transaction structure (instead of as a separate data structure) so that we can simplify the scoping rules around defer_ops. - Refactor twisty delwri buffer submission code to avoid deadlocks. - Shorten and fix indenting problems in the scrub code. - Detect obviously bad summary counts at mount and fix them. - Directly associate deferred ops control structure with a transaction so that callers no longer have to manage it themselves. - Remove a couple of IRIX-era inode macros. - Remove the long-deprecated 'barrier' and 'nobarrier' mount options. - Clean up the inode fork structure a bit. - Check for bad fs summary counter values in the superblock. - Reduce COW fork lookups during writeback. - Refactor the deferred ops control structures into the transaction structure, thereby eliminating the need for transaction users to handle the deferred ops as a separate data structure. - Various fixes and cleanups.