August 2022 - Linux-stable-mirror

Hi

by Jessica Daniel

-- Hello Dear, Did you receive my mail thanks??

2 years, 10 months

1
0
0 0

+ bootmem-remove-the-vmemmap-pages-from-kmemleak-in-put_page_bootmem.patch added to mm-hotfixes-unstable branch

by Andrew Morton

The patch titled Subject: bootmem: remove the vmemmap pages from kmemleak in put_page_bootmem has been added to the -mm mm-hotfixes-unstable branch. Its filename is bootmem-remove-the-vmemmap-pages-from-kmemleak-in-put_page_bootmem.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patche… This patch will later appear in the mm-hotfixes-unstable branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next via the mm-everything branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm and is updated there every 2-3 working days ------------------------------------------------------ From: Liu Shixin <liushixin2(a)huawei.com> Subject: bootmem: remove the vmemmap pages from kmemleak in put_page_bootmem Date: Fri, 19 Aug 2022 17:40:05 +0800 The vmemmap pages is marked by kmemleak when allocated from memblock. Remove it from kmemleak when freeing the page. Otherwise, when we reuse the page, kmemleak may report such an error and then stop working. kmemleak: Cannot insert 0xffff98fb6eab3d40 into the object search tree (overlaps existing) kmemleak: Kernel memory leak detector disabled kmemleak: Object 0xffff98fb6be00000 (size 335544320): kmemleak: comm "swapper", pid 0, jiffies 4294892296 kmemleak: min_count = 0 kmemleak: count = 0 kmemleak: flags = 0x1 kmemleak: checksum = 0 kmemleak: backtrace: Link: https://lkml.kernel.org/r/20220819094005.2928241-1-liushixin2@huawei.com Fixes: f41f2ed43ca5 (mm: hugetlb: free the vmemmap pages associated with each HugeTLB page) Signed-off-by: Liu Shixin <liushixin2(a)huawei.com> Reviewed-by: Muchun Song <songmuchun(a)bytedance.com> Cc: Matthew Wilcox <willy(a)infradead.org> Cc: Mike Kravetz <mike.kravetz(a)oracle.com> Cc: Oscar Salvador <osalvador(a)suse.de> Cc: <stable(a)vger.kernel.org> Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org> --- mm/bootmem_info.c | 2 ++ 1 file changed, 2 insertions(+) --- a/mm/bootmem_info.c~bootmem-remove-the-vmemmap-pages-from-kmemleak-in-put_page_bootmem +++ a/mm/bootmem_info.c @@ -12,6 +12,7 @@ #include <linux/memblock.h> #include <linux/bootmem_info.h> #include <linux/memory_hotplug.h> +#include <linux/kmemleak.h> void get_page_bootmem(unsigned long info, struct page *page, unsigned long type) { @@ -33,6 +34,7 @@ void put_page_bootmem(struct page *page) ClearPagePrivate(page); set_page_private(page, 0); INIT_LIST_HEAD(&page->lru); + kmemleak_free_part(page_to_virt(page), PAGE_SIZE); free_reserved_page(page); } } _ Patches currently in -mm which might be from liushixin2(a)huawei.com are bootmem-remove-the-vmemmap-pages-from-kmemleak-in-free_bootmem_page.patch bootmem-remove-the-vmemmap-pages-from-kmemleak-in-put_page_bootmem.patch

2 years, 10 months

1
0
0 0

[PATCH 5.10 0/1] qrtr: Convert qrtr_ports from IDR to XArray

by Stanislav Goriainov

Syzkaller reports using smp_processor_id() in preemptible code at radix_tree_node_alloc() in 5.10 stable releases. The problem has been fixed by the following patch which can be cleanly applied to the 5.10 branch. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

2 years, 10 months

4
5
0 0

[PATCH 5.10 0/1] ath9k: fix use-after-free in ath9k_hif_usb_rx_cb

by Dragos-Marian Panait

