Tags give the ability to mark specific points in history as being important
-
x86-urgent-2020-10-11
0c768983 · ·Two fixes: - Fix a (hopefully final) IRQ state tracking bug vs. MCE handling - Fix a documentation link Signed-off-by: Ingo Molnar <mingo@kernel.org>
-
perf-urgent-2020-10-11
6d6b8b9f · ·Fix a bug that can cause a lockup if a CPU is offline. Signed-off-by: Ingo Molnar <mingo@kernel.org>
-
locking-urgent-2020-10-11
baffd723 · ·A handful of last minute lockdep fixes: - Revert a bad commit - Fix a recursion related false positive - Fix ->usage_traces[] printing mishap Signed-off-by: Ingo Molnar <mingo@kernel.org>
-
-
-
-
-
-
xfs-5.10-merge-3
e5b23740 · ·Recalling the first round of new code for 5.10, in which we added: - New feature: Widen inode timestamps and quota grace expiration timestamps to support dates through the year 2486. - New feature: storing inode btree counts in the AGI to speed up certain mount time per-AG block reservation operatoins and add a little more metadata redundancy. For the second round of new code for 5.10: - Deprecate the V4 filesystem format, some disused mount options, and some legacy sysctl knobs now that we can support dates into the 25th century. Note that removal of V4 support will not happen until the early 2030s. - Fix some probles with inode realtime flag propagation. - Fix some buffer handling issues when growing a rt filesystem. - Fix a problem where a BMAP_REMAP unmap call would free rt extents even though the purpose of BMAP_REMAP is to avoid freeing the blocks. - Strengthen the dabtree online scrubber to check hash values on child dabtree blocks. - Actually log new intent items created as part of recovering log intent items. - Fix a bug where quotas weren't attached to an inode undergoing bmap intent item recovery. - Fix a buffer overrun problem with specially crafted log buffer headers. - Various cleanups to type usage and slightly inaccurate comments. - More cleanups to the xattr, log, and quota code. - Don't run the (slower) shared-rmap operations on attr fork mappings. - Fix a bug where we failed to check the LSN of finobt blocks during replay and could therefore overwrite newer data with older data. - Clean up the ugly nested transaction mess that log recovery uses to stage intent item recovery in the correct order by creating a proper data structure to capture recovered chains. - Use the capture structure to resume intent item chains with the same log space and block reservations as when they were captured. - Fix a UAF bug in bmap intent item recovery where we failed to maintain our reference to the incore inode if the bmap operation needed to relog itself to continue. - Rearrange the defer ops mechanism to finish newly created subtasks of a parent task before moving on to the next parent task. - Automatically relog intent items in deferred ops chains if doing so would help us avoid pinning the log tail. This will help fix some log scaling problems now and will facilitate atomic file updates later. - Fix a deadlock in the GETFSMAP implementation by using an internal memory buffer to reduce indirect calls and copies to userspace, thereby improving its performance by ~20%.
-
x86_pasid_for_5.10
7f5933f8 · ·Initial support for sharing virtual addresses between the CPU and devices which doesn't need pinning of pages for DMA anymore. Add support for the command submission to devices using new x86 instructions like ENQCMD{,S} and MOVDIR64B. In addition, add support for process address space identifiers (PASIDs) which are referenced by those command submission instructions along with the handling of the PASID state on context switch as another extended state. Work by Fenghua Yu, Ashok Raj, Yu-cheng Yu and Dave Jiang. -
ASB-2020-10-05_mainline
4eaae9ae · ·https://source.android.com/security/bulletin/2020-10-01 Fix for CVE-2020-0423 not yet public.
-
ASB-2020-10-05_12-5.4
9d0d6300 · ·https://source.android.com/security/bulletin/2020-10-01 Fix for CVE-2020-0423 not yet public.
-
ASB-2020-10-05_11-5.4
2ea974a0 · ·https://source.android.com/security/bulletin/2020-10-01 Fix for CVE-2020-0423 not yet public.
-
ASB-2020-10-05_4.19-q-release
5811ca14 · ·https://source.android.com/security/bulletin/2020-10-01 Fix for CVE-2020-0423 not yet public.
-
ASB-2020-10-05_4.19-q
a34f7b1d · ·https://source.android.com/security/bulletin/2020-10-01 Fix for CVE-2020-0423 not yet public.
-
ASB-2020-10-05_4.19-stable
141de28f · ·https://source.android.com/security/bulletin/2020-10-01 Fix for CVE-2020-0423 not yet public.