)]}' { "log": [ { "commit": "dee67a94d4c6cbd05b8f6e1181498e94caa33334", "tree": "352f6df0c8bd645b0107e20fa2b7c3eeeb3d67ac", "parents": [ "cf6d9d2d243f242f51ee0666ca88e61d9408752f", "c3f3edf73a8f854f8766a69d2734198a58762e33" ], "author": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Fri Jun 21 08:03:55 2024 -0400" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Fri Jun 21 08:03:55 2024 -0400" }, "message": "Merge tag \u0027kvm-x86-fixes-6.10-rcN\u0027 of https://github.com/kvm-x86/linux into HEAD\n\nKVM fixes for 6.10\n\n - Fix a \"shift too big\" goof in the KVM_SEV_INIT2 selftest.\n\n - Compute the max mappable gfn for KVM selftests on x86 using GuestMaxPhyAddr\n from KVM\u0027s supported CPUID (if it\u0027s available).\n\n - Fix a race in kvm_vcpu_on_spin() by ensuring loads and stores are atomic.\n\n - Fix technically benign bug in __kvm_handle_hva_range() where KVM consumes\n the return from a void-returning function as if it were a boolean.\n" }, { "commit": "cf6d9d2d243f242f51ee0666ca88e61d9408752f", "tree": "c2afde663473eeb5e6dbd33cda988fdc5bb8565e", "parents": [ "fb443ce70da07b8e5ee1ca297d3c4b48692c1165" ], "author": { "name": "Michael Roth", "email": "michael.roth@amd.com", "time": "Tue Jun 04 18:35:10 2024 -0500" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Fri Jun 21 07:11:29 2024 -0400" }, "message": "KVM: SEV-ES: Fix svm_get_msr()/svm_set_msr() for KVM_SEV_ES_INIT guests\n\nWith commit 27bd5fdc24c0 (\"KVM: SEV-ES: Prevent MSR access post VMSA\nencryption\"), older VMMs like QEMU 9.0 and older will fail when booting\nSEV-ES guests with something like the following error:\n\n qemu-system-x86_64: error: failed to get MSR 0x174\n qemu-system-x86_64: ../qemu.git/target/i386/kvm/kvm.c:3950: kvm_get_msrs: Assertion `ret \u003d\u003d cpu-\u003ekvm_msr_buf-\u003enmsrs\u0027 failed.\n\nThis is because older VMMs that might still call\nsvm_get_msr()/svm_set_msr() for SEV-ES guests after guest boot even if\nthose interfaces were essentially just noops because of the vCPU state\nbeing encrypted and stored separately in the VMSA. Now those VMMs will\nget an -EINVAL and generally crash.\n\nNewer VMMs that are aware of KVM_SEV_INIT2 however are already aware of\nthe stricter limitations of what vCPU state can be sync\u0027d during\nguest run-time, so newer QEMU for instance will work both for legacy\nKVM_SEV_ES_INIT interface as well as KVM_SEV_INIT2.\n\nSo when using KVM_SEV_INIT2 it\u0027s okay to assume userspace can deal with\n-EINVAL, whereas for legacy KVM_SEV_ES_INIT the kernel might be dealing\nwith either an older VMM and so it needs to assume that returning\n-EINVAL might break the VMM.\n\nAddress this by only returning -EINVAL if the guest was started with\nKVM_SEV_INIT2. Otherwise, just silently return.\n\nCc: Ravi Bangoria \u003cravi.bangoria@amd.com\u003e\nCc: Nikunj A Dadhania \u003cnikunj@amd.com\u003e\nReported-by: Srikanth Aithal \u003csraithal@amd.com\u003e\nCloses: https://lore.kernel.org/lkml/37usuu4yu4ok7be2hqexhmcyopluuiqj3k266z4gajc2rcj4yo@eujb23qc3zcm/\nFixes: 27bd5fdc24c0 (\"KVM: SEV-ES: Prevent MSR access post VMSA encryption\")\nSigned-off-by: Michael Roth \u003cmichael.roth@amd.com\u003e\nMessage-ID: \u003c20240604233510.764949-1-michael.roth@amd.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "fb443ce70da07b8e5ee1ca297d3c4b48692c1165", "tree": "39f732b887fe66726396c157866c44d1ee517c5d", "parents": [ "676f819c3e982db3695a371f336a05086585ea4f", "d66e50beb91114f387bd798a371384b2a245e8cc" ], "author": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Thu Jun 20 17:33:49 2024 -0400" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Thu Jun 20 17:33:49 2024 -0400" }, "message": "Merge tag \u0027kvmarm-fixes-6.10-2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD\n\nKVM/arm64 fixes for 6.10, take #2\n\n- Fix dangling references to a redistributor region if\n the vgic was prematurely destroyed.\n\n- Properly mark FFA buffers as released, ensuring that\n both parties can make forward progress.\n" }, { "commit": "676f819c3e982db3695a371f336a05086585ea4f", "tree": "0fbc0e6cfed74402610d4507c92f3f0429728bba", "parents": [ "c31745d2c508796a0996c88bf2e55f552d513f65" ], "author": { "name": "Bibo Mao", "email": "maobibo@loongson.cn", "time": "Thu Jun 13 20:28:03 2024 +0800" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Thu Jun 20 17:20:11 2024 -0400" }, "message": "KVM: Discard zero mask with function kvm_dirty_ring_reset\n\nFunction kvm_reset_dirty_gfn may be called with parameters cur_slot /\ncur_offset / mask are all zero, it does not represent real dirty page.\nIt is not necessary to clear dirty page in this condition. Also return\nvalue of macro __fls() is undefined if mask is zero which is called in\nfunciton kvm_reset_dirty_gfn(). Here just return.\n\nSigned-off-by: Bibo Mao \u003cmaobibo@loongson.cn\u003e\nMessage-ID: \u003c20240613122803.1031511-1-maobibo@loongson.cn\u003e\n[Move the conditional inside kvm_reset_dirty_gfn; suggested by\n Sean Christopherson. - Paolo]\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "c31745d2c508796a0996c88bf2e55f552d513f65", "tree": "b6d21cb721eff72a4b310f7e0bb8a2f2b84379e7", "parents": [ "f474092c6fe1e2154a35308a1a1aef3212c3ecf2" ], "author": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Tue Jun 11 04:22:18 2024 -0400" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Thu Jun 20 17:12:11 2024 -0400" }, "message": "virt: guest_memfd: fix reference leak on hwpoisoned page\n\nIf kvm_gmem_get_pfn() detects an hwpoisoned page, it returns -EHWPOISON\nbut it does not put back the reference that kvm_gmem_get_folio() had\ngrabbed. Add the forgotten folio_put().\n\nFixes: a7800aa80ea4 (\"KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\")\nCc: stable@vger.kernel.org\nReviewed-by: Liam Merwick \u003cliam.merwick@oracle.com\u003e\nReviewed-by: Isaku Yamahata \u003cisaku.yamahata@intel.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "f474092c6fe1e2154a35308a1a1aef3212c3ecf2", "tree": "7ca0bea9c81c710a28f2aeafcf02f18c4a8270c7", "parents": [ "b018589013d6db43fdc894c635d6590e0a7e3285" ], "author": { "name": "Alexey Dobriyan", "email": "adobriyan@gmail.com", "time": "Mon Jun 10 13:31:21 2024 +0300" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Thu Jun 20 14:19:12 2024 -0400" }, "message": "kvm: do not account temporary allocations to kmem\n\nSome allocations done by KVM are temporary, they are created as result\nof program actions, but can\u0027t exists for arbitrary long times.\n\nThey should have been GFP_TEMPORARY (rip!).\n\nOTOH, kvm-nx-lpage-recovery and kvm-pit kernel threads exist for as long\nas VM exists but their task_struct memory is not accounted.\nThis is story for another day.\n\nSigned-off-by: Alexey Dobriyan \u003cadobriyan@gmail.com\u003e\nMessage-ID: \u003cc0122f66-f428-417e-a360-b25fc0f154a0@p183\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "b018589013d6db43fdc894c635d6590e0a7e3285", "tree": "0eea2f00277cf47716597cccf286413e0e74ffc2", "parents": [ "f3ced000a2df53f4b12849e121769045a81a3b22" ], "author": { "name": "Sean Christopherson", "email": "seanjc@google.com", "time": "Mon Jun 10 09:34:27 2024 -0700" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Thu Jun 20 14:18:08 2024 -0400" }, "message": "MAINTAINERS: Drop Wanpeng Li as a Reviewer for KVM Paravirt support\n\nDrop Wanpeng as a KVM PARAVIRT reviewer as his @tencent.com email is\nbouncing, and according to lore[*], the last activity from his @gmail.com\naddress was almost two years ago.\n\n[*] https://lore.kernel.org/all/CANRm+Cwj29M9HU3\u003dJRUOaKDR+iDKgr0eNMWQi0iLkR5THON-bg@mail.gmail.com\n\nCc: Wanpeng Li \u003ckernellwp@gmail.com\u003e\nCc: Like Xu \u003clike.xu.linux@gmail.com\u003e\nSigned-off-by: Sean Christopherson \u003cseanjc@google.com\u003e\nMessage-ID: \u003c20240610163427.3359426-1-seanjc@google.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "f3ced000a2df53f4b12849e121769045a81a3b22", "tree": "fdf579eb23b4659e1b5255c6cfa556c5d6adecbb", "parents": [ "db574f2f96d0c9a245a9e787e3d9ec288fb2b445" ], "author": { "name": "Sean Christopherson", "email": "seanjc@google.com", "time": "Mon Jun 10 18:48:45 2024 -0700" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Thu Jun 20 14:18:02 2024 -0400" }, "message": "KVM: x86: Always sync PIR to IRR prior to scanning I/O APIC routes\n\nSync pending posted interrupts to the IRR prior to re-scanning I/O APIC\nroutes, irrespective of whether the I/O APIC is emulated by userspace or\nby KVM. If a level-triggered interrupt routed through the I/O APIC is\npending or in-service for a vCPU, KVM needs to intercept EOIs on said\nvCPU even if the vCPU isn\u0027t the destination for the new routing, e.g. if\nservicing an interrupt using the old routing races with I/O APIC\nreconfiguration.\n\nCommit fceb3a36c29a (\"KVM: x86: ioapic: Fix level-triggered EOI and\nuserspace I/OAPIC reconfigure race\") fixed the common cases, but\nkvm_apic_pending_eoi() only checks if an interrupt is in the local\nAPIC\u0027s IRR or ISR, i.e. misses the uncommon case where an interrupt is\npending in the PIR.\n\nFailure to intercept EOI can manifest as guest hangs with Windows 11 if\nthe guest uses the RTC as its timekeeping source, e.g. if the VMM doesn\u0027t\nexpose a more modern form of time to the guest.\n\nCc: stable@vger.kernel.org\nCc: Adamos Ttofari \u003cattofari@amazon.de\u003e\nCc: Raghavendra Rao Ananta \u003crananta@google.com\u003e\nReviewed-by: Jim Mattson \u003cjmattson@google.com\u003e\nSigned-off-by: Sean Christopherson \u003cseanjc@google.com\u003e\nMessage-ID: \u003c20240611014845.82795-1-seanjc@google.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "c3f3edf73a8f854f8766a69d2734198a58762e33", "tree": "51ebb48bffcf7aecd9d4ea91d35d865ddcb8a2ab", "parents": [ "49f683b41f28918df3e51ddc0d928cb2e934ccdb" ], "author": { "name": "Babu Moger", "email": "babu.moger@amd.com", "time": "Wed Jun 12 09:41:51 2024 -0500" }, "committer": { "name": "Sean Christopherson", "email": "seanjc@google.com", "time": "Tue Jun 18 08:51:03 2024 -0700" }, "message": "KVM: Stop processing *all* memslots when \"null\" mmu_notifier handler is found\n\nBail from outer address space loop, not just the inner memslot loop, when\na \"null\" handler is encountered by __kvm_handle_hva_range(), which is the\nintended behavior. On x86, which has multiple address spaces thanks to\nSMM emulation, breaking from just the memslot loop results in undefined\nbehavior due to assigning the non-existent return value from kvm_null_fn()\nto a bool.\n\nIn practice, the bug is benign as kvm_mmu_notifier_invalidate_range_end()\nis the only caller that passes handler\u003dkvm_null_fn, and it doesn\u0027t set\nflush_on_ret, i.e. assigning garbage to r.ret is ultimately ignored. And\nfor most configuration the compiler elides the entire sequence, i.e. there\nis no undefined behavior at runtime.\n\n ------------[ cut here ]------------\n UBSAN: invalid-load in arch/x86/kvm/../../../virt/kvm/kvm_main.c:655:10\n load of value 160 is not a valid value for type \u0027_Bool\u0027\n CPU: 370 PID: 8246 Comm: CPU 0/KVM Not tainted 6.8.2-amdsos-build58-ubuntu-22.04+ #1\n Hardware name: AMD Corporation Sh54p/Sh54p, BIOS WPC4429N 04/25/2024\n Call Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x48/0x60\n ubsan_epilogue+0x5/0x30\n __ubsan_handle_load_invalid_value+0x79/0x80\n kvm_mmu_notifier_invalidate_range_end.cold+0x18/0x4f [kvm]\n __mmu_notifier_invalidate_range_end+0x63/0xe0\n __split_huge_pmd+0x367/0xfc0\n do_huge_pmd_wp_page+0x1cc/0x380\n __handle_mm_fault+0x8ee/0xe50\n handle_mm_fault+0xe4/0x4a0\n __get_user_pages+0x190/0x840\n get_user_pages_unlocked+0xe0/0x590\n hva_to_pfn+0x114/0x550 [kvm]\n kvm_faultin_pfn+0xed/0x5b0 [kvm]\n kvm_tdp_page_fault+0x123/0x170 [kvm]\n kvm_mmu_page_fault+0x244/0xaa0 [kvm]\n vcpu_enter_guest+0x592/0x1070 [kvm]\n kvm_arch_vcpu_ioctl_run+0x145/0x8a0 [kvm]\n kvm_vcpu_ioctl+0x288/0x6d0 [kvm]\n __x64_sys_ioctl+0x8f/0xd0\n do_syscall_64+0x77/0x120\n entry_SYSCALL_64_after_hwframe+0x6e/0x76\n \u003c/TASK\u003e\n ---[ end trace ]---\n\nFixes: 071064f14d87 (\"KVM: Don\u0027t take mmu_lock for range invalidation unless necessary\")\nSigned-off-by: Babu Moger \u003cbabu.moger@amd.com\u003e\nLink: https://lore.kernel.org/r/b8723d39903b64c241c50f5513f804390c7b5eec.1718203311.git.babu.moger@amd.com\n[sean: massage changelog]\nSigned-off-by: Sean Christopherson \u003cseanjc@google.com\u003e\n" }, { "commit": "d66e50beb91114f387bd798a371384b2a245e8cc", "tree": "b868faa2ab5e31c7281b5aa649725d139b0d6092", "parents": [ "0d92e4a7ffd5c42b9fa864692f82476c0bf8bcc8" ], "author": { "name": "Vincent Donnefort", "email": "vdonnefort@google.com", "time": "Tue Jun 11 18:53:17 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Jun 11 19:39:22 2024 +0100" }, "message": "KVM: arm64: FFA: Release hyp rx buffer\n\nAccording to the FF-A spec (Buffer states and ownership), after a\nproducer has written into a buffer, it is \"full\" and now owned by the\nconsumer. The producer won\u0027t be able to use that buffer, until the\nconsumer hands it over with an invocation such as RX_RELEASE.\n\nIt is clear in the following paragraph (Transfer of buffer ownership),\nthat MEM_RETRIEVE_RESP is transferring the ownership from producer (in\nour case SPM) to consumer (hypervisor). RX_RELEASE is therefore\nmandatory here.\n\nIt is less clear though what is happening with MEM_FRAG_TX. But this\ninvocation, as a response to MEM_FRAG_RX writes into the same hypervisor\nRX buffer (see paragraph \"Transmission of transaction descriptor in\nfragments\"). Also this is matching the TF-A implementation where the RX\nbuffer is marked \"full\" during a MEM_FRAG_RX.\n\nRelease the RX hypervisor buffer in those two cases. This will unblock\nlater invocations using this buffer which would otherwise fail.\n(RETRIEVE_REQ, MEM_FRAG_RX and PARTITION_INFO_GET).\n\nSigned-off-by: Vincent Donnefort \u003cvdonnefort@google.com\u003e\nReviewed-by: Sudeep Holla \u003csudeep.holla@arm.com\u003e\nLink: https://lore.kernel.org/r/20240611175317.1220842-1-vdonnefort@google.com\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "0d92e4a7ffd5c42b9fa864692f82476c0bf8bcc8", "tree": "c2071f063eb61e655c9f37b4404f5c75146a824b", "parents": [ "afb91f5f8ad7af172d993a34fde1947892408f53" ], "author": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Wed Jun 05 18:56:37 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Thu Jun 06 08:54:15 2024 +0100" }, "message": "KVM: arm64: Disassociate vcpus from redistributor region on teardown\n\nWhen tearing down a redistributor region, make sure we don\u0027t have\nany dangling pointer to that region stored in a vcpu.\n\nFixes: e5a35635464b (\"kvm: arm64: vgic-v3: Introduce vgic_v3_free_redist_region()\")\nReported-by: Alexander Potapenko \u003cglider@google.com\u003e\nReviewed-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\nLink: https://lore.kernel.org/r/20240605175637.1635653-1-maz@kernel.org\nCc: stable@vger.kernel.org\n" }, { "commit": "49f683b41f28918df3e51ddc0d928cb2e934ccdb", "tree": "0c569fa3b762ba5ab1b5ae77c30a3b5257a98a74", "parents": [ "980b8bc01938c8bcc9742c1051f64b5f0ed178ac" ], "author": { "name": "Breno Leitao", "email": "leitao@debian.org", "time": "Fri May 10 02:23:52 2024 -0700" }, "committer": { "name": "Sean Christopherson", "email": "seanjc@google.com", "time": "Wed Jun 05 06:16:11 2024 -0700" }, "message": "KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin()\n\nUse {READ,WRITE}_ONCE() to access kvm-\u003elast_boosted_vcpu to ensure the\nloads and stores are atomic. In the extremely unlikely scenario the\ncompiler tears the stores, it\u0027s theoretically possible for KVM to attempt\nto get a vCPU using an out-of-bounds index, e.g. if the write is split\ninto multiple 8-bit stores, and is paired with a 32-bit load on a VM with\n257 vCPUs:\n\n CPU0 CPU1\n last_boosted_vcpu \u003d 0xff;\n\n (last_boosted_vcpu \u003d 0x100)\n last_boosted_vcpu[15:8] \u003d 0x01;\n i \u003d (last_boosted_vcpu \u003d 0x1ff)\n last_boosted_vcpu[7:0] \u003d 0x00;\n\n vcpu \u003d kvm-\u003evcpu_array[0x1ff];\n\nAs detected by KCSAN:\n\n BUG: KCSAN: data-race in kvm_vcpu_on_spin [kvm] / kvm_vcpu_on_spin [kvm]\n\n write to 0xffffc90025a92344 of 4 bytes by task 4340 on cpu 16:\n kvm_vcpu_on_spin (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4112) kvm\n handle_pause (arch/x86/kvm/vmx/vmx.c:5929) kvm_intel\n vmx_handle_exit (arch/x86/kvm/vmx/vmx.c:?\n\t\t arch/x86/kvm/vmx/vmx.c:6606) kvm_intel\n vcpu_run (arch/x86/kvm/x86.c:11107 arch/x86/kvm/x86.c:11211) kvm\n kvm_arch_vcpu_ioctl_run (arch/x86/kvm/x86.c:?) kvm\n kvm_vcpu_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:?) kvm\n __se_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:904 fs/ioctl.c:890)\n __x64_sys_ioctl (fs/ioctl.c:890)\n x64_sys_call (arch/x86/entry/syscall_64.c:33)\n do_syscall_64 (arch/x86/entry/common.c:?)\n entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n\n read to 0xffffc90025a92344 of 4 bytes by task 4342 on cpu 4:\n kvm_vcpu_on_spin (arch/x86/kvm/../../../virt/kvm/kvm_main.c:4069) kvm\n handle_pause (arch/x86/kvm/vmx/vmx.c:5929) kvm_intel\n vmx_handle_exit (arch/x86/kvm/vmx/vmx.c:?\n\t\t\tarch/x86/kvm/vmx/vmx.c:6606) kvm_intel\n vcpu_run (arch/x86/kvm/x86.c:11107 arch/x86/kvm/x86.c:11211) kvm\n kvm_arch_vcpu_ioctl_run (arch/x86/kvm/x86.c:?) kvm\n kvm_vcpu_ioctl (arch/x86/kvm/../../../virt/kvm/kvm_main.c:?) kvm\n __se_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:904 fs/ioctl.c:890)\n __x64_sys_ioctl (fs/ioctl.c:890)\n x64_sys_call (arch/x86/entry/syscall_64.c:33)\n do_syscall_64 (arch/x86/entry/common.c:?)\n entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n\n value changed: 0x00000012 -\u003e 0x00000000\n\nFixes: 217ece6129f2 (\"KVM: use yield_to instead of sleep in kvm_vcpu_on_spin\")\nCc: stable@vger.kernel.org\nSigned-off-by: Breno Leitao \u003cleitao@debian.org\u003e\nLink: https://lore.kernel.org/r/20240510092353.2261824-1-leitao@debian.org\nSigned-off-by: Sean Christopherson \u003cseanjc@google.com\u003e\n" }, { "commit": "980b8bc01938c8bcc9742c1051f64b5f0ed178ac", "tree": "0bf3dfac527077cb2f266b669c86250eebdad8ab", "parents": [ "d21b3c60d6e3917f7388db6bcc455f01c99ee42b" ], "author": { "name": "Tao Su", "email": "tao1.su@linux.intel.com", "time": "Mon May 13 09:40:03 2024 +0800" }, "committer": { "name": "Sean Christopherson", "email": "seanjc@google.com", "time": "Wed Jun 05 06:16:10 2024 -0700" }, "message": "KVM: selftests: x86: Prioritize getting max_gfn from GuestPhysBits\n\nUse the max mappable GPA via GuestPhysBits advertised by KVM to calculate\nmax_gfn. Currently some selftests (e.g. access_tracking_perf_test,\ndirty_log_test...) add RAM regions close to max_gfn, so guest may access\nGPA beyond its mappable range and cause infinite loop.\n\nAdjust max_gfn in vm_compute_max_gfn() since x86 selftests already\noverrides vm_compute_max_gfn() specifically to deal with goofy edge cases.\n\nReported-by: Yi Lai \u003cyi1.lai@intel.com\u003e\nSigned-off-by: Tao Su \u003ctao1.su@linux.intel.com\u003e\nTested-by: Yi Lai \u003cyi1.lai@intel.com\u003e\nReviewed-by: Xiaoyao Li \u003cxiaoyao.li@intel.com\u003e\nLink: https://lore.kernel.org/r/20240513014003.104593-1-tao1.su@linux.intel.com\n[sean: tweak name, add comment and sanity check]\nSigned-off-by: Sean Christopherson \u003cseanjc@google.com\u003e\n" }, { "commit": "d21b3c60d6e3917f7388db6bcc455f01c99ee42b", "tree": "2aecbc42efac1781d566751d126fb41ebbc13140", "parents": [ "c3f38fa61af77b49866b006939479069cd451173" ], "author": { "name": "Colin Ian King", "email": "colin.i.king@gmail.com", "time": "Thu May 23 16:41:02 2024 +0100" }, "committer": { "name": "Sean Christopherson", "email": "seanjc@google.com", "time": "Wed Jun 05 06:16:09 2024 -0700" }, "message": "KVM: selftests: Fix shift of 32 bit unsigned int more than 32 bits\n\nCurrrentl a 32 bit 1u value is being shifted more than 32 bits causing\noverflow and incorrect checking of bits 32-63. Fix this by using the\nBIT_ULL macro for shifting bits.\n\nDetected by cppcheck:\nsev_init2_tests.c:108:34: error: Shifting 32-bit value by 63 bits is\nundefined behaviour [shiftTooManyBits]\n\nFixes: dfc083a181ba (\"selftests: kvm: add tests for KVM_SEV_INIT2\")\nSigned-off-by: Colin Ian King \u003ccolin.i.king@gmail.com\u003e\nLink: https://lore.kernel.org/r/20240523154102.2236133-1-colin.i.king@gmail.com\nSigned-off-by: Sean Christopherson \u003cseanjc@google.com\u003e\n" }, { "commit": "db574f2f96d0c9a245a9e787e3d9ec288fb2b445", "tree": "5f6f89dff093fc0f894d9f4fd8ff5b409a835888", "parents": [ "45ce0314bf258bd387d92782d5393e7b84b0121f" ], "author": { "name": "Tao Su", "email": "tao1.su@linux.intel.com", "time": "Tue May 28 18:22:34 2024 +0800" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Wed Jun 05 06:45:06 2024 -0400" }, "message": "KVM: x86/mmu: Don\u0027t save mmu_invalidate_seq after checking private attr\n\nDrop the second snapshot of mmu_invalidate_seq in kvm_faultin_pfn().\nBefore checking the mismatch of private vs. shared, mmu_invalidate_seq is\nsaved to fault-\u003emmu_seq, which can be used to detect an invalidation\nrelated to the gfn occurred, i.e. KVM will not install a mapping in page\ntable if fault-\u003emmu_seq !\u003d mmu_invalidate_seq.\n\nCurrently there is a second snapshot of mmu_invalidate_seq, which may not\nbe same as the first snapshot in kvm_faultin_pfn(), i.e. the gfn attribute\nmay be changed between the two snapshots, but the gfn may be mapped in\npage table without hindrance. Therefore, drop the second snapshot as it\nhas no obvious benefits.\n\nFixes: f6adeae81f35 (\"KVM: x86/mmu: Handle no-slot faults at the beginning of kvm_faultin_pfn()\")\nSigned-off-by: Tao Su \u003ctao1.su@linux.intel.com\u003e\nMessage-ID: \u003c20240528102234.2162763-1-tao1.su@linux.intel.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "45ce0314bf258bd387d92782d5393e7b84b0121f", "tree": "734e0d9f158f41bc666e7c1e2caf818f0ec6fb50", "parents": [ "b50788f7cd31a07e0c69c02d2f34b65121ff8775", "afb91f5f8ad7af172d993a34fde1947892408f53" ], "author": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Wed Jun 05 06:32:18 2024 -0400" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Wed Jun 05 06:32:18 2024 -0400" }, "message": "Merge tag \u0027kvmarm-fixes-6.10-1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD\n\nKVM/arm64 fixes for 6.10, take #1\n\n- Large set of FP/SVE fixes for pKVM, addressing the fallout\n from the per-CPU data rework and making sure that the host\n is not involved in the FP/SVE switching any more\n\n- Allow FEAT_BTI to be enabled with NV now that FEAT_PAUTH\n is copletely supported\n\n- Fix for the respective priorities of Failed PAC, Illegal\n Execution state and Instruction Abort exceptions\n\n- Fix the handling of AArch32 instruction traps failing their\n condition code, which was broken by the introduction of\n ESR_EL2.ISS2\n\n- Allow vpcus running in AArch32 state to be restored in\n System mode\n\n- Fix AArch32 GPR restore that would lose the 64 bit state\n under some conditions\n" }, { "commit": "afb91f5f8ad7af172d993a34fde1947892408f53", "tree": "deeee773464a6957b597dc5abe111564ba476746", "parents": [ "a69283ae1db8dd416870d931caa9e2d3d2c1cd8b" ], "author": { "name": "Fuad Tabba", "email": "tabba@google.com", "time": "Mon Jun 03 13:28:51 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Jun 04 15:06:33 2024 +0100" }, "message": "KVM: arm64: Ensure that SME controls are disabled in protected mode\n\nKVM (and pKVM) do not support SME guests. Therefore KVM ensures\nthat the host\u0027s SME state is flushed and that SME controls for\nenabling access to ZA storage and for streaming are disabled.\n\npKVM needs to protect against a buggy/malicious host. Ensure that\nit wouldn\u0027t run a guest when protected mode is enabled should any\nof the SME controls be enabled.\n\nSigned-off-by: Fuad Tabba \u003ctabba@google.com\u003e\nLink: https://lore.kernel.org/r/20240603122852.3923848-10-tabba@google.com\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "a69283ae1db8dd416870d931caa9e2d3d2c1cd8b", "tree": "8237eb6239dfdc77bf435ab759b07edc8540c2bf", "parents": [ "1696fc2174dbab12228ea9ec4c213d6aeea348f8" ], "author": { "name": "Fuad Tabba", "email": "tabba@google.com", "time": "Mon Jun 03 13:28:50 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Jun 04 15:06:33 2024 +0100" }, "message": "KVM: arm64: Refactor CPACR trap bit setting/clearing to use ELx format\n\nWhen setting/clearing CPACR bits for EL0 and EL1, use the ELx\nformat of the bits, which covers both. This makes the code\nclearer, and reduces the chances of accidentally missing a bit.\n\nNo functional change intended.\n\nReviewed-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nSigned-off-by: Fuad Tabba \u003ctabba@google.com\u003e\nLink: https://lore.kernel.org/r/20240603122852.3923848-9-tabba@google.com\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "1696fc2174dbab12228ea9ec4c213d6aeea348f8", "tree": "da3ecb9639424a06db8411eecb8235d13c6039de", "parents": [ "b5b9955617bc0b41546f2fa7c3dbcc048b43dc82" ], "author": { "name": "Fuad Tabba", "email": "tabba@google.com", "time": "Mon Jun 03 13:28:49 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Jun 04 15:06:33 2024 +0100" }, "message": "KVM: arm64: Consolidate initializing the host data\u0027s fpsimd_state/sve in pKVM\n\nNow that we have introduced finalize_init_hyp_mode(), lets\nconsolidate the initializing of the host_data fpsimd_state and\nsve state.\n\nReviewed-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nSigned-off-by: Fuad Tabba \u003ctabba@google.com\u003e\nReviewed-by: Mark Brown \u003cbroonie@kernel.org\u003e\nLink: https://lore.kernel.org/r/20240603122852.3923848-8-tabba@google.com\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "b5b9955617bc0b41546f2fa7c3dbcc048b43dc82", "tree": "034e4b9879c431dda19c38e0dad0e2e1443dabd5", "parents": [ "66d5b53e20a6e00b7ce3b652a3e2db967f7b33d0" ], "author": { "name": "Fuad Tabba", "email": "tabba@google.com", "time": "Mon Jun 03 13:28:48 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Jun 04 15:06:33 2024 +0100" }, "message": "KVM: arm64: Eagerly restore host fpsimd/sve state in pKVM\n\nWhen running in protected mode we don\u0027t want to leak protected\nguest state to the host, including whether a guest has used\nfpsimd/sve. Therefore, eagerly restore the host state on guest\nexit when running in protected mode, which happens only if the\nguest has used fpsimd/sve.\n\nReviewed-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nSigned-off-by: Fuad Tabba \u003ctabba@google.com\u003e\nLink: https://lore.kernel.org/r/20240603122852.3923848-7-tabba@google.com\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "66d5b53e20a6e00b7ce3b652a3e2db967f7b33d0", "tree": "18f77f59a02c28da6abe85df94d16d2dbde15c03", "parents": [ "e511e08a9f496948b13aac50610f2d17335f56c3" ], "author": { "name": "Fuad Tabba", "email": "tabba@google.com", "time": "Mon Jun 03 13:28:47 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Jun 04 15:06:33 2024 +0100" }, "message": "KVM: arm64: Allocate memory mapped at hyp for host sve state in pKVM\n\nProtected mode needs to maintain (save/restore) the host\u0027s sve\nstate, rather than relying on the host kernel to do that. This is\nto avoid leaking information to the host about guests and the\ntype of operations they are performing.\n\nAs a first step towards that, allocate memory mapped at hyp, per\ncpu, for the host sve state. The following patch will use this\nmemory to save/restore the host state.\n\nReviewed-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nSigned-off-by: Fuad Tabba \u003ctabba@google.com\u003e\nLink: https://lore.kernel.org/r/20240603122852.3923848-6-tabba@google.com\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "e511e08a9f496948b13aac50610f2d17335f56c3", "tree": "62f487e64228537e4c1cdaaa1a34ff873c45607b", "parents": [ "6d8fb3cbf7e06431a607c30c1bc4cd53a62c220a" ], "author": { "name": "Fuad Tabba", "email": "tabba@google.com", "time": "Mon Jun 03 13:28:46 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Jun 04 15:06:33 2024 +0100" }, "message": "KVM: arm64: Specialize handling of host fpsimd state on trap\n\nIn subsequent patches, n/vhe will diverge on saving the host\nfpsimd/sve state when taking a guest fpsimd/sve trap. Add a\nspecialized helper to handle it.\n\nNo functional change intended.\n\nReviewed-by: Mark Brown \u003cbroonie@kernel.org\u003e\nReviewed-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nSigned-off-by: Fuad Tabba \u003ctabba@google.com\u003e\nLink: https://lore.kernel.org/r/20240603122852.3923848-5-tabba@google.com\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "6d8fb3cbf7e06431a607c30c1bc4cd53a62c220a", "tree": "ba24ba31fc7451bd33bbe7dbfc101dceb476d72f", "parents": [ "45f4ea9bcfe909b3461059990b1e232e55dde809" ], "author": { "name": "Fuad Tabba", "email": "tabba@google.com", "time": "Mon Jun 03 13:28:45 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Jun 04 15:06:33 2024 +0100" }, "message": "KVM: arm64: Abstract set/clear of CPTR_EL2 bits behind helper\n\nThe same traps controlled by CPTR_EL2 or CPACR_EL1 need to be\ntoggled in different parts of the code, but the exact bits and\ntheir polarity differ between these two formats and the mode\n(vhe/nvhe/hvhe).\n\nTo reduce the amount of duplicated code and the chance of getting\nthe wrong bit/polarity or missing a field, abstract the set/clear\nof CPTR_EL2 bits behind a helper.\n\nSince (h)VHE is the way of the future, use the CPACR_EL1 format,\nwhich is a subset of the VHE CPTR_EL2, as a reference.\n\nNo functional change intended.\n\nSuggested-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nReviewed-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nSigned-off-by: Fuad Tabba \u003ctabba@google.com\u003e\nLink: https://lore.kernel.org/r/20240603122852.3923848-4-tabba@google.com\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "45f4ea9bcfe909b3461059990b1e232e55dde809", "tree": "1496f5ca29d365e49ec0f6e9f345fae840ca127a", "parents": [ "87bb39ed40bdf1596b8820e800226e24eb642677" ], "author": { "name": "Fuad Tabba", "email": "tabba@google.com", "time": "Mon Jun 03 13:28:44 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Jun 04 15:06:32 2024 +0100" }, "message": "KVM: arm64: Fix prototype for __sve_save_state/__sve_restore_state\n\nSince the prototypes for __sve_save_state/__sve_restore_state at\nhyp were added, the underlying macro has acquired a third\nparameter for saving/restoring ffr.\n\nFix the prototypes to account for the third parameter, and\nrestore the ffr for the guest since it is saved.\n\nSuggested-by: Mark Brown \u003cbroonie@kernel.org\u003e\nSigned-off-by: Fuad Tabba \u003ctabba@google.com\u003e\nReviewed-by: Mark Brown \u003cbroonie@kernel.org\u003e\nLink: https://lore.kernel.org/r/20240603122852.3923848-3-tabba@google.com\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "87bb39ed40bdf1596b8820e800226e24eb642677", "tree": "0897925b7249ad7d1acc5c6f69846a8fd2ab5f76", "parents": [ "47eb2d68d10208e6a9e89d10b66018e8d6ca0623" ], "author": { "name": "Fuad Tabba", "email": "tabba@google.com", "time": "Mon Jun 03 13:28:43 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue Jun 04 15:06:32 2024 +0100" }, "message": "KVM: arm64: Reintroduce __sve_save_state\n\nNow that the hypervisor is handling the host sve state in\nprotected mode, it needs to be able to save it.\n\nThis reverts commit e66425fc9ba3 (\"KVM: arm64: Remove unused\n__sve_save_state\").\n\nReviewed-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nSigned-off-by: Fuad Tabba \u003ctabba@google.com\u003e\nLink: https://lore.kernel.org/r/20240603122852.3923848-2-tabba@google.com\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "b50788f7cd31a07e0c69c02d2f34b65121ff8775", "tree": "d43dfabab4f26a4dba67a20cfd07b4323e1297b6", "parents": [ "b3233c737ec5bf8b35130cdb6b3fe49b26a2be99", "c66f3b40b17d3dfc4b6abb5efde8e71c46971821" ], "author": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Mon Jun 03 13:18:18 2024 -0400" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Mon Jun 03 13:18:18 2024 -0400" }, "message": "Merge tag \u0027kvm-riscv-fixes-6.10-1\u0027 of https://github.com/kvm-riscv/linux into HEAD\n\nKVM/riscv fixes for 6.10, take #1\n\n- No need to use mask when hart-index-bits is 0\n- Fix incorrect reg_subtype labels in kvm_riscv_vcpu_set_reg_isa_ext()\n" }, { "commit": "b3233c737ec5bf8b35130cdb6b3fe49b26a2be99", "tree": "03e0f256efd03158095f9f010f94ffd8b5c84061", "parents": [ "c3f38fa61af77b49866b006939479069cd451173", "89a58812c47f1823191e9d0b08b53df2dd304ae2" ], "author": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Mon Jun 03 13:09:55 2024 -0400" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Mon Jun 03 13:18:08 2024 -0400" }, "message": "Merge branch \u0027kvm-fixes-6.10-1\u0027 into HEAD\n\n* Fixes and debugging help for the #VE sanity check. Also disable\n it by default, even for CONFIG_DEBUG_KERNEL, because it was found\n to trigger spuriously (most likely a processor erratum as the\n exact symptoms vary by generation).\n\n* Avoid WARN() when two NMIs arrive simultaneously during an NMI-disabled\n situation (GIF\u003d0 or interrupt shadow) when the processor supports\n virtual NMI. While generally KVM will not request an NMI window\n when virtual NMIs are supported, in this case it *does* have to\n single-step over the interrupt shadow or enable the STGI intercept,\n in order to deliver the latched second NMI.\n\n* Drop support for hand tuning APIC timer advancement from userspace.\n Since we have adaptive tuning, and it has proved to work well,\n drop the module parameter for manual configuration and with it a\n few stupid bugs that it had.\n" }, { "commit": "89a58812c47f1823191e9d0b08b53df2dd304ae2", "tree": "e7c72ea3daa705e174b93b85c8b37ba1bc892556", "parents": [ "b7e4be0a224fe5c6be30c1c8bdda8d2317ad6ba4" ], "author": { "name": "Sean Christopherson", "email": "seanjc@google.com", "time": "Tue May 21 18:03:04 2024 -0700" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Mon Jun 03 13:08:05 2024 -0400" }, "message": "KVM: x86: Drop support for hand tuning APIC timer advancement from userspace\n\nRemove support for specifying a static local APIC timer advancement value,\nand instead present a read-only boolean parameter to let userspace enable\nor disable KVM\u0027s dynamic APIC timer advancement. Realistically, it\u0027s all\nbut impossible for userspace to specify an advancement that is more\nprecise than what KVM\u0027s adaptive tuning can provide. E.g. a static value\nneeds to be tuned for the exact hardware and kernel, and if KVM is using\nhrtimers, likely requires additional tuning for the exact configuration of\nthe entire system.\n\nDropping support for a userspace provided value also fixes several flaws\nin the interface. E.g. KVM interprets a negative value other than -1 as a\nlarge advancement, toggling between a negative and positive value yields\nunpredictable behavior as vCPUs will switch from dynamic to static\nadvancement, changing the advancement in the middle of VM creation can\nresult in different values for vCPUs within a VM, etc. Those flaws are\nmostly fixable, but there\u0027s almost no justification for taking on yet more\ncomplexity (it\u0027s minimal complexity, but still non-zero).\n\nThe only arguments against using KVM\u0027s adaptive tuning is if a setup needs\na higher maximum, or if the adjustments are too reactive, but those are\narguments for letting userspace control the absolute max advancement and\nthe granularity of each adjustment, e.g. similar to how KVM provides knobs\nfor halt polling.\n\nLink: https://lore.kernel.org/all/20240520115334.852510-1-zhoushuling@huawei.com\nCc: Shuling Zhou \u003czhoushuling@huawei.com\u003e\nCc: Marcelo Tosatti \u003cmtosatti@redhat.com\u003e\nSigned-off-by: Sean Christopherson \u003cseanjc@google.com\u003e\nMessage-ID: \u003c20240522010304.1650603-1-seanjc@google.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "b7e4be0a224fe5c6be30c1c8bdda8d2317ad6ba4", "tree": "5f97963333ec76d6a6e233b0fc667749f73ff872", "parents": [ "d922056215617eedfbdbc29fe49953423686fe5e" ], "author": { "name": "Ravi Bangoria", "email": "ravi.bangoria@amd.com", "time": "Fri May 31 04:46:44 2024 +0000" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Mon Jun 03 13:07:18 2024 -0400" }, "message": "KVM: SEV-ES: Delegate LBR virtualization to the processor\n\nAs documented in APM[1], LBR Virtualization must be enabled for SEV-ES\nguests. Although KVM currently enforces LBRV for SEV-ES guests, there\nare multiple issues with it:\n\no MSR_IA32_DEBUGCTLMSR is still intercepted. Since MSR_IA32_DEBUGCTLMSR\n interception is used to dynamically toggle LBRV for performance reasons,\n this can be fatal for SEV-ES guests. For ex SEV-ES guest on Zen3:\n\n [guest ~]# wrmsr 0x1d9 0x4\n KVM: entry failed, hardware error 0xffffffff\n EAX\u003d00000004 EBX\u003d00000000 ECX\u003d000001d9 EDX\u003d00000000\n\n Fix this by never intercepting MSR_IA32_DEBUGCTLMSR for SEV-ES guests.\n No additional save/restore logic is required since MSR_IA32_DEBUGCTLMSR\n is of swap type A.\n\no KVM will disable LBRV if userspace sets MSR_IA32_DEBUGCTLMSR before the\n VMSA is encrypted. Fix this by moving LBRV enablement code post VMSA\n encryption.\n\n[1]: AMD64 Architecture Programmer\u0027s Manual Pub. 40332, Rev. 4.07 - June\n 2023, Vol 2, 15.35.2 Enabling SEV-ES.\n https://bugzilla.kernel.org/attachment.cgi?id\u003d304653\n\nFixes: 376c6d285017 (\"KVM: SVM: Provide support for SEV-ES vCPU creation/loading\")\nCo-developed-by: Nikunj A Dadhania \u003cnikunj@amd.com\u003e\nSigned-off-by: Nikunj A Dadhania \u003cnikunj@amd.com\u003e\nSigned-off-by: Ravi Bangoria \u003cravi.bangoria@amd.com\u003e\nMessage-ID: \u003c20240531044644.768-4-ravi.bangoria@amd.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "d922056215617eedfbdbc29fe49953423686fe5e", "tree": "7711d656d269bf18bb4250299e7f63693f4121a4", "parents": [ "27bd5fdc24c0d5d1306f968ef24105c4577242b0" ], "author": { "name": "Ravi Bangoria", "email": "ravi.bangoria@amd.com", "time": "Fri May 31 04:46:43 2024 +0000" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Mon Jun 03 13:06:48 2024 -0400" }, "message": "KVM: SEV-ES: Disallow SEV-ES guests when X86_FEATURE_LBRV is absent\n\nAs documented in APM[1], LBR Virtualization must be enabled for SEV-ES\nguests. So, prevent SEV-ES guests when LBRV support is missing.\n\n[1]: AMD64 Architecture Programmer\u0027s Manual Pub. 40332, Rev. 4.07 - June\n 2023, Vol 2, 15.35.2 Enabling SEV-ES.\n https://bugzilla.kernel.org/attachment.cgi?id\u003d304653\n\nFixes: 376c6d285017 (\"KVM: SVM: Provide support for SEV-ES vCPU creation/loading\")\nSigned-off-by: Ravi Bangoria \u003cravi.bangoria@amd.com\u003e\nMessage-ID: \u003c20240531044644.768-3-ravi.bangoria@amd.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "27bd5fdc24c0d5d1306f968ef24105c4577242b0", "tree": "db4b43259cfb6ee57fbdaf6feaa0151437b7f4c8", "parents": [ "b4bd556467477420ee3a91fbcba73c579669edc6" ], "author": { "name": "Nikunj A Dadhania", "email": "nikunj@amd.com", "time": "Fri May 31 04:46:42 2024 +0000" }, "committer": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Mon Jun 03 13:06:48 2024 -0400" }, "message": "KVM: SEV-ES: Prevent MSR access post VMSA encryption\n\nKVM currently allows userspace to read/write MSRs even after the VMSA is\nencrypted. This can cause unintentional issues if MSR access has side-\neffects. For ex, while migrating a guest, userspace could attempt to\nmigrate MSR_IA32_DEBUGCTLMSR and end up unintentionally disabling LBRV on\nthe target. Fix this by preventing access to those MSRs which are context\nswitched via the VMSA, once the VMSA is encrypted.\n\nSuggested-by: Sean Christopherson \u003cseanjc@google.com\u003e\nSigned-off-by: Nikunj A Dadhania \u003cnikunj@amd.com\u003e\nSigned-off-by: Ravi Bangoria \u003cravi.bangoria@amd.com\u003e\nMessage-ID: \u003c20240531044644.768-2-ravi.bangoria@amd.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n" }, { "commit": "c3f38fa61af77b49866b006939479069cd451173", "tree": "b6b90bae867ab9a6b1b8d1323df48f3fb6ebf6a9", "parents": [ "58d89ee81a0b264db6249a374b1264a475aef4ca" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 15:44:56 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 15:44:56 2024 -0700" }, "message": "Linux 6.10-rc2\n" }, { "commit": "58d89ee81a0b264db6249a374b1264a475aef4ca", "tree": "8c40a67a6c6dc45f373f38e1c6d123489ce78ccf", "parents": [ "a693b9c95abd4947c2d06e05733de5d470ab6586", "3cb648c4dd3e8dde800fb3659250ed11f2d9efa5" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 13:30:53 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 13:30:53 2024 -0700" }, "message": "Merge tag \u0027ata-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux\n\nPull ata fixes from Niklas Cassel:\n\n - Add a quirk for three different devices that have shown issues with\n LPM (link power management). These devices appear to not implement\n LPM properly, since we see command timeouts when enabling LPM. The\n quirk disables LPM for these problematic devices. (Me)\n\n - Do not apply the Intel PCS quirk on Alder Lake. The quirk is not\n needed and was originally added by mistake when LPM support was\n enabled for this AHCI controller. Enabling the quirk when not needed\n causes the the controller to not be able to detect the connected\n devices on some platforms.\n\n* tag \u0027ata-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux:\n ata: libata-core: Add ATA_HORKAGE_NOLPM for Apacer AS340\n ata: libata-core: Add ATA_HORKAGE_NOLPM for AMD Radeon S3 SSD\n ata: libata-core: Add ATA_HORKAGE_NOLPM for Crucial CT240BX500SSD1\n ata: ahci: Do not apply Intel PCS quirk on Intel Alder Lake\n" }, { "commit": "a693b9c95abd4947c2d06e05733de5d470ab6586", "tree": "0e40ee6bafe28f9c1e6cfadf0f9f26e4b925b79d", "parents": [ "3fca58ffad37a06912d25e5a1818afb3183cff17", "0c2f6d04619ec2b53ad4b0b591eafc9389786e86" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 09:32:34 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 09:32:34 2024 -0700" }, "message": "Merge tag \u0027x86-urgent-2024-06-02\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip\n\nPull x86 fixes from Ingo Molnar:\n \"Miscellaneous topology parsing fixes:\n\n - Fix topology parsing regression on older CPUs in the new AMD/Hygon\n parser\n\n - Fix boot crash on odd Intel Quark and similar CPUs that do not fill\n out cpuinfo_x86::x86_clflush_size and zero out\n cpuinfo_x86::x86_cache_alignment as a result.\n\n Provide 32 bytes as a general fallback value.\n\n - Fix topology enumeration on certain rare CPUs where the BIOS locks\n certain CPUID leaves and the kernel unlocked them late, which broke\n with the new topology parsing code. Factor out this unlocking logic\n and move it earlier in the parsing sequence\"\n\n* tag \u0027x86-urgent-2024-06-02\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:\n x86/topology/intel: Unlock CPUID before evaluating anything\n x86/cpu: Provide default cache line size if not enumerated\n x86/topology/amd: Evaluate SMT in CPUID leaf 0x8000001e only on family 0x17 and greater\n" }, { "commit": "3fca58ffad37a06912d25e5a1818afb3183cff17", "tree": "429af9795efa9c099790db50f066c66561d17a1b", "parents": [ "efa8f11a7ebeb8758dcd847a4b9a0cdcb68d9d87", "d40605a6823577a6c40fad6fb1f10a40ea0389d7" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 09:23:35 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 09:23:35 2024 -0700" }, "message": "Merge tag \u0027sched-urgent-2024-06-02\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip\n\nPull scheduler fix from Ingo Molnar:\n \"Export a symbol to make life easier for instrumentation/debugging\"\n\n* tag \u0027sched-urgent-2024-06-02\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:\n sched/x86: Export \u0027percpu arch_freq_scale\u0027\n" }, { "commit": "efa8f11a7ebeb8758dcd847a4b9a0cdcb68d9d87", "tree": "42e0f89459ad624fca21b9fe7073f04262da8066", "parents": [ "00a8c352dd7581961fd0f284c6fc1a17b370d0f4", "dc8e5dfb52d56e955ad09174330252710845b8d2" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 09:20:37 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 09:20:37 2024 -0700" }, "message": "Merge tag \u0027perf-urgent-2024-06-02\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip\n\nPull perf events fix from Ingo Molnar:\n \"Add missing MODULE_DESCRIPTION() lines\"\n\n* tag \u0027perf-urgent-2024-06-02\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:\n perf/x86/intel: Add missing MODULE_DESCRIPTION() lines\n perf/x86/rapl: Add missing MODULE_DESCRIPTION() line\n" }, { "commit": "00a8c352dd7581961fd0f284c6fc1a17b370d0f4", "tree": "92142d3913359374bbac68a7ce7fb5e98666aa2e", "parents": [ "83814698cf48ce3aadc5d88a3f577f04482ff92a", "99a6087dfdc65303d26ab5fba2dacd8931b82b08" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 09:15:28 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jun 02 09:15:28 2024 -0700" }, "message": "Merge tag \u0027hardening-v6.10-rc2-take2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux\n\nPull hardening fixes from Kees Cook:\n\n - scsi: mpt3sas: Avoid possible run-time warning with long manufacturer\n strings\n\n - mailmap: update entry for Kees Cook\n\n - kunit/fortify: Remove __kmalloc_node() test\n\n* tag \u0027hardening-v6.10-rc2-take2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux:\n kunit/fortify: Remove __kmalloc_node() test\n mailmap: update entry for Kees Cook\n scsi: mpt3sas: Avoid possible run-time warning with long manufacturer strings\n" }, { "commit": "83814698cf48ce3aadc5d88a3f577f04482ff92a", "tree": "b35bbbdffe75f446f042aab69e752202789fcd44", "parents": [ "54bec8ed5732339438271d07376890454fa58046", "be2fc65d66e0406cc9d39d40becaecdf4ee765f3" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 17:34:35 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 17:34:35 2024 -0700" }, "message": "Merge tag \u0027powerpc-6.10-2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux\n\nPull powerpc fixes from Michael Ellerman:\n\n - Enforce full ordering for ATOMIC operations with BPF_FETCH\n\n - Fix uaccess build errors seen with GCC 13/14\n\n - Fix build errors on ppc32 due to ARCH_HAS_KERNEL_FPU_SUPPORT\n\n - Drop error message from lparcfg guest name lookup\n\nThanks to Christophe Leroy, Guenter Roeck, Nathan Lynch, Naveen N Rao,\nPuranjay Mohan, and Samuel Holland.\n\n* tag \u0027powerpc-6.10-2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:\n powerpc: Limit ARCH_HAS_KERNEL_FPU_SUPPORT to PPC64\n powerpc/uaccess: Use YZ asm constraint for ld\n powerpc/uaccess: Fix build errors seen with GCC 13/14\n powerpc/pseries/lparcfg: drop error message from guest name lookup\n powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH\n" }, { "commit": "54bec8ed5732339438271d07376890454fa58046", "tree": "08b8e072bc22832a37d234891cb255ad1fafa416", "parents": [ "89be4025b0db42db830d72d532437248774cba49", "f94b77709e82242c1101e59a90a7807455c4ab2a" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 17:05:00 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 17:05:00 2024 -0700" }, "message": "Merge tag \u0027firewire-fixes-6.10-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394\n\nPull firewire fix from Takashi Sakamoto:\n \"After merging a commit 1fffe7a34c89 (\"script: modpost: emit a warning\n when the description is missing\"), MODULE_DESCRIPTOR seems to be\n mandatory for kernel modules. In FireWire subsystem, the most of\n practical kernel modules have the field, while KUnit test modules do\n not. A single patch is applied to fix them\"\n\n* tag \u0027firewire-fixes-6.10-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394:\n firewire: add missing MODULE_DESCRIPTION() to test modules\n" }, { "commit": "89be4025b0db42db830d72d532437248774cba49", "tree": "108d3055ad93d8307814278ff42828d385042004", "parents": [ "ec9eeb89e60d86fcc0243f47c2383399ce0de8f8", "518549c120e671c4906f77d1802b97e9b23f673a" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 14:35:57 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 14:35:57 2024 -0700" }, "message": "Merge tag \u00276.10-rc1-smb3-client-fixes\u0027 of git://git.samba.org/sfrench/cifs-2.6\n\nPull smb client fixes from Steve French:\n \"Two small smb3 fixes:\n\n - Fix socket creation with sfu mount option (spotted by test generic/423)\n\n - Minor cleanup: fix missing description in two files\"\n\n* tag \u00276.10-rc1-smb3-client-fixes\u0027 of git://git.samba.org/sfrench/cifs-2.6:\n cifs: fix creating sockets when using sfu mount options\n fs: smb: common: add missing MODULE_DESCRIPTION() macros\n" }, { "commit": "ec9eeb89e60d86fcc0243f47c2383399ce0de8f8", "tree": "c7ede32c369d743d2e5372f9648aaed77b25e074", "parents": [ "bbeb1219eeeeab7ef302fdaedee71b08e413a04c", "1b1c9f0fd3fb70adf1f3b0aec58ab037d6e595d0" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 09:33:55 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 09:33:55 2024 -0700" }, "message": "Merge tag \u0027kbuild-fixes-v6.10\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild\n\nPull Kbuild fixes from Masahiro Yamada:\n\n - Fix a Kconfig bug regarding comparisons to \u0027m\u0027 or \u0027n\u0027\n\n - Replace missed $(srctree)/$(src)\n\n - Fix unneeded kallsyms step 3\n\n - Remove incorrect \"compatible\" properties from image nodes in\n image.fit\n\n - Improve gen_kheaders.sh\n\n - Fix \u0027make dt_binding_check\u0027\n\n - Clean up unnecessary code\n\n* tag \u0027kbuild-fixes-v6.10\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild:\n dt-bindings: kbuild: Fix dt_binding_check on unconfigured build\n kheaders: use `command -v` to test for existence of `cpio`\n kheaders: explicitly define file modes for archived headers\n scripts/make_fit: Drop fdt image entry compatible string\n kbuild: remove a stale comment about cleaning in link-vmlinux.sh\n kbuild: fix short log for AS in link-vmlinux.sh\n kbuild: change scripts/mksysmap into sed script\n kbuild: avoid unneeded kallsyms step 3\n kbuild: scripts/gdb: Replace missed $(srctree)/$(src) w/ $(src)\n kconfig: remove redundant check in expr_join_or()\n kconfig: fix comparison to constant symbols, \u0027m\u0027, \u0027n\u0027\n kconfig: remove unused expr_is_no()\n" }, { "commit": "bbeb1219eeeeab7ef302fdaedee71b08e413a04c", "tree": "5bde40066a6ca08b1ad6cc56417af2aead8a1780", "parents": [ "f26ee67a0f94b8ec79b08c046c2a47568517d772", "b0c6bcd58d44b1b843d1b7218db5a1efe917d27e" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 08:59:04 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 08:59:04 2024 -0700" }, "message": "Merge tag \u0027xfs-6.10-fixes-1\u0027 of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux\n\nPull xfs fixes from Chandan Babu:\n\n - Fix a livelock by dropping an xfarray sortinfo folio when an error\n is encountered\n\n - During extended attribute operations, Initialize transaction\n reservation computation based on attribute operation code\n\n - Relax symbolic link\u0027s ondisk verification code to allow symbolic\n links with short remote targets\n\n - Prevent soft lockups when unmapping file ranges and also during\n remapping blocks during a reflink operation\n\n - Fix compilation warnings when XFS is built with W\u003d1 option\n\n* tag \u0027xfs-6.10-fixes-1\u0027 of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:\n xfs: Add cond_resched to block unmap range and reflink remap path\n xfs: don\u0027t open-code u64_to_user_ptr\n xfs: allow symlinks with short remote targets\n xfs: fix xfs_init_attr_trans not handling explicit operation codes\n xfs: drop xfarray sortinfo folio on error\n xfs: Stop using __maybe_unused in xfs_alloc.c\n xfs: Clear W\u003d1 warning in xfs_iwalk_run_callbacks()\n" }, { "commit": "f26ee67a0f94b8ec79b08c046c2a47568517d772", "tree": "d591401eecbc6284708c8826770c9da9a573d158", "parents": [ "d9aab0b1c9b2838b2c91431a5d4ac4129553797d", "7bc4244c882a7d7d79f4afefc50893244eb11d07" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 08:53:39 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 08:53:39 2024 -0700" }, "message": "Merge tag \u0027tty-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty\n\nPull tty fix from Greg KH:\n \"Here is a single revert for a much-reported regression in 6.10-rc1\n when it comes to a few older architectures.\n\n Turns out that the VT ioctls don\u0027t work the same across all cpu types\n because of some old compatibility requrements for stuff like alpha and\n powerpc. So revert the change that attempted to have them use the\n _IO() macros and go back to the known-working values instead.\n\n This has NOT been in linux-next but has had many reports that it fixes\n the issue with 6.10-rc1\"\n\n* tag \u0027tty-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:\n Revert \"VT: Use macros to define ioctls\"\n" }, { "commit": "d9aab0b1c9b2838b2c91431a5d4ac4129553797d", "tree": "248e38df2a37360ad75ef438c72012b61870f356", "parents": [ "cc8ed4d0a8486c7472cd72ec3c19957e509dc68c", "0055f53aac80fd938bf7cdfad7ad414ca6c0e198" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 08:28:24 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jun 01 08:28:24 2024 -0700" }, "message": "Merge tag \u0027landlock-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/mic/linux\n\nPull landlock fix from Mickaël Salaün:\n \"This fixes a wrong path walk triggered by syzkaller\"\n\n* tag \u0027landlock-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/mic/linux:\n selftests/landlock: Add layout1.refer_mount_root\n landlock: Fix d_parent walk\n" }, { "commit": "7bc4244c882a7d7d79f4afefc50893244eb11d07", "tree": "3624e4b370ff97b96b6ba0f233b2eb5d63da8e7f", "parents": [ "1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Jun 01 07:28:21 2024 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Jun 01 07:28:21 2024 +0200" }, "message": "Revert \"VT: Use macros to define ioctls\"\n\nThis reverts commit 8c467f3300591a206fa8dcc6988d768910799872.\n\nTurns out this breaks many architectures as the vt ioctls do not all\nmatch up everywhere due to historical reasons, so the original commit is\ninvalid for many values.\n\nReported-by: Nick Bowler \u003cnbowler@draconx.ca\u003e\nReported-by: Arnd Bergmann \u003carnd@kernel.org\u003e\nReported-by: Jiri Slaby \u003cjirislaby@kernel.org\u003e\nReported-by: Christian Zigotzky \u003cchzigotzky@xenosoft.de\u003e\nReported-by: Michael Ellerman \u003cmpe@ellerman.id.au\u003e\nCc: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Alexey Gladkov \u003clegion@kernel.org\u003e\nLink: https://lore.kernel.org/r/ad4e561c-1d49-4f25-882c-7a36c6b1b5c0@draconx.ca\nLink: https://lore.kernel.org/r/0da9785e-ba44-4718-9d08-4e96c1ba7ab2@kernel.org\nLink: https://lore.kernel.org/all/34d848f4-670b-4493-bf21-130ef862521b@xenosoft.de/\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "cc8ed4d0a8486c7472cd72ec3c19957e509dc68c", "tree": "02dcf6a1a3a580b67cf2753b513cd907d43ebfff", "parents": [ "1b907b83aecac3804e9b0ab2589578e3ba1c9f4a", "a2ce3f7752bfbb47e659574fc2e1e6942bca3c29" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:26:48 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:26:48 2024 -0700" }, "message": "Merge tag \u0027drm-fixes-2024-06-01\u0027 of https://gitlab.freedesktop.org/drm/kernel\n\nPull drm fixes from Dave Airlie:\n \"This is the weekly fixes. Lots of small fixes across the board, one\n BUG_ON fix in shmem seems most important, otherwise amdgpu, i915, xe\n mostly with small fixes to all the other drivers.\n\n shmem:\n - fix BUG_ON in COW handling\n - warn when trying to pin imported objects\n\n buddy:\n - fix page size handling\n\n dma-buf:\n - sw-sync: Don\u0027t interfere with IRQ handling\n - fix kthreads-handling error path\n\n i915:\n - fix a race in audio component by registering it later\n - make DPT object unshrinkable to avoid shrinking when framebuffer\n has not shrunk\n - fix CCS id calculation to fix a perf regression\n - fix selftest caching mode\n - fix FIELD_PREP compiler warnings\n - fix indefinite wait for GT wakeref release\n - revert overeager multi-gt pm reference removal\n\n xe:\n - pcode polling timeout change\n - fix for deadlocks for faulting VMs\n - error-path lock imbalance fix\n\n amdgpu:\n - RAS fix\n - fix colorspace property for MST connectors\n - fix for PCIe DPM\n - silence UBSAN warning\n - GPUVM robustness fix\n - partition fix\n - drop deprecated I2C_CLASS_SPD\n\n amdkfd:\n - revert unused changes for certain 11.0.3 devices\n - simplify APU VRAM handling\n\n lima:\n - fix dma_resv-related deadlock in object pin\n\n msm:\n - remove build-time dependency on Python 3.9\n\n nouveau:\n - nvif: Fix possible integer overflow\n\n panel:\n - lg-sw43408: Select DP helpers; Declare backlight ops as static\n - sitronix-st7789v: Various fixes for jt240mhqs_hwt_ek_e3 panel\n\n panfrost:\n - fix dma_resv-related deadlock in object pin\"\n\n* tag \u0027drm-fixes-2024-06-01\u0027 of https://gitlab.freedesktop.org/drm/kernel: (35 commits)\n drm/msm: remove python 3.9 dependency for compiling msm\n drm/panel: sitronix-st7789v: fix display size for jt240mhqs_hwt_ek_e3 panel\n drm/panel: sitronix-st7789v: tweak timing for jt240mhqs_hwt_ek_e3 panel\n drm/panel: sitronix-st7789v: fix timing for jt240mhqs_hwt_ek_e3 panel\n drm/amd/pm: remove deprecated I2C_CLASS_SPD support from newly added SMU_14_0_2\n drm/amdgpu: Make CPX mode auto default in NPS4\n drm/amdkfd: simplify APU VRAM handling\n Revert \"drm/amdkfd: fix gfx_target_version for certain 11.0.3 devices\"\n drm/amdgpu: fix dereference null return value for the function amdgpu_vm_pt_parent\n drm/amdgpu: silence UBSAN warning\n drm/amdgpu: Adjust logic in amdgpu_device_partner_bandwidth()\n drm/i915: Fix audio component initialization\n drm/i915/dpt: Make DPT object unshrinkable\n drm/i915/gt: Fix CCS id\u0027s calculation for CCS mode setting\n drm/panel/lg-sw43408: mark sw43408_backlight_ops as static\n drm/i915/selftests: Set always_coherent to false when reading from CPU\n drm/panel/lg-sw43408: select CONFIG_DRM_DISPLAY_DP_HELPER\n drm/i915/guc: avoid FIELD_PREP warning\n drm/i915/gt: Disarm breadcrumbs if engines are already idle\n Revert \"drm/i915: Remove extra multi-gt pm-references\"\n ...\n" }, { "commit": "1b907b83aecac3804e9b0ab2589578e3ba1c9f4a", "tree": "7383a3eb2bf5134224b45cecec73cdda792ec8ac", "parents": [ "b7087cb35a007245de172b0e05130d56f56248d5", "52a2c70c3ec555e670a34dd1ab958986451d2dd2" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:24:11 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:24:11 2024 -0700" }, "message": "Merge tag \u0027hwmon-for-v6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging\n\nPull hwmon fixes from Guenter Roeck:\n\n - sttcs: Fix property spelling\n\n - intel-m10-bmc-hwmon: Fix multiplier for N6000 board power sensor\n\n - ltc2992: Fix memory leak\n\n - dell-smm: Add Dell G15 5511 to fan control whitelist\n\n* tag \u0027hwmon-for-v6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging:\n hwmon: (shtc1) Fix property misspelling\n hwmon: (intel-m10-bmc-hwmon) Fix multiplier for N6000 board power sensor\n hwmon: (ltc2992) Fix memory leak in ltc2992_parse_dt()\n hwmon: (dell-smm) Add Dell G15 5511 to fan control whitelist\n" }, { "commit": "b7087cb35a007245de172b0e05130d56f56248d5", "tree": "c9f5672433680b5ef23102d39c6f242fdcb84c27", "parents": [ "d5931dd0de5f4177e38defedcc4c9cede7933d3d", "d551ce15d08114514d489fad63bd275de2aca862" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:21:00 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:21:00 2024 -0700" }, "message": "Merge tag \u0027mailbox-fixes-v6.10-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/jassibrar/mailbox\n\nPull mailbox fix from Jassi Brar:\n\n - zynqmp-ipi: fix linker error on some configurations\n\n* tag \u0027mailbox-fixes-v6.10-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/jassibrar/mailbox:\n mailbox: zynqmp-ipi: drop irq_to_desc() call\n" }, { "commit": "d5931dd0de5f4177e38defedcc4c9cede7933d3d", "tree": "a5ee2a90782bcee4f1cee0d904f16da1d07ddccd", "parents": [ "28add42dc226a4e7caf139407df714820b389bbc", "95d7c452a26564ef0c427f2806761b857106d8c4" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:17:40 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:17:40 2024 -0700" }, "message": "Merge tag \u0027spi-fix-v6.10-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi\n\nPull spi fixes from Mark Brown:\n \"A series of fixes that came in since the merge window, the main thing\n being the fixes Andy did for DMA sync where we were calling into the\n DMA API in suprising ways and causing issues as a result, the main\n thing being confusing the IOMMU code.\n\n We\u0027ve also got some fairly important fixes for the stm32 driver, it\n supports a wide range of hardware and some optimisations that were\n done recently have broken on some systems, and a fix to prevent\n glitched signals on the bus in the cadence driver\"\n\n* tag \u0027spi-fix-v6.10-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi:\n spi: stm32: Don\u0027t warn about spurious interrupts\n spi: Assign dummy scatterlist to unidirectional transfers\n spi: cadence: Ensure data lines set to low during dummy-cycle period\n spi: stm32: Revert change that enabled controller before asserting CS\n spi: Check if transfer is mapped before calling DMA sync APIs\n spi: Don\u0027t mark message DMA mapped when no transfer in it is\n" }, { "commit": "28add42dc226a4e7caf139407df714820b389bbc", "tree": "5276f0dc727b367a02a2a5bf719107a90f68a90b", "parents": [ "b7c05622da0e40c0ce93f847055a57e47df35492", "72b6a2d6506843375c7b91197f49ef38ca0c6d0f" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:12:54 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:12:54 2024 -0700" }, "message": "Merge tag \u0027regulator-fix-v6.10-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator\n\nPull regulator fix from Mark Brown:\n \"One fix that came in since -rc1, fixing misuse of a local variable in\n the DT parsing code in the RTQ2208 driver\"\n\n* tag \u0027regulator-fix-v6.10-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator:\n regulator: rtq2208: Fix invalid memory access when devm_of_regulator_put_matches is called\n" }, { "commit": "b7c05622da0e40c0ce93f847055a57e47df35492", "tree": "df48e7f22fd8214d48cfc8f069a2a1c59a471bed", "parents": [ "0f9a75179da33cc03594b882ed823cc5f4356d9a", "611b7eb19d0a305d4de00280e4a71a1b15c507fc" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:09:27 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 16:09:27 2024 -0700" }, "message": "Merge tag \u0027regmap-fix-v6.10-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap\n\nPull regmap fix from Mark Brown:\n \"The I2C bus was not taking account of the register and any padding\n bytes when handling maximum write sizes supported by an I2C adaptor,\n this patch from Jim Wylder fixes that\"\n\n* tag \u0027regmap-fix-v6.10-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap:\n regmap-i2c: Subtract reg size from max_write\n" }, { "commit": "0f9a75179da33cc03594b882ed823cc5f4356d9a", "tree": "7cb38f21b862a0d7e314100bf8935f707c60b0bd", "parents": [ "6d541d6672eeaf526d67b67b5407f48fe0522c6d", "0a751df4566c86e5a24f2a03290dad3d0f215692" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 15:31:27 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 15:31:27 2024 -0700" }, "message": "Merge tag \u0027block-6.10-20240530\u0027 of git://git.kernel.dk/linux\n\nPull block fixes from Jens Axboe:\n\n - NVMe fixes via Keith:\n - Removing unused fields (Kanchan)\n - Large folio offsets support (Kundan)\n - Multipath NUMA node initialiazation fix (Nilay)\n - Multipath IO stats accounting fixes (Keith)\n - Circular lockdep fix (Keith)\n - Target race condition fix (Sagi)\n - Target memory leak fix (Sagi)\n\n - bcache fixes\n\n - null_blk fixes (Damien)\n\n - Fix regression in io.max due to throttle low removal (Waiman)\n\n - DM limit table fixes (Christoph)\n\n - SCSI and block limit fixes (Christoph)\n\n - zone fixes (Damien)\n\n - Misc fixes (Christoph, Hannes, hexue)\n\n* tag \u0027block-6.10-20240530\u0027 of git://git.kernel.dk/linux: (25 commits)\n blk-throttle: Fix incorrect display of io.max\n block: Fix zone write plugging handling of devices with a runt zone\n block: Fix validation of zoned device with a runt zone\n null_blk: Do not allow runt zone with zone capacity smaller then zone size\n nvmet: fix a possible leak when destroy a ctrl during qp establishment\n nvme: use srcu for iterating namespace list\n bcache: code cleanup in __bch_bucket_alloc_set()\n bcache: call force_wake_up_gc() if necessary in check_should_bypass()\n bcache: allow allocator to invalidate bucket in gc\n block: check for max_hw_sectors underflow\n block: stack max_user_sectors\n sd: also set max_user_sectors when setting max_sectors\n null_blk: Print correct max open zones limit in null_init_zoned_dev()\n block: delete redundant function declaration\n null_blk: Fix return value of nullb_device_power_store()\n dm: make dm_set_zones_restrictions work on the queue limits\n dm: remove dm_check_zoned\n dm: move setting zoned_enabled to dm_table_set_restrictions\n block: remove blk_queue_max_integrity_segments\n nvme: adjust multiples of NVME_CTRL_PAGE_SIZE in offset\n ...\n" }, { "commit": "6d541d6672eeaf526d67b67b5407f48fe0522c6d", "tree": "c77aacebb645fc3c9a69ddd025504071adcf84ab", "parents": [ "b050496579632f86ee1ef7e7501906db579f3457", "18414a4a2eabb0281d12d374c92874327e0e3fe3" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 15:22:58 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 15:22:58 2024 -0700" }, "message": "Merge tag \u0027io_uring-6.10-20240530\u0027 of git://git.kernel.dk/linux\n\nPull io_uring fixes from Jens Axboe:\n \"A couple of minor fixes for issues introduced in the 6.10 merge window:\n\n - Ensure that all read/write ops have an appropriate cleanup handler\n set (Breno)\n\n - Regression for applications still doing multiple mmaps even if\n FEAT_SINGLE_MMAP is set (me)\n\n - Move kmsg inquiry setting above any potential failure point,\n avoiding a spurious NONEMPTY flag setting on early error (me)\"\n\n* tag \u0027io_uring-6.10-20240530\u0027 of git://git.kernel.dk/linux:\n io_uring/net: assign kmsg inq/flags before buffer selection\n io_uring/rw: Free iovec before cleaning async data\n io_uring: don\u0027t attempt to mmap larger than what the user asks for\n" }, { "commit": "99a6087dfdc65303d26ab5fba2dacd8931b82b08", "tree": "1e33f104f6583744d54f3e49423d6b05009fb261", "parents": [ "4e173c825b1914d5b118bbf26f0168102d56ae95" ], "author": { "name": "Kees Cook", "email": "kees@kernel.org", "time": "Fri May 31 11:57:07 2024 -0700" }, "committer": { "name": "Kees Cook", "email": "kees@kernel.org", "time": "Fri May 31 13:47:41 2024 -0700" }, "message": "kunit/fortify: Remove __kmalloc_node() test\n\n__kmalloc_node() is considered an \"internal\" function to the Slab, so\ndrop it from explicit testing.\n\nLink: https://lore.kernel.org/r/20240531185703.work.588-kees@kernel.org\nSigned-off-by: Kees Cook \u003ckees@kernel.org\u003e\n" }, { "commit": "b050496579632f86ee1ef7e7501906db579f3457", "tree": "f30be2e4897aaee85d7922ea3c0bc2a693d1b403", "parents": [ "7d88cc8ecc4cf74ef5e4e4f6c9ae4f13d9b969c9", "82d71b53d7e732ede6028591342bdc80fabfa29f" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 12:14:55 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 12:14:55 2024 -0700" }, "message": "Merge tag \u0027dma-mapping-6.10-2024-05-31\u0027 of git://git.infradead.org/users/hch/dma-mapping\n\nPull dma-mapping fixes from Christoph Hellwig:\n\n - dma-mapping benchmark error handling fixes (Fedor Pchelkin)\n\n - correct a config symbol reference in the DMA API documentation (Lukas\n Bulwahn)\n\n* tag \u0027dma-mapping-6.10-2024-05-31\u0027 of git://git.infradead.org/users/hch/dma-mapping:\n Documentation/core-api: correct reference to SWIOTLB_DYNAMIC\n dma-mapping: benchmark: handle NUMA_NO_NODE correctly\n dma-mapping: benchmark: fix node id validation\n dma-mapping: benchmark: avoid needless copy_to_user if benchmark fails\n dma-mapping: benchmark: fix up kthread-related error handling\n" }, { "commit": "7d88cc8ecc4cf74ef5e4e4f6c9ae4f13d9b969c9", "tree": "76b3b56bf39c6c8a145969970ef8dbe115566591", "parents": [ "87895a6402604f7a2b55a62e8afd7889b8ec72e4", "310fa3ec2859f1c094e6e9b5d2e1ca51738c409a" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 12:11:44 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 12:11:44 2024 -0700" }, "message": "Merge tag \u0027sound-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound\n\nPull sound fixes from Takashi Iwai:\n \"Lots of small fixes:\n\n - A race fix for debugfs handling in ALSA core\n\n - A series of corrections for MIDI2 core format conversions\n\n - ASoC Intel fixes for 16 bit DMIC config\n\n - Updates for missing module parameters in ASoC code\n\n - HD-audio quirk, Cirrus codec fix, etc minor fixes\"\n\n* tag \u0027sound-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound: (26 commits)\n ALSA: seq: ump: Fix swapped song position pointer data\n ASoC: SOF: ipc4-topology: Adjust the params based on DAI formats\n ASoC: SOF: ipc4-topology: Improve readability of sof_ipc4_prepare_dai_copier()\n ASoC: SOF: ipc4-topology/pcm: Rename sof_ipc4_copier_is_single_format()\n ASoC: SOF: ipc4-topology: Print out the channel count in sof_ipc4_dbg_audio_format\n ASoC: SOF: ipc4-topology: Add support for NHLT with 16-bit only DMIC blob\n ALSA: seq: Fix yet another spot for system message conversion\n ALSA: ump: Set default protocol when not given explicitly\n ALSA: ump: Don\u0027t accept an invalid UMP protocol number\n ASoC: SOF: ipc4-topology: Fix input format query of process modules without base extension\n ASoC: Intel: sof-sdw: fix missing SPI_MASTER dependency\n ALSA: pcm: fix typo in comment\n ALSA: ump: Don\u0027t clear bank selection after sending a program change\n ALSA: seq: Fix incorrect UMP type for system messages\n ALSA/hda: intel-dsp-config: reduce log verbosity\n ALSA: seq: Don\u0027t clear bank selection at event -\u003e UMP MIDI2 conversion\n ALSA: seq: Fix missing bank setup between MIDI1/MIDI2 UMP conversion\n ASoC: SOF: add missing MODULE_DESCRIPTION()\n ASoC: SOF: reorder MODULE_ definitions\n ASoC: SOF: AMD: group all module related information\n ...\n" }, { "commit": "87895a6402604f7a2b55a62e8afd7889b8ec72e4", "tree": "48049d132ba56f021c9256ff55c160ab7c949584", "parents": [ "c6cc9799b4c16b1bd42de35be563d4fa6ea43799", "3050052613790e75b5e4a8536930426b0a8b0774" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 12:03:28 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 12:03:28 2024 -0700" }, "message": "Merge tag \u0027platform-drivers-x86-v6.10-2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86\n\nPull x86 platform driver fixes from Hans de Goede:\n\n - a use-after-free bugfix\n\n - Kconfig fixes for randconfig builds\n\n - allow setting touchscreen_dmi quirks from the cmdline for debugging\n\n - touchscreen_dmi quirks for two new laptop/tablet models\n\n* tag \u0027platform-drivers-x86-v6.10-2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86:\n platform/x86: touchscreen_dmi: Add info for the EZpad 6s Pro\n platform/x86: touchscreen_dmi: Add info for GlobalSpace SolT IVW 11.6\" tablet\n platform/x86: touchscreen_dmi: Add support for setting touchscreen properties from cmdline\n platform/x86: thinkpad_acpi: Select INPUT_SPARSEKMAP in Kconfig\n platform/x86: x86-android-tablets: Add \"select LEDS_CLASS\"\n platform/x86: ISST: fix use-after-free in tpmi_sst_dev_remove()\n" }, { "commit": "c6cc9799b4c16b1bd42de35be563d4fa6ea43799", "tree": "2647b1495c5589037740c9b3c3d5ecdaed3294f5", "parents": [ "ff9bce3d06fbdd12bcc74657516757b66aca9e43", "1d84afaf02524d2558e8ca3ca169be2ef720380b" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 11:52:06 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 11:52:06 2024 -0700" }, "message": "Merge tag \u0027riscv-for-linus-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux\n\nPull RISC-V fixes from Palmer Dabbelt:\n\n - A fix to avoid pt_regs aliasing with idle thread stacks on secondary\n harts.\n\n - HAVE_ARCH_HUGE_VMAP is enabled on XIP kernels, which fixes boot\n issues on XIP systems with huge pages.\n\n - An update to the uABI documentation clarifying that only scalar\n misaligned accesses were grandfathered in as supported, as the vector\n extension did not exist at the time the uABI was frozen.\n\n - A fix for the recently-added byte/half atomics to avoid losing the\n fully ordered decorations.\n\n* tag \u0027riscv-for-linus-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux:\n riscv: Fix fully ordered LR/SC xchg[8|16]() implementations\n Documentation: RISC-V: uabi: Only scalar misaligned loads are supported\n riscv: enable HAVE_ARCH_HUGE_VMAP for XIP kernel\n riscv: prevent pt_regs corruption for secondary idle threads\n" }, { "commit": "ff9bce3d06fbdd12bcc74657516757b66aca9e43", "tree": "c18d066f4295623d8b3f41c661c4f5c91b033b84", "parents": [ "d8ec19857b095b39d114ae299713bd8ea6c1e66a", "7b038b564b3e2a752d2211e7b0c3c29fd2f6e197" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 11:45:41 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri May 31 11:45:41 2024 -0700" }, "message": "Merge tag \u0027bcachefs-2024-05-30\u0027 of https://evilpiepirate.org/git/bcachefs\n\nPull bcachefs fixes from Kent Overstreet:\n \"Assorted odds and ends...\n\n - two downgrade fixes\n\n - a couple snapshot deletion and repair fixes, thanks to noradtux for\n finding these and providing the image to debug them\n\n - a couple assert fixes\n\n - convert to folio helper, from Matthew\n\n - some improved error messages\n\n - bit of code reorganization (just moving things around); doing this\n while things are quiet so I\u0027m not rebasing fixes past reorgs\n\n - don\u0027t return -EROFS on inconsistency error in recovery, this\n confuses util-linux and has it retry the mount\n\n - fix failure to return error on misaligned dio write; reported as an\n issue with coreutils shred\"\n\n* tag \u0027bcachefs-2024-05-30\u0027 of https://evilpiepirate.org/git/bcachefs: (21 commits)\n bcachefs: Fix failure to return error on misaligned dio write\n bcachefs: Don\u0027t return -EROFS from mount on inconsistency error\n bcachefs: Fix uninitialized var warning\n bcachefs: Split out sb-errors_format.h\n bcachefs: Split out journal_seq_blacklist_format.h\n bcachefs: Split out replicas_format.h\n bcachefs: Split out disk_groups_format.h\n bcachefs: split out sb-downgrade_format.h\n bcachefs: split out sb-members_format.h\n bcachefs: Better fsck error message for key version\n bcachefs: btree_gc can now handle unknown btrees\n bcachefs: add missing MODULE_DESCRIPTION()\n bcachefs: Fix setting of downgrade recovery passes/errors\n bcachefs: Run check_key_has_snapshot in snapshot_delete_keys()\n bcachefs: Refactor delete_dead_snapshots()\n bcachefs: Fix locking assert\n bcachefs: Fix lookup_first_inode() when inode_generations are present\n bcachefs: Plumb bkey into __btree_err()\n bcachefs: Use copy_folio_from_iter_atomic()\n bcachefs: Fix sb-downgrade validation\n ...\n" }, { "commit": "0c2f6d04619ec2b53ad4b0b591eafc9389786e86", "tree": "a8e61de9d63e3ba403e29e0716671ed9c97597ad", "parents": [ "2a38e4ca302280fdcce370ba2bee79bac16c4587" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu May 30 17:29:18 2024 +0200" }, "committer": { "name": "Borislav Petkov (AMD)", "email": "bp@alien8.de", "time": "Fri May 31 20:25:56 2024 +0200" }, "message": "x86/topology/intel: Unlock CPUID before evaluating anything\n\nIntel CPUs have a MSR bit to limit CPUID enumeration to leaf two. If\nthis bit is set by the BIOS then CPUID evaluation including topology\nenumeration does not work correctly as the evaluation code does not try\nto analyze any leaf greater than two.\n\nThis went unnoticed before because the original topology code just\nrepeated evaluation several times and managed to overwrite the initial\nlimited information with the correct one later. The new evaluation code\ndoes it once and therefore ends up with the limited and wrong\ninformation.\n\nCure this by unlocking CPUID right before evaluating anything which\ndepends on the maximum CPUID leaf being greater than two instead of\nrereading stuff after unlock.\n\nFixes: 22d63660c35e (\"x86/cpu: Use common topology code for Intel\")\nReported-by: Peter Schneider \u003cpschneider1968@googlemail.com\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Borislav Petkov (AMD) \u003cbp@alien8.de\u003e\nTested-by: Peter Schneider \u003cpschneider1968@googlemail.com\u003e\nCc: \u003cstable@kernel.org\u003e\nLink: https://lore.kernel.org/r/fd3f73dc-a86f-4bcf-9c60-43556a21eb42@googlemail.com\n" }, { "commit": "d551ce15d08114514d489fad63bd275de2aca862", "tree": "44281e27e5e5f234d1b1a24c48a7992669062126", "parents": [ "1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Tue May 28 14:02:35 2024 +0200" }, "committer": { "name": "Jassi Brar", "email": "jassisinghbrar@gmail.com", "time": "Fri May 31 12:39:15 2024 -0500" }, "message": "mailbox: zynqmp-ipi: drop irq_to_desc() call\n\nirq_to_desc() is not exported to loadable modules, so this driver now\nfails to link in some configurations:\n\nERROR: modpost: \"irq_to_desc\" [drivers/mailbox/zynqmp-ipi-mailbox.ko] undefined!\n\nI can\u0027t see a purpose for this call, since the return value is unused\nand probably left over from some code refactoring.\n\nAddress the link failure by just removing the line.\n\nFixes: 6ffb1635341b (\"mailbox: zynqmp: handle SGI for shared IPI\")\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nTested-by: Tanmay Shah \u003ctanmay.shah@amd.com\u003e\nSigned-off-by: Jassi Brar \u003cjassisinghbrar@gmail.com\u003e\n" }, { "commit": "4e173c825b1914d5b118bbf26f0168102d56ae95", "tree": "fa0b76886ba431a82963c9f0014368445d64fcb5", "parents": [ "adb77bba9c664f5d120e0ffb1387e9d7408e1529" ], "author": { "name": "Kees Cook", "email": "kees@kernel.org", "time": "Fri May 31 08:54:52 2024 -0700" }, "committer": { "name": "Kees Cook", "email": "kees@kernel.org", "time": "Fri May 31 08:58:36 2024 -0700" }, "message": "mailmap: update entry for Kees Cook\n\nI\u0027m tired of gmail breaking DKIM. Switch everything over to my\n@kernel.org alias instead.\n\nSigned-off-by: Kees Cook \u003ckees@kernel.org\u003e\n" }, { "commit": "adb77bba9c664f5d120e0ffb1387e9d7408e1529", "tree": "c75ba2e0d292eea7401491fef8cf5b78268c34ad", "parents": [ "1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0" ], "author": { "name": "Kees Cook", "email": "keescook@chromium.org", "time": "Tue Apr 09 19:31:52 2024 -0700" }, "committer": { "name": "Kees Cook", "email": "kees@kernel.org", "time": "Fri May 31 08:58:20 2024 -0700" }, "message": "scsi: mpt3sas: Avoid possible run-time warning with long manufacturer strings\n\nThe prior strscpy() replacement of strncpy() here expected the\nmanufacture_reply strings to be NUL-terminated, but it is possible\nthey are not, as the code pattern here shows, e.g., edev-\u003evendor_id\nbeing exactly 1 character larger than manufacture_reply-\u003evendor_id,\nand the replaced strncpy() was copying only up to the size of the\nsource character array. Replace this with memtostr(), which is the\nunambiguous way to convert a maybe not-NUL-terminated character array\ninto a NUL-terminated string.\n\nFixes: b7e9712a02e8 (\"scsi: mpt3sas: Replace deprecated strncpy() with strscpy()\")\nSigned-off-by: Kees Cook \u003ckeescook@chromium.org\u003e\nTested-by: Marco Patalano \u003cmpatalan@redhat.com\u003e\nReviewed-by: Ewan D. Milne \u003cemilne@redhat.com\u003e\nReviewed-by: Martin K. Petersen \u003cmartin.petersen@oracle.com\u003e\nLink: https://lore.kernel.org/r/20240410023155.2100422-3-keescook@chromium.org\nSigned-off-by: Kees Cook \u003ckees@kernel.org\u003e\n" }, { "commit": "518549c120e671c4906f77d1802b97e9b23f673a", "tree": "32a18d87ef1df63612c23274f429ce654027bce8", "parents": [ "9ee267a29309233b9ef8f58ee61e0b1c9b5879e8" ], "author": { "name": "Steve French", "email": "stfrench@microsoft.com", "time": "Wed May 29 18:16:56 2024 -0500" }, "committer": { "name": "Steve French", "email": "stfrench@microsoft.com", "time": "Fri May 31 10:55:15 2024 -0500" }, "message": "cifs: fix creating sockets when using sfu mount options\n\nWhen running fstest generic/423 with sfu mount option, it\nwas being skipped due to inability to create sockets:\n\n generic/423 [not run] cifs does not support mknod/mkfifo\n\nwhich can also be easily reproduced with their af_unix tool:\n\n ./src/af_unix /mnt1/socket-two bind: Operation not permitted\n\nFix sfu mount option to allow creating and reporting sockets.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Steve French \u003cstfrench@microsoft.com\u003e\n" }, { "commit": "0055f53aac80fd938bf7cdfad7ad414ca6c0e198", "tree": "7e07216209ea7e4bf1f4dff89fe48f138dc073ee", "parents": [ "88da52ccd66e65f2e63a6c35c9dff55d448ef4dc" ], "author": { "name": "Mickaël Salaün", "email": "mic@digikod.net", "time": "Thu May 16 20:19:35 2024 +0200" }, "committer": { "name": "Mickaël Salaün", "email": "mic@digikod.net", "time": "Fri May 31 16:41:54 2024 +0200" }, "message": "selftests/landlock: Add layout1.refer_mount_root\n\nAdd tests to check error codes when linking or renaming a mount root\ndirectory. This previously triggered a kernel warning, but it is fixed\nwith the previous commit.\n\nCc: Günther Noack \u003cgnoack@google.com\u003e\nCc: Paul Moore \u003cpaul@paul-moore.com\u003e\nLink: https://lore.kernel.org/r/20240516181935.1645983-3-mic@digikod.net\nSigned-off-by: Mickaël Salaün \u003cmic@digikod.net\u003e\n" }, { "commit": "88da52ccd66e65f2e63a6c35c9dff55d448ef4dc", "tree": "4308738f019d2b37b3035db93ff5b77cf79b0a6a", "parents": [ "1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0" ], "author": { "name": "Mickaël Salaün", "email": "mic@digikod.net", "time": "Thu May 16 20:19:34 2024 +0200" }, "committer": { "name": "Mickaël Salaün", "email": "mic@digikod.net", "time": "Fri May 31 16:41:52 2024 +0200" }, "message": "landlock: Fix d_parent walk\n\nThe WARN_ON_ONCE() in collect_domain_accesses() can be triggered when\ntrying to link a root mount point. This cannot work in practice because\nthis directory is mounted, but the VFS check is done after the call to\nsecurity_path_link().\n\nDo not use source directory\u0027s d_parent when the source directory is the\nmount point.\n\nCc: Günther Noack \u003cgnoack@google.com\u003e\nCc: Paul Moore \u003cpaul@paul-moore.com\u003e\nCc: stable@vger.kernel.org\nReported-by: syzbot+bf4903dc7e12b18ebc87@syzkaller.appspotmail.com\nFixes: b91c3e4ea756 (\"landlock: Add support for file reparenting with LANDLOCK_ACCESS_FS_REFER\")\nCloses: https://lore.kernel.org/r/000000000000553d3f0618198200@google.com\nLink: https://lore.kernel.org/r/20240516181935.1645983-2-mic@digikod.net\n[mic: Fix commit message]\nSigned-off-by: Mickaël Salaün \u003cmic@digikod.net\u003e\n" }, { "commit": "3cb648c4dd3e8dde800fb3659250ed11f2d9efa5", "tree": "b7fdd1f9108826d0f8227aac9eb4ad23aceb59a7", "parents": [ "473880369304cfd4445720cdd8bae4c6f1e16e60" ], "author": { "name": "Niklas Cassel", "email": "cassel@kernel.org", "time": "Thu May 30 23:27:04 2024 +0200" }, "committer": { "name": "Niklas Cassel", "email": "cassel@kernel.org", "time": "Fri May 31 15:14:06 2024 +0200" }, "message": "ata: libata-core: Add ATA_HORKAGE_NOLPM for Apacer AS340\n\nCommit 7627a0edef54 (\"ata: ahci: Drop low power policy board type\")\ndropped the board_ahci_low_power board type, and instead enables LPM if:\n-The AHCI controller reports that it supports LPM (Partial/Slumber), and\n-CONFIG_SATA_MOBILE_LPM_POLICY !\u003d 0, and\n-The port is not defined as external in the per port PxCMD register, and\n-The port is not defined as hotplug capable in the per port PxCMD\n register.\n\nPartial and Slumber LPM states can either be initiated by HIPM or DIPM.\n\nFor HIPM (host initiated power management) to get enabled, both the AHCI\ncontroller and the drive have to report that they support HIPM.\n\nFor DIPM (device initiated power management) to get enabled, only the\ndrive has to report that it supports DIPM. However, the HBA will reject\ndevice requests to enter LPM states which the HBA does not support.\n\nThe problem is that Apacer AS340 drives do not handle low power modes\ncorrectly. The problem was most likely not seen before because no one\nhad used this drive with a AHCI controller with LPM enabled.\n\nAdd a quirk so that we do not enable LPM for this drive, since we see\ncommand timeouts if we do (even though the drive claims to support DIPM).\n\nFixes: 7627a0edef54 (\"ata: ahci: Drop low power policy board type\")\nCc: stable@vger.kernel.org\nReported-by: Tim Teichmann \u003cteichmanntim@outlook.de\u003e\nCloses: https://lore.kernel.org/linux-ide/87bk4pbve8.ffs@tglx/\nReviewed-by: Mika Westerberg \u003cmika.westerberg@linux.intel.com\u003e\nReviewed-by: Damien Le Moal \u003cdlemoal@kernel.org\u003e\nSigned-off-by: Niklas Cassel \u003ccassel@kernel.org\u003e\n" }, { "commit": "473880369304cfd4445720cdd8bae4c6f1e16e60", "tree": "ba90ab1d5a64b7493a079c319ebf0d1e90dde935", "parents": [ "86aaa7e9d641c1ad1035ed2df88b8d0b48c86b30" ], "author": { "name": "Niklas Cassel", "email": "cassel@kernel.org", "time": "Thu May 30 23:32:44 2024 +0200" }, "committer": { "name": "Niklas Cassel", "email": "cassel@kernel.org", "time": "Fri May 31 15:11:51 2024 +0200" }, "message": "ata: libata-core: Add ATA_HORKAGE_NOLPM for AMD Radeon S3 SSD\n\nCommit 7627a0edef54 (\"ata: ahci: Drop low power policy board type\")\ndropped the board_ahci_low_power board type, and instead enables LPM if:\n-The AHCI controller reports that it supports LPM (Partial/Slumber), and\n-CONFIG_SATA_MOBILE_LPM_POLICY !\u003d 0, and\n-The port is not defined as external in the per port PxCMD register, and\n-The port is not defined as hotplug capable in the per port PxCMD\n register.\n\nPartial and Slumber LPM states can either be initiated by HIPM or DIPM.\n\nFor HIPM (host initiated power management) to get enabled, both the AHCI\ncontroller and the drive have to report that they support HIPM.\n\nFor DIPM (device initiated power management) to get enabled, only the\ndrive has to report that it supports DIPM. However, the HBA will reject\ndevice requests to enter LPM states which the HBA does not support.\n\nThe problem is that AMD Radeon S3 SSD drives do not handle low power modes\ncorrectly. The problem was most likely not seen before because no one\nhad used this drive with a AHCI controller with LPM enabled.\n\nAdd a quirk so that we do not enable LPM for this drive, since we see\ncommand timeouts if we do (even though the drive claims to support both\nHIPM and DIPM).\n\nFixes: 7627a0edef54 (\"ata: ahci: Drop low power policy board type\")\nCc: stable@vger.kernel.org\nReported-by: Doru Iorgulescu \u003cdoru.iorgulescu1@gmail.com\u003e\nCloses: https://bugzilla.kernel.org/show_bug.cgi?id\u003d218832\nReviewed-by: Mika Westerberg \u003cmika.westerberg@linux.intel.com\u003e\nReviewed-by: Damien Le Moal \u003cdlemoal@kernel.org\u003e\nSigned-off-by: Niklas Cassel \u003ccassel@kernel.org\u003e\n" }, { "commit": "86aaa7e9d641c1ad1035ed2df88b8d0b48c86b30", "tree": "20b6fcd472216db1f00adae0b35c2bfbb7b49397", "parents": [ "9e2f46cd87473c70d01fcaf8a559809e6d18dd50" ], "author": { "name": "Niklas Cassel", "email": "cassel@kernel.org", "time": "Thu May 30 23:28:17 2024 +0200" }, "committer": { "name": "Niklas Cassel", "email": "cassel@kernel.org", "time": "Fri May 31 15:10:41 2024 +0200" }, "message": "ata: libata-core: Add ATA_HORKAGE_NOLPM for Crucial CT240BX500SSD1\n\nCommit 7627a0edef54 (\"ata: ahci: Drop low power policy board type\")\ndropped the board_ahci_low_power board type, and instead enables LPM if:\n-The AHCI controller reports that it supports LPM (Partial/Slumber), and\n-CONFIG_SATA_MOBILE_LPM_POLICY !\u003d 0, and\n-The port is not defined as external in the per port PxCMD register, and\n-The port is not defined as hotplug capable in the per port PxCMD\n register.\n\nPartial and Slumber LPM states can either be initiated by HIPM or DIPM.\n\nFor HIPM (host initiated power management) to get enabled, both the AHCI\ncontroller and the drive have to report that they support HIPM.\n\nFor DIPM (device initiated power management) to get enabled, only the\ndrive has to report that it supports DIPM. However, the HBA will reject\ndevice requests to enter LPM states which the HBA does not support.\n\nThe problem is that Crucial CT240BX500SSD1 drives do not handle low power\nmodes correctly. The problem was most likely not seen before because no\none had used this drive with a AHCI controller with LPM enabled.\n\nAdd a quirk so that we do not enable LPM for this drive, since we see\ncommand timeouts if we do (even though the drive claims to support DIPM).\n\nFixes: 7627a0edef54 (\"ata: ahci: Drop low power policy board type\")\nCc: stable@vger.kernel.org\nReported-by: Aarrayy \u003clp610mh@gmail.com\u003e\nCloses: https://bugzilla.kernel.org/show_bug.cgi?id\u003d218832\nReviewed-by: Mika Westerberg \u003cmika.westerberg@linux.intel.com\u003e\nReviewed-by: Damien Le Moal \u003cdlemoal@kernel.org\u003e\nSigned-off-by: Niklas Cassel \u003ccassel@kernel.org\u003e\n" }, { "commit": "d40605a6823577a6c40fad6fb1f10a40ea0389d7", "tree": "9194e8875efbd49abc7d83c713618b8ca682cf47", "parents": [ "49217ea147df7647cb89161b805c797487783fc0" ], "author": { "name": "Phil Auld", "email": "pauld@redhat.com", "time": "Thu May 30 14:15:48 2024 -0400" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Fri May 31 11:48:42 2024 +0200" }, "message": "sched/x86: Export \u0027percpu arch_freq_scale\u0027\n\nCommit:\n\n 7bc263840bc3 (\"sched/topology: Consolidate and clean up access to a CPU\u0027s max compute capacity\")\n\nremoved rq-\u003ecpu_capacity_orig in favor of using arch_scale_freq_capacity()\ncalls. Export the underlying percpu symbol on x86 so that external trace\npoint helper modules can be made to work again.\n\nSigned-off-by: Phil Auld \u003cpauld@redhat.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nLink: https://lore.kernel.org/r/20240530181548.2039216-1-pauld@redhat.com\n" }, { "commit": "dc8e5dfb52d56e955ad09174330252710845b8d2", "tree": "8c7455bf9555d5253d2359077c014dba125292d4", "parents": [ "0a44078f2b72abcdda47581c942bd5d0468ec50b" ], "author": { "name": "Jeff Johnson", "email": "quic_jjohnson@quicinc.com", "time": "Thu May 30 13:42:51 2024 -0700" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Fri May 31 11:41:15 2024 +0200" }, "message": "perf/x86/intel: Add missing MODULE_DESCRIPTION() lines\n\nFix the \u0027make W\u003d1 C\u003d1\u0027 warnings:\n\n WARNING: modpost: missing MODULE_DESCRIPTION() in arch/x86/events/intel/intel-uncore.o\n WARNING: modpost: missing MODULE_DESCRIPTION() in arch/x86/events/intel/intel-cstate.o\n\nSigned-off-by: Jeff Johnson \u003cquic_jjohnson@quicinc.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nCc: Arnaldo Carvalho de Melo \u003cacme@kernel.org\u003e\nCc: Alexander Shishkin \u003calexander.shishkin@linux.intel.com\u003e\nLink: https://lore.kernel.org/r/20240530-md-arch-x86-events-intel-v1-1-8252194ed20a@quicinc.com\n" }, { "commit": "0a44078f2b72abcdda47581c942bd5d0468ec50b", "tree": "1355a3c76a19c0157c966f39399eb69a14e5efe5", "parents": [ "4a4be1ad3a6efea16c56615f31117590fd881358" ], "author": { "name": "Jeff Johnson", "email": "quic_jjohnson@quicinc.com", "time": "Thu May 30 13:12:03 2024 -0700" }, "committer": { "name": "Ingo Molnar", "email": "mingo@kernel.org", "time": "Fri May 31 11:41:04 2024 +0200" }, "message": "perf/x86/rapl: Add missing MODULE_DESCRIPTION() line\n\nFix the warning from \u0027make C\u003d1 W\u003d1\u0027:\n\n WARNING: modpost: missing MODULE_DESCRIPTION() in arch/x86/events/rapl.o\n\nSigned-off-by: Jeff Johnson \u003cquic_jjohnson@quicinc.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nCc: Arnaldo Carvalho de Melo \u003cacme@kernel.org\u003e\nCc: Alexander Shishkin \u003calexander.shishkin@linux.intel.com\u003e\nLink: https://lore.kernel.org/r/20240530-md-arch-x86-events-v1-1-e45ffa8af99f@quicinc.com\n" }, { "commit": "310fa3ec2859f1c094e6e9b5d2e1ca51738c409a", "tree": "e07283af203232b507ba7c29b9777cac9aeaabf3", "parents": [ "e1e287e6f9de7e43716438f4c131eeb4a0be65b7" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Fri May 31 09:51:07 2024 +0200" }, "committer": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Fri May 31 09:51:44 2024 +0200" }, "message": "ALSA: seq: ump: Fix swapped song position pointer data\n\nAt converting between the legacy event and UMP, the parameters for\nMIDI Song Position Pointer are incorrectly stored. It should have\nbeen LSB -\u003e MSB order while it stored in MSB -\u003e LSB order.\nThis patch corrects the ordering.\n\nFixes: e9e02819a98a (\"ALSA: seq: Automatic conversion of UMP events\")\nLink: https://lore.kernel.org/r/20240531075110.3250-1-tiwai@suse.de\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\n" }, { "commit": "c66f3b40b17d3dfc4b6abb5efde8e71c46971821", "tree": "016fa247d396de2b5c36ebef789aadc21cf4c2cf", "parents": [ "2d707b4e37f9b0c37b8b2392f91b04c5b63ea538" ], "author": { "name": "Quan Zhou", "email": "zhouquan@iscas.ac.cn", "time": "Thu May 23 10:13:34 2024 +0800" }, "committer": { "name": "Anup Patel", "email": "anup@brainfault.org", "time": "Fri May 31 10:40:39 2024 +0530" }, "message": "RISC-V: KVM: Fix incorrect reg_subtype labels in kvm_riscv_vcpu_set_reg_isa_ext function\n\nIn the function kvm_riscv_vcpu_set_reg_isa_ext, the original code\nused incorrect reg_subtype labels KVM_REG_RISCV_SBI_MULTI_EN/DIS.\nThese have been corrected to KVM_REG_RISCV_ISA_MULTI_EN/DIS respectively.\nAlthough they are numerically equivalent, the actual processing\nwill not result in errors, but it may lead to ambiguous code semantics.\n\nFixes: 613029442a4b (\"RISC-V: KVM: Extend ONE_REG to enable/disable multiple ISA extensions\")\nSigned-off-by: Quan Zhou \u003czhouquan@iscas.ac.cn\u003e\nReviewed-by: Andrew Jones \u003cajones@ventanamicro.com\u003e\nLink: https://lore.kernel.org/r/ff1c6771a67d660db94372ac9aaa40f51e5e0090.1716429371.git.zhouquan@iscas.ac.cn\nSigned-off-by: Anup Patel \u003canup@brainfault.org\u003e\n" }, { "commit": "2d707b4e37f9b0c37b8b2392f91b04c5b63ea538", "tree": "37df8d23932561926ad6acda8ebad1161a18cda8", "parents": [ "1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0" ], "author": { "name": "Yong-Xuan Wang", "email": "yongxuan.wang@sifive.com", "time": "Mon Apr 15 14:49:04 2024 +0800" }, "committer": { "name": "Anup Patel", "email": "anup@brainfault.org", "time": "Fri May 31 09:47:08 2024 +0530" }, "message": "RISC-V: KVM: No need to use mask when hart-index-bit is 0\n\nWhen the maximum hart number within groups is 1, hart-index-bit is set to\n0. Consequently, there is no need to restore the hart ID from IMSIC\naddresses and hart-index-bit settings. Currently, QEMU and kvmtool do not\npass correct hart-index-bit values when the maximum hart number is a\npower of 2, thereby avoiding this issue. Corresponding patches for QEMU\nand kvmtool will also be dispatched.\n\nFixes: 89d01306e34d (\"RISC-V: KVM: Implement device interface for AIA irqchip\")\nSigned-off-by: Yong-Xuan Wang \u003cyongxuan.wang@sifive.com\u003e\nReviewed-by: Andrew Jones \u003cajones@ventanamicro.com\u003e\nLink: https://lore.kernel.org/r/20240415064905.25184-1-yongxuan.wang@sifive.com\nSigned-off-by: Anup Patel \u003canup@brainfault.org\u003e\n" }, { "commit": "a2ce3f7752bfbb47e659574fc2e1e6942bca3c29", "tree": "f816b99784348e731003be5f95fcfdff51cb8f50", "parents": [ "bb61cf46b66a875bc30b930f7ccf93fa8c8a1797", "bb195358806847217efba98de62b7decec3b371f" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri May 31 10:08:52 2024 +1000" }, "committer": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri May 31 11:51:20 2024 +1000" }, "message": "Merge tag \u0027drm-misc-fixes-2024-05-30\u0027 of https://gitlab.freedesktop.org/drm/misc/kernel into drm-fixes\n\nShort summary of fixes pull:\n\ndma-buf:\n- sw-sync: Don\u0027t interfere with IRQ handling\n- Fix kthreads-handling error path\n\ngem-shmem:\n- Warn when trying to pin imported objects\n\nlima:\n- Fix dma_resv-related deadlock in object pin\n\nmsm:\n- Remove build-time dependency on Python 3.9\n\nnouveau:\n- nvif: Fix possible integer overflow\n\npanel:\n- lg-sw43408: Select DP helpers; Declare backlight ops as static\n- sitronix-st7789v: Various fixes for jt240mhqs_hwt_ek_e3 panel\n\npanfrost:\n- Fix dma_resv-related deadlock in object pin\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\n\nFrom: Thomas Zimmermann \u003ctzimmermann@suse.de\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20240530192307.GA14809@localhost.localdomain\n" }, { "commit": "0a751df4566c86e5a24f2a03290dad3d0f215692", "tree": "509cf43e62385c6eaca53c9b9715ed3a6c4fbb06", "parents": [ "29459c3eaa5c6261fbe0dea7bdeb9b48d35d862a" ], "author": { "name": "Waiman Long", "email": "longman@redhat.com", "time": "Thu May 30 09:45:47 2024 -0400" }, "committer": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Thu May 30 19:44:29 2024 -0600" }, "message": "blk-throttle: Fix incorrect display of io.max\n\nCommit bf20ab538c81 (\"blk-throttle: remove CONFIG_BLK_DEV_THROTTLING_LOW\")\nattempts to revert the code change introduced by commit cd5ab1b0fcb4\n(\"blk-throttle: add .low interface\"). However, it leaves behind the\nbps_conf[] and iops_conf[] fields in the throtl_grp structure which\naren\u0027t set anywhere in the new blk-throttle.c code but are still being\nused by tg_prfill_limit() to display the limits in io.max. Now io.max\nalways displays the following values if a block queue is used:\n\n\t\u003cm\u003e:\u003cn\u003e rbps\u003d0 wbps\u003d0 riops\u003d0 wiops\u003d0\n\nFix this problem by removing bps_conf[] and iops_conf[] and use bps[]\nand iops[] instead to complete the revert.\n\nFixes: bf20ab538c81 (\"blk-throttle: remove CONFIG_BLK_DEV_THROTTLING_LOW\")\nReported-by: Justin Forbes \u003cjforbes@redhat.com\u003e\nCloses: https://github.com/containers/podman/issues/22701#issuecomment-2120627789\nSigned-off-by: Waiman Long \u003clongman@redhat.com\u003e\nAcked-by: Tejun Heo \u003ctj@kernel.org\u003e\nReviewed-by: Yu Kuai \u003cyukuai3@huawei.com\u003e\nLink: https://lore.kernel.org/r/20240530134547.970075-1-longman@redhat.com\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "bb61cf46b66a875bc30b930f7ccf93fa8c8a1797", "tree": "07c620a0679dd9f9cea7b9a2f81e8f3276ecba3e", "parents": [ "c301c3d2acb3eddcf79b9755633801f7c6d9e840", "67c7d4fa267bcfe8d68fb36d938e3c6e0912b57d" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri May 31 08:38:04 2024 +1000" }, "committer": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri May 31 08:38:15 2024 +1000" }, "message": "Merge tag \u0027amd-drm-fixes-6.10-2024-05-30\u0027 of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes\n\namd-drm-fixes-6.10-2024-05-30:\n\namdgpu:\n- RAS fix\n- Fix colorspace property for MST connectors\n- Fix for PCIe DPM\n- Silence UBSAN warning\n- GPUVM robustness fix\n- Partition fix\n- Drop deprecated I2C_CLASS_SPD\n\namdkfd:\n- Revert unused changes for certain 11.0.3 devices\n- Simplify APU VRAM handling\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\n\nFrom: Alex Deucher \u003calexander.deucher@amd.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20240530202316.2246826-1-alexander.deucher@amd.com\n" }, { "commit": "c301c3d2acb3eddcf79b9755633801f7c6d9e840", "tree": "5b492099e71a829a8bb00e26b92bb0e5241aeeab", "parents": [ "cfd36ae37c490b88058e0a220e16edd8bfd126c7", "6c5cd0807c79eb4c0cda70b48f6be668a241d584" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri May 31 08:32:58 2024 +1000" }, "committer": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri May 31 08:33:13 2024 +1000" }, "message": "Merge tag \u0027drm-xe-fixes-2024-05-30\u0027 of https://gitlab.freedesktop.org/drm/xe/kernel into drm-fixes\n\nDriver Changes:\n- One pcode polling timeout change\n- One fix for deadlocks for faulting VMs\n- One error-path lock imbalance fix\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\n\nFrom: Thomas Hellstrom \u003cthomas.hellstrom@linux.intel.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/ZlisNHzgoq9nVg6g@fedora\n" }, { "commit": "cfd36ae37c490b88058e0a220e16edd8bfd126c7", "tree": "81075efb53cc85aa2e92b117d930136b965d5d18", "parents": [ "3e049b6b8f32f25c6967f4cffd8eac6e1e5316f6", "75800e2e4203ea83bbc9d4f63ad97ea582244a08" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri May 31 08:18:17 2024 +1000" }, "committer": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Fri May 31 08:18:18 2024 +1000" }, "message": "Merge tag \u0027drm-intel-fixes-2024-05-30\u0027 of https://gitlab.freedesktop.org/drm/i915/kernel into drm-fixes\n\ndrm/i915 fixes for v6.10-rc2:\n- Fix a race in audio component by registering it later\n- Make DPT object unshrinkable to avoid shrinking when framebuffer has\n not shrunk\n- Fix CCS id calculation to fix a perf regression\n- Fix selftest caching mode\n- Fix FIELD_PREP compiler warnings\n- Fix indefinite wait for GT wakeref release\n- Revert overeager multi-gt pm reference removal\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nFrom: Jani Nikula \u003cjani.nikula@intel.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/87a5k7iwod.fsf@intel.com\n" }, { "commit": "29459c3eaa5c6261fbe0dea7bdeb9b48d35d862a", "tree": "212eb2b7e2c0742ac77ceecf9635a323ded7e78a", "parents": [ "cd6399936869b4a042dd1270078cbf2bb871a407" ], "author": { "name": "Damien Le Moal", "email": "dlemoal@kernel.org", "time": "Thu May 30 14:40:34 2024 +0900" }, "committer": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Thu May 30 15:03:52 2024 -0600" }, "message": "block: Fix zone write plugging handling of devices with a runt zone\n\nA zoned device may have a last sequential write required zone that is\nsmaller than other zones. However, all tests to check if a zone write\nplug write offset exceeds the zone capacity use the same capacity\nvalue stored in the gendisk zone_capacity field. This is incorrect for a\nzoned device with a last runt (smaller) zone.\n\nAdd the new field last_zone_capacity to struct gendisk to store the\ncapacity of the last zone of the device. blk_revalidate_seq_zone() and\nblk_revalidate_conv_zone() are both modified to get this value when\ndisk_zone_is_last() returns true. Similarly to zone_capacity, the value\nis first stored using the last_zone_capacity field of struct\nblk_revalidate_zone_args. Once zone revalidation of all zones is done,\nthis is used to set the gendisk last_zone_capacity field.\n\nThe checks to determine if a zone is full or if a sector offset in a\nzone exceeds the zone capacity in disk_should_remove_zone_wplug(),\ndisk_zone_wplug_abort_unaligned(), blk_zone_write_plug_init_request(),\nand blk_zone_wplug_prepare_bio() are modified to use the new helper\nfunctions disk_zone_is_full() and disk_zone_wplug_is_full().\ndisk_zone_is_full() uses the zone index to determine if the zone being\ntested is the last one of the disk and uses the either the disk\nzone_capacity or last_zone_capacity accordingly.\n\nFixes: dd291d77cc90 (\"block: Introduce zone write plugging\")\nSigned-off-by: Damien Le Moal \u003cdlemoal@kernel.org\u003e\nReviewed-by: Bart Van Assche \u003cbvanassche@acm.org\u003e\nReviewed-by: Niklas Cassel \u003ccassel@kernel.org\u003e\nLink: https://lore.kernel.org/r/20240530054035.491497-4-dlemoal@kernel.org\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "cd6399936869b4a042dd1270078cbf2bb871a407", "tree": "5636b77e8bfd0b8f2a8bdc8dd5bc395f3204f1a0", "parents": [ "b164316808ec5de391c3e7b0148ec937d32d280d" ], "author": { "name": "Damien Le Moal", "email": "dlemoal@kernel.org", "time": "Thu May 30 14:40:33 2024 +0900" }, "committer": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Thu May 30 15:03:52 2024 -0600" }, "message": "block: Fix validation of zoned device with a runt zone\n\nCommit ecfe43b11b02 (\"block: Remember zone capacity when revalidating\nzones\") introduced checks to ensure that the capacity of the zones of\na zoned device is constant for all zones. However, this check ignores\nthe possibility that a zoned device has a smaller last zone with a size\nnot equal to the capacity of other zones. Such device correspond in\npractice to an SMR drive with a smaller last zone and all zones with a\ncapacity equal to the zone size, leading to the last zone capacity being\ndifferent than the capacity of other zones.\n\nCorrectly handle such device by fixing the check for the constant zone\ncapacity in blk_revalidate_seq_zone() using the new helper function\ndisk_zone_is_last(). This helper function is also used in\nblk_revalidate_zone_cb() when checking the zone size.\n\nFixes: ecfe43b11b02 (\"block: Remember zone capacity when revalidating zones\")\nSigned-off-by: Damien Le Moal \u003cdlemoal@kernel.org\u003e\nReviewed-by: Bart Van Assche \u003cbvanassche@acm.org\u003e\nReviewed-by: Niklas Cassel \u003ccassel@kernel.org\u003e\nLink: https://lore.kernel.org/r/20240530054035.491497-3-dlemoal@kernel.org\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "b164316808ec5de391c3e7b0148ec937d32d280d", "tree": "7a4979ebc03838d7c68c6df3db9f18d3c5dd8659", "parents": [ "1521dc2410837222e8f0211b8e76898880c4d263" ], "author": { "name": "Damien Le Moal", "email": "dlemoal@kernel.org", "time": "Thu May 30 14:40:32 2024 +0900" }, "committer": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Thu May 30 15:03:52 2024 -0600" }, "message": "null_blk: Do not allow runt zone with zone capacity smaller then zone size\n\nA zoned device with a smaller last zone together with a zone capacity\nsmaller than the zone size does make any sense as that does not\ncorrespond to any possible setup for a real device:\n1) For ZNS and zoned UFS devices, all zones are always the same size.\n2) For SMR HDDs, all zones always have the same capacity.\nIn other words, if we have a smaller last runt zone, then this zone\ncapacity should always be equal to the zone size.\n\nAdd a check in null_init_zoned_dev() to prevent a configuration to have\nboth a smaller zone size and a zone capacity smaller than the zone size.\n\nSigned-off-by: Damien Le Moal \u003cdlemoal@kernel.org\u003e\nReviewed-by: Niklas Cassel \u003ccassel@kernel.org\u003e\nReviewed-by: Bart Van Assche \u003cbvanassche@acm.org\u003e\nLink: https://lore.kernel.org/r/20240530054035.491497-2-dlemoal@kernel.org\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "18414a4a2eabb0281d12d374c92874327e0e3fe3", "tree": "4cda8f7e4b849de75474873e9a267c4f67c0ce62", "parents": [ "e112311615a24e1618a591c73506571dc304eb8d" ], "author": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Thu May 30 13:35:50 2024 -0600" }, "committer": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Thu May 30 14:04:37 2024 -0600" }, "message": "io_uring/net: assign kmsg inq/flags before buffer selection\n\nsyzbot reports that recv is using an uninitialized value:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nBUG: KMSAN: uninit-value in io_req_cqe_overflow io_uring/io_uring.c:810 [inline]\nBUG: KMSAN: uninit-value in io_req_complete_post io_uring/io_uring.c:937 [inline]\nBUG: KMSAN: uninit-value in io_issue_sqe+0x1f1b/0x22c0 io_uring/io_uring.c:1763\n io_req_cqe_overflow io_uring/io_uring.c:810 [inline]\n io_req_complete_post io_uring/io_uring.c:937 [inline]\n io_issue_sqe+0x1f1b/0x22c0 io_uring/io_uring.c:1763\n io_wq_submit_work+0xa17/0xeb0 io_uring/io_uring.c:1860\n io_worker_handle_work+0xc04/0x2000 io_uring/io-wq.c:597\n io_wq_worker+0x447/0x1410 io_uring/io-wq.c:651\n ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:147\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244\n\nUninit was stored to memory at:\n io_req_set_res io_uring/io_uring.h:215 [inline]\n io_recv_finish+0xf10/0x1560 io_uring/net.c:861\n io_recv+0x12ec/0x1ea0 io_uring/net.c:1175\n io_issue_sqe+0x429/0x22c0 io_uring/io_uring.c:1751\n io_wq_submit_work+0xa17/0xeb0 io_uring/io_uring.c:1860\n io_worker_handle_work+0xc04/0x2000 io_uring/io-wq.c:597\n io_wq_worker+0x447/0x1410 io_uring/io-wq.c:651\n ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:147\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244\n\nUninit was created at:\n slab_post_alloc_hook mm/slub.c:3877 [inline]\n slab_alloc_node mm/slub.c:3918 [inline]\n __do_kmalloc_node mm/slub.c:4038 [inline]\n __kmalloc+0x6e4/0x1060 mm/slub.c:4052\n kmalloc include/linux/slab.h:632 [inline]\n io_alloc_async_data+0xc0/0x220 io_uring/io_uring.c:1662\n io_msg_alloc_async io_uring/net.c:166 [inline]\n io_recvmsg_prep_setup io_uring/net.c:725 [inline]\n io_recvmsg_prep+0xbe8/0x1a20 io_uring/net.c:806\n io_init_req io_uring/io_uring.c:2135 [inline]\n io_submit_sqe io_uring/io_uring.c:2182 [inline]\n io_submit_sqes+0x1135/0x2f10 io_uring/io_uring.c:2335\n __do_sys_io_uring_enter io_uring/io_uring.c:3246 [inline]\n __se_sys_io_uring_enter+0x40f/0x3c80 io_uring/io_uring.c:3183\n __x64_sys_io_uring_enter+0x11f/0x1a0 io_uring/io_uring.c:3183\n x64_sys_call+0x2c0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:427\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nwhich appears to be io_recv_finish() reading kmsg-\u003emsg.msg_inq to decide\nif it needs to set IORING_CQE_F_SOCK_NONEMPTY or not. If the recv is\nentered with buffer selection, but no buffer is available, then we jump\nerror path which calls io_recv_finish() without having assigned\nkmsg-\u003emsg_inq. This might cause an errant setting of the NONEMPTY flag\nfor a request get gets errored with -ENOBUFS.\n\nReported-by: syzbot+b1647099e82b3b349fbf@syzkaller.appspotmail.com\nFixes: 4a3223f7bfda (\"io_uring/net: switch io_recv() to using io_async_msghdr\")\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "e1e287e6f9de7e43716438f4c131eeb4a0be65b7", "tree": "7d812ab8f3b3819f40cf838b31c3c2f1597626ee", "parents": [ "700fe6fd093d08c6da2bda8efe00479b0e617327", "c85578e730135d47271ca874e4436dd87e87f252" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Thu May 30 21:26:19 2024 +0200" }, "committer": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Thu May 30 21:26:19 2024 +0200" }, "message": "Merge tag \u0027asoc-fix-v6.10-rc1\u0027 of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus\n\nASoC: Fixes for v6.10\n\nSeveral serieses of fixes that have come in since the merge window,\nmostly for Intel systems. The biggest thing is some updates from Peter\nwhich fix support for a series of Intel laptops which have been found to\nuse 16 bit rather than 32 bit DMIC configuration blobs in their firmware\ndescriptions. We also have a bunch of fixes for module annotations, and\nsome smaller single patch fixes.\n" }, { "commit": "bb195358806847217efba98de62b7decec3b371f", "tree": "9495a764d626daf93490c81e4d4b2ef5cd36edbf", "parents": [ "b62c150c3bae72ac1910dcc588f360159eb0744a" ], "author": { "name": "Abhinav Kumar", "email": "quic_abhinavk@quicinc.com", "time": "Tue May 07 16:04:40 2024 -0700" }, "committer": { "name": "Thierry Reding", "email": "treding@nvidia.com", "time": "Thu May 30 18:49:23 2024 +0200" }, "message": "drm/msm: remove python 3.9 dependency for compiling msm\n\nSince commit 5acf49119630 (\"drm/msm: import gen_header.py script from Mesa\"),\ncompilation is broken on machines having python versions older than 3.9\ndue to dependency on argparse.BooleanOptionalAction.\n\nSwitch to use simple bool for the validate flag to remove the dependency.\n\nFixes: 5acf49119630 (\"drm/msm: import gen_header.py script from Mesa\")\nSigned-off-by: Abhinav Kumar \u003cquic_abhinavk@quicinc.com\u003e\nTested-by: Douglas Anderson \u003cdianders@chromium.org\u003e\nReviewed-by: Dmitry Baryshkov \u003cdmitry.baryshkov@linaro.org\u003e\nSigned-off-by: Thierry Reding \u003ctreding@nvidia.com\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20240507230440.3384949-1-quic_abhinavk@quicinc.com\n" }, { "commit": "1d84afaf02524d2558e8ca3ca169be2ef720380b", "tree": "2beb818750ca19a1ee3093832f2105d03b1b9efc", "parents": [ "982a7eb97be685d1129c06671aed4c26d6919af4" ], "author": { "name": "Alexandre Ghiti", "email": "alexghiti@rivosinc.com", "time": "Thu May 30 16:55:46 2024 +0200" }, "committer": { "name": "Palmer Dabbelt", "email": "palmer@rivosinc.com", "time": "Thu May 30 09:43:14 2024 -0700" }, "message": "riscv: Fix fully ordered LR/SC xchg[8|16]() implementations\n\nThe fully ordered versions of xchg[8|16]() using LR/SC lack the\nnecessary memory barriers to guarantee the order.\n\nFix this by matching what is already implemented in the fully ordered\nversions of cmpxchg() using LR/SC.\n\nSuggested-by: Andrea Parri \u003cparri.andrea@gmail.com\u003e\nReported-by: Andrea Parri \u003cparri.andrea@gmail.com\u003e\nCloses: https://lore.kernel.org/linux-riscv/ZlYbupL5XgzgA0MX@andrea/T/#u\nFixes: a8ed2b7a2c13 (\"riscv/cmpxchg: Implement xchg for variables of size 1 and 2\")\nSigned-off-by: Alexandre Ghiti \u003calexghiti@rivosinc.com\u003e\nReviewed-by: Andrea Parri \u003cparri.andrea@gmail.com\u003e\nLink: https://lore.kernel.org/r/20240530145546.394248-1-alexghiti@rivosinc.com\nSigned-off-by: Palmer Dabbelt \u003cpalmer@rivosinc.com\u003e\n" }, { "commit": "982a7eb97be685d1129c06671aed4c26d6919af4", "tree": "84600d6540ddfe5443e630b59d67cb1edb37cfe6", "parents": [ "7bed51617401dab2be930b13ed5aacf581f7c8ef" ], "author": { "name": "Palmer Dabbelt", "email": "palmer@rivosinc.com", "time": "Fri May 24 11:56:00 2024 -0700" }, "committer": { "name": "Palmer Dabbelt", "email": "palmer@rivosinc.com", "time": "Thu May 30 09:42:53 2024 -0700" }, "message": "Documentation: RISC-V: uabi: Only scalar misaligned loads are supported\n\nWe\u0027re stuck supporting scalar misaligned loads in userspace because they\nwere part of the ISA at the time we froze the uABI. That wasn\u0027t the\ncase for vector misaligned accesses, so depending on them\nunconditionally is a userspace bug. All extant vector hardware traps on\nthese misaligned accesses.\n\nReviewed-by: Conor Dooley \u003cconor.dooley@microchip.com\u003e\nLink: https://lore.kernel.org/r/20240524185600.5919-1-palmer@rivosinc.com\nSigned-off-by: Palmer Dabbelt \u003cpalmer@rivosinc.com\u003e\n" }, { "commit": "7bed51617401dab2be930b13ed5aacf581f7c8ef", "tree": "916ab0ce2a66d0baf806a5471db55b4d2e01dbf6", "parents": [ "a638b0461b58aa3205cd9d5f14d6f703d795b4af" ], "author": { "name": "Nam Cao", "email": "namcao@linutronix.de", "time": "Sun May 26 13:01:04 2024 +0200" }, "committer": { "name": "Palmer Dabbelt", "email": "palmer@rivosinc.com", "time": "Thu May 30 09:42:52 2024 -0700" }, "message": "riscv: enable HAVE_ARCH_HUGE_VMAP for XIP kernel\n\nHAVE_ARCH_HUGE_VMAP also works on XIP kernel, so remove its dependency on\n!XIP_KERNEL.\n\nThis also fixes a boot problem for XIP kernel introduced by the commit in\n\"Fixes:\". This commit used huge page mapping for vmemmap, but huge page\nvmap was not enabled for XIP kernel.\n\nFixes: ff172d4818ad (\"riscv: Use hugepage mappings for vmemmap\")\nSigned-off-by: Nam Cao \u003cnamcao@linutronix.de\u003e\nCc: \u003cstable@vger.kernel.org\u003e\nReviewed-by: Alexandre Ghiti \u003calexghiti@rivosinc.com\u003e\nLink: https://lore.kernel.org/r/20240526110104.470429-1-namcao@linutronix.de\nSigned-off-by: Palmer Dabbelt \u003cpalmer@rivosinc.com\u003e\n" }, { "commit": "a638b0461b58aa3205cd9d5f14d6f703d795b4af", "tree": "ce68ca8619c3314e4d30c0e2e0449cd474c2310d", "parents": [ "1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0" ], "author": { "name": "Sergey Matyukevich", "email": "sergey.matyukevich@syntacore.com", "time": "Thu May 23 11:43:23 2024 +0300" }, "committer": { "name": "Palmer Dabbelt", "email": "palmer@rivosinc.com", "time": "Thu May 30 09:42:51 2024 -0700" }, "message": "riscv: prevent pt_regs corruption for secondary idle threads\n\nTop of the kernel thread stack should be reserved for pt_regs. However\nthis is not the case for the idle threads of the secondary boot harts.\nTheir stacks overlap with their pt_regs, so both may get corrupted.\n\nSimilar issue has been fixed for the primary hart, see c7cdd96eca28\n(\"riscv: prevent stack corruption by reserving task_pt_regs(p) early\").\nHowever that fix was not propagated to the secondary harts. The problem\nhas been noticed in some CPU hotplug tests with V enabled. The function\nsmp_callin stored several registers on stack, corrupting top of pt_regs\nstructure including status field. As a result, kernel attempted to save\nor restore inexistent V context.\n\nFixes: 9a2451f18663 (\"RISC-V: Avoid using per cpu array for ordered booting\")\nFixes: 2875fe056156 (\"RISC-V: Add cpu_ops and modify default booting method\")\nSigned-off-by: Sergey Matyukevich \u003csergey.matyukevich@syntacore.com\u003e\nReviewed-by: Alexandre Ghiti \u003calexghiti@rivosinc.com\u003e\nLink: https://lore.kernel.org/r/20240523084327.2013211-1-geomatsi@gmail.com\nSigned-off-by: Palmer Dabbelt \u003cpalmer@rivosinc.com\u003e\n" }, { "commit": "47eb2d68d10208e6a9e89d10b66018e8d6ca0623", "tree": "9c05975661ffb10b2c99a60bbf353a7f9bbf4ba6", "parents": [ "41011e2de3480f9adb6420b35b67628b2d903355" ], "author": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue May 28 11:06:32 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Thu May 30 17:36:22 2024 +0100" }, "message": "KVM: arm64: nv: Expose BTI and CSV_frac to a guest hypervisor\n\nNow that we expose PAC to NV guests, we can also expose BTI (as\nthe two as joined at the hip, due to some of the PAC instructions\nbeing landing pads).\n\nWhile we\u0027re at it, also propagate CSV_frac, which requires no\nparticular emulation.\n\nFixes: f4f6a95bac49 (\"KVM: arm64: nv: Advertise support for PAuth\")\nReviewed-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nLink: https://lore.kernel.org/r/20240528100632.1831995-3-maz@kernel.org\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "41011e2de3480f9adb6420b35b67628b2d903355", "tree": "4b26fc2e9f1f5dc5673d23009dbfea7651a75ab0", "parents": [ "c92e8b9eacebb4060634ebd9395bba1b29aadc68" ], "author": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Tue May 28 11:06:31 2024 +0100" }, "committer": { "name": "Marc Zyngier", "email": "maz@kernel.org", "time": "Thu May 30 17:36:22 2024 +0100" }, "message": "KVM: arm64: nv: Fix relative priorities of exceptions generated by ERETAx\n\nERETAx can fail in multiple ways:\n\n(1) ELR_EL2 points lalaland\n(2) we get a PAC failure\n(3) SPSR_EL2 has the wrong mode\n\n(1) is easy, as we just let the CPU do its thing and deliver an\nInstruction Abort. However, (2) and (3) are interesting, because\nthe PAC failure priority is way below that of the Illegal Execution\nState exception.\n\nWhich means that if we have detected a PAC failure (and that we have\nFPACCOMBINE), we must be careful to give priority to the Illegal\nExecution State exception, should one be pending.\n\nSolving this involves hoisting the SPSR calculation earlier and\ntesting for the IL bit before injecting the FPAC exception.\n\nIn the extreme case of a ERETAx returning to an invalid mode *and*\nfailing its PAC check, we end up with an Instruction Abort (due\nto the new PC being mangled by the failed Auth) *and* PSTATE.IL\nbeing set. Which matches the requirements of the architecture.\n\nWhilst we\u0027re at it, remove a stale comment that states the obvious\nand only confuses the reader.\n\nFixes: 213b3d1ea161 (\"KVM: arm64: nv: Handle ERETA[AB] instructions\")\nReviewed-by: Joey Gouly \u003cjoey.gouly@arm.com\u003e\nReviewed-by: Oliver Upton \u003coliver.upton@linux.dev\u003e\nLink: https://lore.kernel.org/r/20240528100632.1831995-2-maz@kernel.org\nSigned-off-by: Marc Zyngier \u003cmaz@kernel.org\u003e\n" }, { "commit": "52a2c70c3ec555e670a34dd1ab958986451d2dd2", "tree": "7c2e9bd56173d19c6769c808900b1c33d4c8775d", "parents": [ "027a44fedd55fbdf1d45603894634acd960ad04b" ], "author": { "name": "Guenter Roeck", "email": "linux@roeck-us.net", "time": "Thu May 30 08:20:14 2024 -0700" }, "committer": { "name": "Guenter Roeck", "email": "linux@roeck-us.net", "time": "Thu May 30 09:05:19 2024 -0700" }, "message": "hwmon: (shtc1) Fix property misspelling\n\nThe property name is \"sensirion,low-precision\", not\n\"sensicon,low-precision\".\n\nCc: Chris Ruehl \u003cchris.ruehl@gtsys.com.hk\u003e\nFixes: be7373b60df5 (\"hwmon: shtc1: add support for device tree bindings\")\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\n" }, { "commit": "027a44fedd55fbdf1d45603894634acd960ad04b", "tree": "a632214c86c7b7b44485c4007bedce03cb16dff1", "parents": [ "a94ff8e50c20bde6d50864849a98b106e45d30c6" ], "author": { "name": "Peter Colberg", "email": "peter.colberg@intel.com", "time": "Tue May 21 14:12:46 2024 -0400" }, "committer": { "name": "Guenter Roeck", "email": "linux@roeck-us.net", "time": "Thu May 30 09:05:06 2024 -0700" }, "message": "hwmon: (intel-m10-bmc-hwmon) Fix multiplier for N6000 board power sensor\n\nThe Intel N6000 BMC outputs the board power value in milliwatt, whereas\nthe hwmon sysfs interface must provide power values in microwatt.\n\nFixes: e1983220ae14 (\"hwmon: intel-m10-bmc-hwmon: Add N6000 sensors\")\nSigned-off-by: Peter Colberg \u003cpeter.colberg@intel.com\u003e\nReviewed-by: Matthew Gerlach \u003cmatthew.gerlach@linux.intel.com\u003e\nLink: https://lore.kernel.org/r/20240521181246.683833-1-peter.colberg@intel.com\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\n" }, { "commit": "d8ec19857b095b39d114ae299713bd8ea6c1e66a", "tree": "57a75bbcf7ef6e671208c61e35ae570ba51b3359", "parents": [ "4a4be1ad3a6efea16c56615f31117590fd881358", "13c7c941e72908b8cce5a84b45a7b5e485ca12ed" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu May 30 08:33:04 2024 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu May 30 08:33:04 2024 -0700" }, "message": "Merge tag \u0027net-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net\n\nPull networking fixes from Paolo Abeni:\n \"Including fixes from bpf and netfilter.\n\n Current release - regressions:\n\n - gro: initialize network_offset in network layer\n\n - tcp: reduce accepted window in NEW_SYN_RECV state\n\n Current release - new code bugs:\n\n - eth: mlx5e: do not use ptp structure for tx ts stats when not\n initialized\n\n - eth: ice: check for unregistering correct number of devlink params\n\n Previous releases - regressions:\n\n - bpf: Allow delete from sockmap/sockhash only if update is allowed\n\n - sched: taprio: extend minimum interval restriction to entire cycle\n too\n\n - netfilter: ipset: add list flush to cancel_gc\n\n - ipv4: fix address dump when IPv4 is disabled on an interface\n\n - sock_map: avoid race between sock_map_close and sk_psock_put\n\n - eth: mlx5: use mlx5_ipsec_rx_status_destroy to correctly delete\n status rules\n\n Previous releases - always broken:\n\n - core: fix __dst_negative_advice() race\n\n - bpf:\n - fix multi-uprobe PID filtering logic\n - fix pkt_type override upon netkit pass verdict\n\n - netfilter: tproxy: bail out if IP has been disabled on the device\n\n - af_unix: annotate data-race around unix_sk(sk)-\u003eaddr\n\n - eth: mlx5e: fix UDP GSO for encapsulated packets\n\n - eth: idpf: don\u0027t enable NAPI and interrupts prior to allocating Rx\n buffers\n\n - eth: i40e: fully suspend and resume IO operations in EEH case\n\n - eth: octeontx2-pf: free send queue buffers incase of leaf to inner\n\n - eth: ipvlan: dont Use skb-\u003esk in ipvlan_process_v{4,6}_outbound\"\n\n* tag \u0027net-6.10-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (69 commits)\n netdev: add qstat for csum complete\n ipvlan: Dont Use skb-\u003esk in ipvlan_process_v{4,6}_outbound\n net: ena: Fix redundant device NUMA node override\n ice: check for unregistering correct number of devlink params\n ice: fix 200G PHY types to link speed mapping\n i40e: Fully suspend and resume IO operations in EEH case\n i40e: factoring out i40e_suspend/i40e_resume\n e1000e: move force SMBUS near the end of enable_ulp function\n net: dsa: microchip: fix RGMII error in KSZ DSA driver\n ipv4: correctly iterate over the target netns in inet_dump_ifaddr()\n net: fix __dst_negative_advice() race\n nfc/nci: Add the inconsistency check between the input data length and count\n MAINTAINERS: dwmac: starfive: update Maintainer\n net/sched: taprio: extend minimum interval restriction to entire cycle too\n net/sched: taprio: make q-\u003epicos_per_byte available to fill_sched_entry()\n netfilter: nft_fib: allow from forward/input without iif selector\n netfilter: tproxy: bail out if IP has been disabled on the device\n netfilter: nft_payload: skbuff vlan metadata mangle support\n net: ti: icssg-prueth: Fix start counter for ft1 filter\n sock_map: avoid race between sock_map_close and sk_psock_put\n ...\n" }, { "commit": "2a38e4ca302280fdcce370ba2bee79bac16c4587", "tree": "9f63322faa8d7004cb2c747bcf357cc6df4ab70a", "parents": [ "34bf6bae3286a58762711cfbce2cf74ecd42e1b5" ], "author": { "name": "Dave Hansen", "email": "dave.hansen@linux.intel.com", "time": "Fri May 17 13:05:34 2024 -0700" }, "committer": { "name": "Dave Hansen", "email": "dave.hansen@linux.intel.com", "time": "Thu May 30 08:29:45 2024 -0700" }, "message": "x86/cpu: Provide default cache line size if not enumerated\n\ntl;dr: CPUs with CPUID.80000008H but without CPUID.01H:EDX[CLFSH]\nwill end up reporting cache_line_size()\u003d\u003d0 and bad things happen.\nFill in a default on those to avoid the problem.\n\nLong Story:\n\nThe kernel dies a horrible death if c-\u003ex86_cache_alignment (aka.\ncache_line_size() is 0. Normally, this value is populated from\nc-\u003ex86_clflush_size.\n\nRight now the code is set up to get c-\u003ex86_clflush_size from two\nplaces. First, modern CPUs get it from CPUID. Old CPUs that don\u0027t\nhave leaf 0x80000008 (or CPUID at all) just get some sane defaults\nfrom the kernel in get_cpu_address_sizes().\n\nThe vast majority of CPUs that have leaf 0x80000008 also get\n-\u003ex86_clflush_size from CPUID. But there are oddballs.\n\nIntel Quark CPUs[1] and others[2] have leaf 0x80000008 but don\u0027t set\nCPUID.01H:EDX[CLFSH], so they skip over filling in -\u003ex86_clflush_size:\n\n\tcpuid(0x00000001, \u0026tfms, \u0026misc, \u0026junk, \u0026cap0);\n\tif (cap0 \u0026 (1\u003c\u003c19))\n\t\tc-\u003ex86_clflush_size \u003d ((misc \u003e\u003e 8) \u0026 0xff) * 8;\n\nSo they: land in get_cpu_address_sizes() and see that CPUID has level\n0x80000008 and jump into the side of the if() that does not fill in\nc-\u003ex86_clflush_size. That assigns a 0 to c-\u003ex86_cache_alignment, and\nhilarity ensues in code like:\n\n buffer \u003d kzalloc(ALIGN(sizeof(*buffer), cache_line_size()),\n GFP_KERNEL);\n\nTo fix this, always provide a sane value for -\u003ex86_clflush_size.\n\nBig thanks to Andy Shevchenko for finding and reporting this and also\nproviding a first pass at a fix. But his fix was only partial and only\nworked on the Quark CPUs. It would not, for instance, have worked on\nthe QEMU config.\n\n1. https://raw.githubusercontent.com/InstLatx64/InstLatx64/master/GenuineIntel/GenuineIntel0000590_Clanton_03_CPUID.txt\n2. You can also get this behavior if you use \"-cpu 486,+clzero\"\n in QEMU.\n\n[ dhansen: remove \u0027vp_bits_from_cpuid\u0027 reference in changelog\n\t because bpetkov brutally murdered it recently. ]\n\nFixes: fbf6449f84bf (\"x86/sev-es: Set x86_virt_bits to the correct value straight away, instead of a two-phase approach\")\nReported-by: Andy Shevchenko \u003candriy.shevchenko@linux.intel.com\u003e\nSigned-off-by: Dave Hansen \u003cdave.hansen@linux.intel.com\u003e\nTested-by: Andy Shevchenko \u003candriy.shevchenko@linux.intel.com\u003e\nTested-by: Jörn Heusipp \u003cosmanx@heusipp.de\u003e\nCc: stable@vger.kernel.org\nLink: https://lore.kernel.org/all/20240516173928.3960193-1-andriy.shevchenko@linux.intel.com/\nLink: https://lore.kernel.org/lkml/5e31cad3-ad4d-493e-ab07-724cfbfaba44@heusipp.de/\nLink: https://lore.kernel.org/all/20240517200534.8EC5F33E%40davehans-spike.ostc.intel.com\n" }, { "commit": "e112311615a24e1618a591c73506571dc304eb8d", "tree": "928889898fd9451362d8921d068ca85eac25a4cc", "parents": [ "06fe9b1df1086b42718d632aa57e8f7cd1a66a21" ], "author": { "name": "Breno Leitao", "email": "leitao@debian.org", "time": "Thu May 30 07:23:39 2024 -0700" }, "committer": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Thu May 30 08:33:01 2024 -0600" }, "message": "io_uring/rw: Free iovec before cleaning async data\n\nkmemleak shows that there is a memory leak in io_uring read operation,\nwhere a buffer is allocated at iovec import, but never de-allocated.\n\nThe memory is allocated at io_async_rw-\u003efree_iovec, but, then\nio_async_rw is kfreed, taking the allocated memory with it. I saw this\nhappening when the read operation fails with -11 (EAGAIN).\n\nThis is the kmemleak splat.\n\n unreferenced object 0xffff8881da591c00 (size 256):\n...\n backtrace (crc 7a15bdee):\n\t[\u003c00000000256f2de4\u003e] __kmalloc+0x2d6/0x410\n\t[\u003c000000007a9f5fc7\u003e] iovec_from_user.part.0+0xc6/0x160\n\t[\u003c00000000cecdf83a\u003e] __import_iovec+0x50/0x220\n\t[\u003c00000000d1d586a2\u003e] __io_import_iovec+0x13d/0x220\n\t[\u003c0000000054ee9bd2\u003e] io_prep_rw+0x186/0x340\n\t[\u003c00000000a9c0372d\u003e] io_prep_rwv+0x31/0x120\n\t[\u003c000000001d1170b9\u003e] io_prep_readv+0xe/0x30\n\t[\u003c0000000070b8eb67\u003e] io_submit_sqes+0x1bd/0x780\n\t[\u003c00000000812496d4\u003e] __do_sys_io_uring_enter+0x3ed/0x5b0\n\t[\u003c0000000081499602\u003e] do_syscall_64+0x5d/0x170\n\t[\u003c00000000de1c5a4d\u003e] entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThis occurs because the async data cleanup functions are not set for\nread/write operations. As a result, the potentially allocated iovec in\nthe rw async data is not freed before the async data is released,\nleading to a memory leak.\n\nWith this following patch, kmemleak does not show the leaked memory\nanymore, and all liburing tests pass.\n\nFixes: a9165b83c193 (\"io_uring/rw: always setup io_async_rw for read/write requests\")\nSigned-off-by: Breno Leitao \u003cleitao@debian.org\u003e\nLink: https://lore.kernel.org/r/20240530142340.1248216-1-leitao@debian.org\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "34bf6bae3286a58762711cfbce2cf74ecd42e1b5", "tree": "6b4140c145f436968fe8fdc84609024aceebd16a", "parents": [ "1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Tue May 28 22:21:31 2024 +0200" }, "committer": { "name": "Borislav Petkov (AMD)", "email": "bp@alien8.de", "time": "Thu May 30 15:58:55 2024 +0200" }, "message": "x86/topology/amd: Evaluate SMT in CPUID leaf 0x8000001e only on family 0x17 and greater\n\nThe new AMD/HYGON topology parser evaluates the SMT information in CPUID leaf\n0x8000001e unconditionally while the original code restricted it to CPUs with\nfamily 0x17 and greater.\n\nThis breaks family 0x15 CPUs which advertise that leaf and have a non-zero\nvalue in the SMT section. The machine boots, but the scheduler complains loudly\nabout the mismatch of the core IDs:\n\n WARNING: CPU: 1 PID: 0 at kernel/sched/core.c:6482 sched_cpu_starting+0x183/0x250\n WARNING: CPU: 0 PID: 1 at kernel/sched/topology.c:2408 build_sched_domains+0x76b/0x12b0\n\nAdd the condition back to cure it.\n\n [ bp: Make it actually build because grandpa is not concerned with\n trivial stuff. :-P ]\n\nFixes: f7fb3b2dd92c (\"x86/cpu: Provide an AMD/HYGON specific topology parser\")\nCloses: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/56\nReported-by: Tim Teichmann \u003cteichmanntim@outlook.de\u003e\nReported-by: Christian Heusel \u003cchristian@heusel.eu\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Borislav Petkov (AMD) \u003cbp@alien8.de\u003e\nTested-by: Tim Teichmann \u003cteichmanntim@outlook.de\u003e\nCc: stable@vger.kernel.org\nLink: https://lore.kernel.org/r/7skhx6mwe4hxiul64v6azhlxnokheorksqsdbp7qw6g2jduf6c@7b5pvomauugk\n" }, { "commit": "c85578e730135d47271ca874e4436dd87e87f252", "tree": "d1bc087d28dd3bc624f9556721a85df1e6073e7c", "parents": [ "ba2e8323d7b71781c7da02e83d813af9ab7fe1f9", "b65456b7b379e20ab225a4e906dc4a0c98fddd7a" ], "author": { "name": "Mark Brown", "email": "broonie@kernel.org", "time": "Thu May 30 14:33:14 2024 +0100" }, "committer": { "name": "Mark Brown", "email": "broonie@kernel.org", "time": "Thu May 30 14:33:14 2024 +0100" }, "message": "ASoC: SOF: ipc4-topology: Fix nhlt configuration blob\n\nMerge series from Peter Ujfalusi \u003cpeter.ujfalusi@linux.intel.com\u003e:\n\nThe existing logic to pick a DMIC blob is based on several historical\nassumptions that the NHLT in BIOS always contains 32-bits per sample\ntype (first patch, [1]).\n\nThe other issue with the existing logic is that it was designed to care only\nabout the bit depth of the format and fails to find the existing and correct\nblob when rate/channels are different on the FE side compared to what we should\nbe using on the DAI side (we have components in path which can change\nrate/channel count).\n\nThese issues have not been observed in past but with new MTL based (Windows)\nlaptops and new topologies to enhance the audio quality, we started to see weird\nissues around how our assumptions of vendors failed.\n\nSince some NHLT blob handling cleanup has been done for 6.10, this series will\ncomplete that work to cover even cases that we don\u0027t anticipate to see.\n\n[1] https://github.com/thesofproject/linux/issues/4973\n" }, { "commit": "b62c150c3bae72ac1910dcc588f360159eb0744a", "tree": "bb4f6e4cd7010a465d5e85cd4ff75e24bd55c1f2", "parents": [ "2ba50582634d0bfe3a333ab7575a7f0122a7cde8" ], "author": { "name": "Gerald Loacker", "email": "gerald.loacker@wolfvision.net", "time": "Wed May 29 16:42:47 2024 +0200" }, "committer": { "name": "Neil Armstrong", "email": "neil.armstrong@linaro.org", "time": "Thu May 30 14:57:33 2024 +0200" }, "message": "drm/panel: sitronix-st7789v: fix display size for jt240mhqs_hwt_ek_e3 panel\n\nThis is a portrait mode display. Change the dimensions accordingly.\n\nFixes: 0fbbe96bfa08 (\"drm/panel: sitronix-st7789v: add jasonic jt240mhqs-hwt-ek-e3 support\")\nSigned-off-by: Gerald Loacker \u003cgerald.loacker@wolfvision.net\u003e\nAcked-by: Jessica Zhang \u003cquic_jesszhan@quicinc.com\u003e\nLink: https://lore.kernel.org/r/20240409-bugfix-jt240mhqs_hwt_ek_e3-timing-v2-3-e4821802443d@wolfvision.net\nSigned-off-by: Neil Armstrong \u003cneil.armstrong@linaro.org\u003e\nLink: https://patchwork.freedesktop.org/patch/msgid/20240409-bugfix-jt240mhqs_hwt_ek_e3-timing-v2-3-e4821802443d@wolfvision.net\n" } ], "next": "2ba50582634d0bfe3a333ab7575a7f0122a7cde8" }