The following commit is needed to fix CVE-2022-1679: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… Pavel Skripkin (1): ath9k: fix use-after-free in ath9k_hif_usb_rx_cb drivers/net/wireless/ath/ath9k/htc.h | 10 +++++----- drivers/net/wireless/ath/ath9k/htc_drv_init.c | 3 ++- 2 files changed, 7 insertions(+), 6 deletions(-) base-commit: 6eae1503ddf94b4c3581092d566b17ed12d80f20 -- 2.37.1

2 years, 10 months

2
4
0 0

[RFC PATCH 0/3] kallsyms: add option to include relative filepaths into kallsyms

by Alexander Lobakin

This is an early RFC to not rewrite stuff one more time later on if the implementation is not acceptable or any major design changes are required. For the TODO list, please scroll to the end. Make kallsyms independent of symbols positions in vmlinux (or module) by including relative filepath in each symbol's kallsyms value. I.e. dev_gro_receive -> net/core/gro.c:dev_gro_receive For the implementation details, please look at the patch 3/3. Patch 2/3 is just a stub, I plan to reuse kallsyms enhancement from the Rust series for it. Patch 1/3 is a fix of one modpost macro straight from 2.6.12-rc2. A nice side effect is that it's now easier to debug the kernel, as stacktraces will now tell every call's place in the file tree: [ 0.733191] Call Trace: [ 0.733668] <TASK> [ 0.733980] lib/dump_stack.c:dump_stack_lvl+0x48/0x68 [ 0.734689] kernel/panic.c:panic+0xf8/0x2ae [ 0.735291] init/do_mounts.c:mount_block_root+0x143/0x1ea [ 0.736046] init/do_mounts.c:prepare_namespace+0x13f/0x16e [ 0.736798] init/main.c:kernel_init_freeable+0x240/0x24f [ 0.737549] ? init/main.c:rest_init+0xc0/0xc0 [ 0.738171] init/main.c:kernel_init+0x1a/0x140 [ 0.738765] arch/x86/entry/entry_64.S:ret_from_fork+0x1f/0x30 [ 0.739529] </TASK> Here are some stats: Despite running a small utility on each object file and a script on each built-in.a plus one at the kallsyms generation process, it adds only 3 seconds to the whole clean build time: make -j$(($(nproc) + 1)) all compile_commands.json 19071.12s user 3481.97s system 4587% cpu 8:11.64 total make -j$(($(nproc) + 1)) all compile_commands.json 19202.88s user 3598.80s system 4607% cpu 8:14.85 total Compressed kallsyms become bigger by 1.4 Mbytes on x86_64 standard distroconfig - 60% of the kallsyms and 2.4% of the decompressed vmlinux in the memory: ffffffff8259ab30 D kallsyms_offsets ffffffff82624ed0 D kallsyms_relative_base ffffffff82624ed8 D kallsyms_num_syms ffffffff82624ee0 D kallsyms_names ffffffff827e9c68 D kallsyms_markers ffffffff827ea510 D kallsyms_token_table ffffffff827ea8c0 D kallsyms_token_index ffffffff827eaac0 d .LC1 -> ffffffff8259ac30 D kallsyms_offsets ffffffff82624fb8 D kallsyms_relative_base ffffffff82624fc0 D kallsyms_num_syms ffffffff82624fc8 D kallsyms_names ffffffff8294de50 D kallsyms_markers ffffffff8294e6f8 D kallsyms_token_table ffffffff8294eac8 D kallsyms_token_index ffffffff8294ecc8 d .LC1 TODO: * ELF rel and MIPS relocation support (only rela currently, just to test on x86_64); * modules support. Currently, the kernel reuses standard ELF strtab for module kallsyms. My plan is to create a new section which will have the same symbol order as symtab, but point to new complete strings with filepaths, and use this section solely for kallsyms (leaving symtab alone); * LTO support (now relies on that object files are ELFs); * the actual kallsyms/livepatching/probes code which will use filepaths instead of indexes/positions. Have fun! Alexander Lobakin (3): modpost: fix TO_NATIVE() with expressions and consts [STUB] increase kallsyms length limit kallsyms: add option to include relative filepaths into kallsyms .gitignore | 1 + Makefile | 2 +- include/linux/kallsyms.h | 2 +- init/Kconfig | 26 ++- kernel/livepatch/core.c | 4 +- scripts/Makefile.build | 7 +- scripts/Makefile.lib | 10 +- scripts/Makefile.modfinal | 3 +- scripts/gen_sympaths.pl | 270 ++++++++++++++++++++++++++ scripts/kallsyms.c | 89 +++++++-- scripts/link-vmlinux.sh | 14 +- scripts/mod/.gitignore | 1 + scripts/mod/Makefile | 9 + scripts/mod/modpost.h | 7 +- scripts/mod/sympath.c | 385 ++++++++++++++++++++++++++++++++++++++ 15 files changed, 796 insertions(+), 34 deletions(-) create mode 100755 scripts/gen_sympaths.pl create mode 100644 scripts/mod/sympath.c -- 2.37.2

