Linux Kernel
The mainline Linux kernel.
www.kernel.org
Most Popular This Year
- tpm: Allow system suspend to continue when TPM suspend fails
Jason A. Donenfeld: TPM 1 is sometimes broken across system suspends, due to races or locking issues or something else that haven't been diagnosed or fixed yet, most likely having to do with concurrent reads from the TPM's hardware random number generator driver. - ITER_PIPE: cache the type of last buffer
Al Viro: We often need to find whether the last buffer is anon or not, and currently it's rather clumsy: check if ->iov_offset is non-zero (i.e. - kunit: make kunit_test_timeout compatible with comment
Peng Liu: In function kunit_test_timeout, it is declared "300 * MSEC_PER_SEC" represent 5min. - certs: make system keyring depend on x509 parser
Adam Borowski: This code requires x509_load_certificate_list() to be built-in. - mm: handle uninitialized numa nodes gracefully
Michal Hocko: We have had several reports [1][2][3] that page allocator blows up when an allocation from a possible node is requested. - mm: invalidate hwpoison page cache page in fault path
Rik van Riel: Sometimes the page offlining code can leave behind a hwpoisoned clean page cache page. - mm: hugetlb: free the 2nd vmemmap page associated with each HugeTLB page
Muchun Song: Patch series "Free the 2nd vmemmap page associated with each HugeTLB page", v7.
This series can minimize the overhead of struct page for 2MB HugeTLB pages significantly. - mm: sparsemem: use page table lock to protect kernel pmd operations
Muchun Song: The init_mm.page_table_lock is used to protect kernel page tables, we can use it to serialize splitting vmemmap PMD mappings instead of mmap write lock, which can increase the concurrency of vmemmap_remap_free().
Actually, It increase the concurrency between allocations of HugeTLB pages. - memcg: unify force charging conditions
Shakeel Butt: Currently the kernel force charges the allocations which have __GFP_HIGH flag without triggering the memory reclaim. - firmware_loader: enable XZ by default if compressed support is enabled
Linus Torvalds: Commit 23cfbc6ec44e ("firmware: Add the support for ZSTD-compressed firmware files") added support for ZSTD compression, but in the process also made the previously default XZ compression a config option.
That means that anybody who upgrades their kernel and does a
make oldconfig
to update their configuration, will end up without the XZ compression that the configuration used to have.
Add the 'default y' to make sure this doesn't happen.
The whole compression question should probably be improved upon, since it is now possible to "enable" compression in the kernel config but not enable any actual compression algorithm, which makes it all very useless.