Tags give the ability to mark specific points in history as being important
-
locking-urgent-2020-08-10
0cd39f46 · ·A set of locking fixes and updates: - Untangle the header spaghetti which causes build failures in various situations caused by the lockdep additions to seqcount to validate that the write side critical sections are non-preemptible. - The seqcount associated lock debug addons which were blocked by the above fallout. seqcount writers contrary to seqlock writers must be externally serialized, which usually happens via locking - except for strict per CPU seqcounts. As the lock is not part of the seqcount, lockdep cannot validate that the lock is held. This new debug mechanism adds the concept of associated locks. sequence count has now lock type variants and corresponding initializers which take a pointer to the associated lock used for writer serialization. If lockdep is enabled the pointer is stored and write_seqcount_begin() has a lockdep assertion to validate that the lock is held. Aside of the type and the initializer no other code changes are required at the seqcount usage sites. The rest of the seqcount API is unchanged and determines the type at compile time with the help of _Generic which is possible now that the minimal GCC version has been moved up. Adding this lockdep coverage unearthed a handful of seqcount bugs which have been addressed already independent of this. While generaly useful this comes with a Trojan Horse twist: On RT kernels the write side critical section can become preemtible if the writers are serialized by an associated lock, which leads to the well known reader preempts writer livelock. RT prevents this by storing the associated lock pointer independent of lockdep in the seqcount and changing the reader side to block on the lock when a reader detects that a writer is in the write side critical section. - Conversion of seqcount usage sites to associated types and initializers. -
xfs-5.9-merge-8
96cf2a2c · ·Fixes for 5.9-rc1: - Fix duplicated words in comments. - Fix an ubsan complaint about null pointer arithmetic.
-
pm-5.9-rc1-2
0873ad92 · ·More power management updates for 5.9-rc1 - Add adaptive voltage scaling (AVS) support to the brcmstb cpufreq driver and clean it up (Florian Fainelli, Markus Mayer). - Add a new Tegra cpufreq driver and clean up the existing one (Jon Hunter, Sumit Gupta). - Add bandwidth level support to the Qcom cpufreq driver along with OPP changes (Sibi Sankar). - Clean up the sti, cpufreq-dt, ap806, CPPC cpufreq drivers (Viresh Kumar, Lee Jones, Ivan Kokshaysky, Sven Auhagen, Xin Hao). - Make schedutil the default governor for ARM (Valentin Schneider). - Fix dependency issues for the imx cpufreq driver (Walter Lozano). - Clean up cached_resolved_idx handlihng in the cpufreq core (Viresh Kumar). - Fix the intel_pstate driver to use the correct maximum frequency value when MSR_TURBO_RATIO_LIMIT is 0 (Srinivas Pandruvada). - Provide kenrneldoc comments for multiple runtime PM helpers and improve the pm_runtime_get_if_active() kerneldoc (Rafael Wysocki).
-
-
ASB-2020-08-05_12-5.4
750930c2 · ·https://source.android.com/security/bulletin/2020-08-01 CVE-2020-0255 CVE-2020-12464 CVE-2019-16746
-
ASB-2020-08-05_11-5.4
fcb0d3ef · ·https://source.android.com/security/bulletin/2020-08-01 CVE-2020-0255 CVE-2020-12464 CVE-2019-16746
-
ASB-2020-08-05_mainline
15415a6a · ·https://source.android.com/security/bulletin/2020-08-01 CVE-2020-0255 CVE-2020-12464 CVE-2019-16746
-
ASB-2020-08-05_4.19-q-release
613d22a7 · ·https://source.android.com/security/bulletin/2020-08-01 CVE-2020-0255 CVE-2020-12464 CVE-2019-16746
-
ASB-2020-08-05_4.19-q
09b5b6fc · ·https://source.android.com/security/bulletin/2020-08-01 CVE-2020-0255 CVE-2020-12464 CVE-2019-16746
-
ASB-2020-08-05_4.19-stable
a5218b36 · ·https://source.android.com/security/bulletin/2020-08-01 CVE-2020-0255 CVE-2020-12464 CVE-2019-16746
-
ASB-2020-08-05_4.14-q-release
b4656b9b · ·https://source.android.com/security/bulletin/2020-08-01 CVE-2020-0255 CVE-2020-12464 CVE-2019-16746