2 years, 10 months

2
17
0 0

FAILED: patch "[PATCH] arm64: kexec_file: use more system keyrings to verify kernel" failed to apply to 5.10-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 5.10-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. thanks, greg k-h ------------------ original commit in Linus's tree ------------------ From 0d519cadf75184a24313568e7f489a7fc9b1be3b Mon Sep 17 00:00:00 2001 From: Coiby Xu <coxu(a)redhat.com> Date: Thu, 14 Jul 2022 21:40:26 +0800 Subject: [PATCH] arm64: kexec_file: use more system keyrings to verify kernel image signature Currently, when loading a kernel image via the kexec_file_load() system call, arm64 can only use the .builtin_trusted_keys keyring to verify a signature whereas x86 can use three more keyrings i.e. .secondary_trusted_keys, .machine and .platform keyrings. For example, one resulting problem is kexec'ing a kernel image would be rejected with the error "Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7". This patch set enables arm64 to make use of the same keyrings as x86 to verify the signature kexec'ed kernel image. Fixes: 732b7b93d849 ("arm64: kexec_file: add kernel signature verification support") Cc: stable(a)vger.kernel.org # 105e10e2cf1c: kexec_file: drop weak attribute from functions Cc: stable(a)vger.kernel.org # 34d5960af253: kexec: clean up arch_kexec_kernel_verify_sig Cc: stable(a)vger.kernel.org # 83b7bb2d49ae: kexec, KEYS: make the code in bzImage64_verify_sig generic Acked-by: Baoquan He <bhe(a)redhat.com> Cc: kexec(a)lists.infradead.org Cc: keyrings(a)vger.kernel.org Cc: linux-security-module(a)vger.kernel.org Co-developed-by: Michal Suchanek <msuchanek(a)suse.de> Signed-off-by: Michal Suchanek <msuchanek(a)suse.de> Acked-by: Will Deacon <will(a)kernel.org> Signed-off-by: Coiby Xu <coxu(a)redhat.com> Signed-off-by: Mimi Zohar <zohar(a)linux.ibm.com> diff --git a/arch/arm64/kernel/kexec_image.c b/arch/arm64/kernel/kexec_image.c index 9ec34690e255..5ed6a585f21f 100644 --- a/arch/arm64/kernel/kexec_image.c +++ b/arch/arm64/kernel/kexec_image.c @@ -14,7 +14,6 @@ #include <linux/kexec.h> #include <linux/pe.h> #include <linux/string.h> -#include <linux/verification.h> #include <asm/byteorder.h> #include <asm/cpufeature.h> #include <asm/image.h> @@ -130,18 +129,10 @@ static void *image_load(struct kimage *image, return NULL; } -#ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG -static int image_verify_sig(const char *kernel, unsigned long kernel_len) -{ - return verify_pefile_signature(kernel, kernel_len, NULL, - VERIFYING_KEXEC_PE_SIGNATURE); -} -#endif - const struct kexec_file_ops kexec_image_ops = { .probe = image_probe, .load = image_load, #ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG - .verify_sig = image_verify_sig, + .verify_sig = kexec_kernel_verify_pe_sig, #endif };

