Tags give the ability to mark specific points in history as being important
-
ASB-2019-11-05_4.9-q
dc734d73 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.9-p-release
4528bd05 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.9-o-mr1
d5f4847a · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.9-o-release
f3c4f4ed · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.9-p
5fe01252 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.9-o
9ce2cd83 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.4-p-release
0b137c48 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.4-o-mr1
631f238a · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.4-o-release
82bd53b8 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.4-n-release
0ce83621 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.4-p
766d0c0c · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.4-o
b50355fe · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.4-n
3642bca0 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_3.18-o-mr1
b729bd15 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_3.18-o-release
4bde8dac · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_3.18-n-release
71c88531 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_3.18
c53307ea · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
xfs-5.5-merge-8
c34d570d · ·New code for 5.5: - Fill out the build string - Prevent inode fork extent count overflows - Refactor the allocator to reduce long tail latency - Rework incore log locking a little to reduce spinning - Break up the xfs_iomap_begin functions into smaller more cohesive parts - Fix allocation alignment being dropped too early when the allocation request is for more blocks than an AG is large - Other small cleanups - Clean up file buftarg retrieval helpers - Hoist the resvsp and unresvsp ioctls to the vfs - Remove the undocumented biosize mount option, since it has never been mentioned as existing or supported on linux - Clean up some of the mount option printing and parsing - Enhance attr leaf verifier to check block structure - Check dirent and attr names for invalid characters before passing them to the vfs - Refactor open-coded bmbt walking - Fix a few places where we return EIO instead of EFSCORRUPTED after failing metadata sanity checks - Fix a synchronization problem between fallocate and aio dio corrupting the file length - Clean up various loose ends in the iomap and bmap code
-