2 years, 10 months

3
3
0 0

FAILED: patch "[PATCH] arm64: kexec_file: use more system keyrings to verify kernel" failed to apply to 5.19-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 5.19-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. thanks, greg k-h ------------------ original commit in Linus's tree ------------------ From 0d519cadf75184a24313568e7f489a7fc9b1be3b Mon Sep 17 00:00:00 2001 From: Coiby Xu <coxu(a)redhat.com> Date: Thu, 14 Jul 2022 21:40:26 +0800 Subject: [PATCH] arm64: kexec_file: use more system keyrings to verify kernel image signature Currently, when loading a kernel image via the kexec_file_load() system call, arm64 can only use the .builtin_trusted_keys keyring to verify a signature whereas x86 can use three more keyrings i.e. .secondary_trusted_keys, .machine and .platform keyrings. For example, one resulting problem is kexec'ing a kernel image would be rejected with the error "Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7". This patch set enables arm64 to make use of the same keyrings as x86 to verify the signature kexec'ed kernel image. Fixes: 732b7b93d849 ("arm64: kexec_file: add kernel signature verification support") Cc: stable(a)vger.kernel.org # 105e10e2cf1c: kexec_file: drop weak attribute from functions Cc: stable(a)vger.kernel.org # 34d5960af253: kexec: clean up arch_kexec_kernel_verify_sig Cc: stable(a)vger.kernel.org # 83b7bb2d49ae: kexec, KEYS: make the code in bzImage64_verify_sig generic Acked-by: Baoquan He <bhe(a)redhat.com> Cc: kexec(a)lists.infradead.org Cc: keyrings(a)vger.kernel.org Cc: linux-security-module(a)vger.kernel.org Co-developed-by: Michal Suchanek <msuchanek(a)suse.de> Signed-off-by: Michal Suchanek <msuchanek(a)suse.de> Acked-by: Will Deacon <will(a)kernel.org> Signed-off-by: Coiby Xu <coxu(a)redhat.com> Signed-off-by: Mimi Zohar <zohar(a)linux.ibm.com> diff --git a/arch/arm64/kernel/kexec_image.c b/arch/arm64/kernel/kexec_image.c index 9ec34690e255..5ed6a585f21f 100644 --- a/arch/arm64/kernel/kexec_image.c +++ b/arch/arm64/kernel/kexec_image.c @@ -14,7 +14,6 @@ #include <linux/kexec.h> #include <linux/pe.h> #include <linux/string.h> -#include <linux/verification.h> #include <asm/byteorder.h> #include <asm/cpufeature.h> #include <asm/image.h> @@ -130,18 +129,10 @@ static void *image_load(struct kimage *image, return NULL; } -#ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG -static int image_verify_sig(const char *kernel, unsigned long kernel_len) -{ - return verify_pefile_signature(kernel, kernel_len, NULL, - VERIFYING_KEXEC_PE_SIGNATURE); -} -#endif - const struct kexec_file_ops kexec_image_ops = { .probe = image_probe, .load = image_load, #ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG - .verify_sig = image_verify_sig, + .verify_sig = kexec_kernel_verify_pe_sig, #endif };

2 years, 10 months

5
13
0 0

FAILED: patch "[PATCH] arm64: kexec_file: use more system keyrings to verify kernel" failed to apply to 5.18-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 5.18-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. thanks, greg k-h ------------------ original commit in Linus's tree ------------------ From 0d519cadf75184a24313568e7f489a7fc9b1be3b Mon Sep 17 00:00:00 2001 From: Coiby Xu <coxu(a)redhat.com> Date: Thu, 14 Jul 2022 21:40:26 +0800 Subject: [PATCH] arm64: kexec_file: use more system keyrings to verify kernel image signature Currently, when loading a kernel image via the kexec_file_load() system call, arm64 can only use the .builtin_trusted_keys keyring to verify a signature whereas x86 can use three more keyrings i.e. .secondary_trusted_keys, .machine and .platform keyrings. For example, one resulting problem is kexec'ing a kernel image would be rejected with the error "Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7". This patch set enables arm64 to make use of the same keyrings as x86 to verify the signature kexec'ed kernel image. Fixes: 732b7b93d849 ("arm64: kexec_file: add kernel signature verification support") Cc: stable(a)vger.kernel.org # 105e10e2cf1c: kexec_file: drop weak attribute from functions Cc: stable(a)vger.kernel.org # 34d5960af253: kexec: clean up arch_kexec_kernel_verify_sig Cc: stable(a)vger.kernel.org # 83b7bb2d49ae: kexec, KEYS: make the code in bzImage64_verify_sig generic Acked-by: Baoquan He <bhe(a)redhat.com> Cc: kexec(a)lists.infradead.org Cc: keyrings(a)vger.kernel.org Cc: linux-security-module(a)vger.kernel.org Co-developed-by: Michal Suchanek <msuchanek(a)suse.de> Signed-off-by: Michal Suchanek <msuchanek(a)suse.de> Acked-by: Will Deacon <will(a)kernel.org> Signed-off-by: Coiby Xu <coxu(a)redhat.com> Signed-off-by: Mimi Zohar <zohar(a)linux.ibm.com> diff --git a/arch/arm64/kernel/kexec_image.c b/arch/arm64/kernel/kexec_image.c index 9ec34690e255..5ed6a585f21f 100644 --- a/arch/arm64/kernel/kexec_image.c +++ b/arch/arm64/kernel/kexec_image.c @@ -14,7 +14,6 @@ #include <linux/kexec.h> #include <linux/pe.h> #include <linux/string.h> -#include <linux/verification.h> #include <asm/byteorder.h> #include <asm/cpufeature.h> #include <asm/image.h> @@ -130,18 +129,10 @@ static void *image_load(struct kimage *image, return NULL; } -#ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG -static int image_verify_sig(const char *kernel, unsigned long kernel_len) -{ - return verify_pefile_signature(kernel, kernel_len, NULL, - VERIFYING_KEXEC_PE_SIGNATURE); -} -#endif - const struct kexec_file_ops kexec_image_ops = { .probe = image_probe, .load = image_load, #ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG - .verify_sig = image_verify_sig, + .verify_sig = kexec_kernel_verify_pe_sig, #endif };

2 years, 10 months

3
2
0 0

[PATCH STABLE 5.10 0/2] btrfs: raid56: backports to reduce corruption

by Qu Wenruo

This is the backport for v5.10.x stable branch. The full explananation can be found here: https://lore.kernel.org/linux-btrfs/cover.1660891713.git.wqu@suse.com/ Difference between v5.10.x and v5.15.x backports: - Naming change in btrfs_io_contrl In v5.15, we don't have the btrfs_io_contrl rename, thus only btrfs_bio. - Missing btrfs_fs_info::sectorsize_bits Since RAID56 doesn't support anything but PAGE_SIZE == sectorsize (until v5.19+), here we just use PAGE_SHIFT. Another thing related to v5.10.x testing is, there are some lockdep assert triggered related to uuid_mutex. I'm not 100% sure, but at least RAID56 code is not touching that mutex, thus I guess it's some other problems. Qu Wenruo (2): btrfs: only write the sectors in the vertical stripe which has data stripes btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() fs/btrfs/raid56.c | 74 ++++++++++++++++++++++++++++++++++++----------- 1 file changed, 57 insertions(+), 17 deletions(-) -- 2.37.1

2 years, 10 months

2
3
0 0

[PATCH 5.19 00/21] 5.19.1-rc1 review

by Greg Kroah-Hartman

This is the start of the stable review cycle for the 5.19.1 release. There are 21 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Thu, 11 Aug 2022 17:55:02 +0000. Anything received after that time might be too late. The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.19.1-rc1… or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.19.y and the diffstat can be found below. thanks, greg k-h ------------- Pseudo-Shortlog of commits: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> Linux 5.19.1-rc1 Pawan Gupta <pawan.kumar.gupta(a)linux.intel.com> x86/speculation: Add LFENCE to RSB fill sequence Daniel Sneddon <daniel.sneddon(a)linux.intel.com> x86/speculation: Add RSB VM Exit protections Ning Qiang <sohu0106(a)126.com> macintosh/adb: fix oob read in do_adb_query() function Hilda Wu <hildawu(a)realtek.com> Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586 Hilda Wu <hildawu(a)realtek.com> Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587 Hilda Wu <hildawu(a)realtek.com> Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558 Hilda Wu <hildawu(a)realtek.com> Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675 Hilda Wu <hildawu(a)realtek.com> Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007 Aaron Ma <aaron.ma(a)canonical.com> Bluetooth: btusb: Add support of IMC Networks PID 0x3568 Ahmad Fatoum <a.fatoum(a)pengutronix.de> dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding Hakan Jansson <hakan.jansson(a)infineon.com> Bluetooth: hci_bcm: Add DT compatible for CYW55572 Ahmad Fatoum <a.fatoum(a)pengutronix.de> Bluetooth: hci_bcm: Add BCM4349B1 variant Sai Teja Aluvala <quic_saluvala(a)quicinc.com> Bluetooth: hci_qca: Return wakeup for qca_wakeup Peter Collingbourne <pcc(a)google.com> arm64: set UXN on swapper page tables Andrew Lunn <andrew(a)lunn.ch> ata: sata_mv: Fixes expected number of resources now IRQs are gone GUO Zihua <guozihua(a)huawei.com> crypto: arm64/poly1305 - fix a read out-of-bound Tony Luck <tony.luck(a)intel.com> ACPI: APEI: Better fix to avoid spamming the console with old error logs Werner Sembach <wse(a)tuxedocomputers.com> ACPI: video: Shortening quirk list by identifying Clevo by board_name only Werner Sembach <wse(a)tuxedocomputers.com> ACPI: video: Force backlight native for some TongFang devices Stéphane Graber <stgraber(a)ubuntu.com> tools/vm/slabinfo: Handle files in debugfs Jan Kara <jack(a)suse.cz> block: fix default IO priority handling again ------------- Diffstat: Documentation/admin-guide/hw-vuln/spectre.rst | 8 ++ .../bindings/net/broadcom-bluetooth.yaml | 1 + Makefile | 4 +- arch/arm64/crypto/poly1305-glue.c | 2 +- arch/arm64/include/asm/kernel-pgtable.h | 4 +- arch/arm64/kernel/head.S | 2 +- arch/x86/include/asm/cpufeatures.h | 2 + arch/x86/include/asm/msr-index.h | 4 + arch/x86/include/asm/nospec-branch.h | 21 +++++- arch/x86/kernel/cpu/bugs.c | 86 ++++++++++++++++------ arch/x86/kernel/cpu/common.c | 12 ++- arch/x86/kvm/vmx/vmenter.S | 8 +- block/blk-ioc.c | 2 + block/ioprio.c | 4 +- drivers/acpi/apei/bert.c | 31 ++++++-- drivers/acpi/video_detect.c | 55 +++++++++----- drivers/ata/sata_mv.c | 2 +- drivers/bluetooth/btbcm.c | 2 + drivers/bluetooth/btusb.c | 15 ++++ drivers/bluetooth/hci_bcm.c | 2 + drivers/bluetooth/hci_qca.c | 2 +- drivers/macintosh/adb.c | 2 +- include/linux/ioprio.h | 2 +- tools/arch/x86/include/asm/cpufeatures.h | 1 + tools/arch/x86/include/asm/msr-index.h | 4 + tools/vm/slabinfo.c | 26 ++++++- 26 files changed, 232 insertions(+), 72 deletions(-)

2 years, 10 months

18
45
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror August 2022