1. 22 Jun, 2024 9 commits
    • Linus Torvalds's avatar
      Merge tag 'xfs-6.10-fixes-4' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux · 563a5067
      Linus Torvalds authored
      Pull xfs fix from Chandan Babu:
      
       - Fix assertion failure due to a race between unlink and cluster buffer
         instantiation.
      
      * tag 'xfs-6.10-fixes-4' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
        xfs: fix unlink vs cluster buffer instantiation race
      563a5067
    • Linus Torvalds's avatar
      Merge tag 'bcachefs-2024-06-22' of https://evilpiepirate.org/git/bcachefs · c3de9b57
      Linus Torvalds authored
      Pull bcachefs fixes from Kent Overstreet:
       "Lots of (mostly boring) fixes for syzbot bugs and rare(r) CI bugs.
      
        The LRU_TIME_BITS fix was slightly more involved; we only have 48 bits
        for the LRU position (we would prefer 64), so wraparound is possible
        for the cached data LRUs on a filesystem that has done sufficient
        (petabytes) reads; this is now handled.
      
        One notable user reported bugfix, where we were forgetting to
        correctly set the bucket data type, which should have been
        BCH_DATA_need_gc_gens instead of BCH_DATA_free; this was causing us to
        go emergency read-only on a filesystem that had seen heavy enough use
        to see bucket gen wraparoud.
      
        We're now starting to fix simple (safe) errors without requiring user
        intervention - i.e. a small incremental step towards full self
        healing.
      
        This is currently limited to just certain allocation information
        counters, and the error is still logged in the superblock; see that
        patch for more information. ("bcachefs: Fix safe errors by default")"
      
      * tag 'bcachefs-2024-06-22' of https://evilpiepirate.org/git/bcachefs: (22 commits)
        bcachefs: Move the ei_flags setting to after initialization
        bcachefs: Fix a UAF after write_super()
        bcachefs: Use bch2_print_string_as_lines for long err
        bcachefs: Fix I_NEW warning in race path in bch2_inode_insert()
        bcachefs: Replace bare EEXIST with private error codes
        bcachefs: Fix missing alloc_data_type_set()
        closures: Change BUG_ON() to WARN_ON()
        bcachefs: fix alignment of VMA for memory mapped files on THP
        bcachefs: Fix safe errors by default
        bcachefs: Fix bch2_trans_put()
        bcachefs: set_worker_desc() for delete_dead_snapshots
        bcachefs: Fix bch2_sb_downgrade_update()
        bcachefs: Handle cached data LRU wraparound
        bcachefs: Guard against overflowing LRU_TIME_BITS
        bcachefs: delete_dead_snapshots() doesn't need to go RW
        bcachefs: Fix early init error path in journal code
        bcachefs: Check for invalid btree IDs
        bcachefs: Fix btree ID bitmasks
        bcachefs: Fix shift overflow in read_one_super()
        bcachefs: Fix a locking bug in the do_discard_fast() path
        ...
      c3de9b57
    • Linus Torvalds's avatar
      Merge tag 'ata-6.10-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux · da3b6ef1
      Linus Torvalds authored
      Pull ata fix from Niklas Cassel:
      
       - We currently enable DIPM (device initiated power management) in the
         device (using a SET FEATURES call to the device), regardless if the
         HBA supports any LPM states or not. It seems counter intuitive, and
         potentially dangerous to enable a device side feature, when the HBA
         does not have the corresponding support. Thus, make sure that we do
         not enable DIPM if the HBA does not support any LPM states.
      
      * tag 'ata-6.10-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux:
        ata: ahci: Do not enable LPM if no LPM states are supported by the HBA
      da3b6ef1
    • Linus Torvalds's avatar
      Merge tag 'pwm/for-6.10-rc5-fixes-take2' of... · 1f5c5371
      Linus Torvalds authored
      Merge tag 'pwm/for-6.10-rc5-fixes-take2' of git://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux
      
      Pull pwm fixes from Uwe Kleine-König:
       "Three fixes for the pwm-stm32 driver.
      
        The first patch prevents an integer wrap-around for small periods. In
        the second patch the calculation of the prescaler is fixed which
        resulted in values for the ARR register that don't fit into the
        corresponding register bit field. The last commit improves an error
        message that was wrongly copied from another error path"
      
      * tag 'pwm/for-6.10-rc5-fixes-take2' of git://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux:
        pwm: stm32: Fix error message to not describe the previous error path
        pwm: stm32: Fix calculation of prescaler
        pwm: stm32: Refuse too small period requests
      1f5c5371
    • Linus Torvalds's avatar
      Merge tag 'arm-fixes-6.10' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc · 56bf7334
      Linus Torvalds authored
      Pull SoC fixes from Arnd Bergmann:
       "There are seven oneline patches that each address a distinct problem
        on the NXP i.MX platform, mostly the popular i.MX8M variant.
      
        The only other two fixes are for error handling on the psci firmware
        driver and SD card support on the milkv duo riscv board"
      
      * tag 'arm-fixes-6.10' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc:
        firmware: psci: Fix return value from psci_system_suspend()
        riscv: dts: sophgo: disable write-protection for milkv duo
        arm64: dts: imx8qm-mek: fix gpio number for reg_usdhc2_vmmc
        arm64: dts: freescale: imx8mm-verdin: enable hysteresis on slow input pin
        arm64: dts: imx93-11x11-evk: Remove the 'no-sdio' property
        arm64: dts: freescale: imx8mp-venice-gw73xx-2x: fix BT shutdown GPIO
        arm: dts: imx53-qsb-hdmi: Disable panel instead of deleting node
        arm64: dts: imx8mp: Fix TC9595 input clock on DH i.MX8M Plus DHCOM SoM
        arm64: dts: freescale: imx8mm-verdin: Fix GPU speed
      56bf7334
    • Linus Torvalds's avatar
      Merge tag 'loongarch-fixes-6.10-2' of... · d4ba3313
      Linus Torvalds authored
      Merge tag 'loongarch-fixes-6.10-2' of git://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson
      
      Pull LoongArch fixes from Huacai Chen:
       "Some hw breakpoint fixes, an objtool build warnging fix, and a trivial
        cleanup"
      
      * tag 'loongarch-fixes-6.10-2' of git://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson:
        LoongArch: KVM: Remove an unneeded semicolon
        LoongArch: Fix multiple hardware watchpoint issues
        LoongArch: Trigger user-space watchpoints correctly
        LoongArch: Fix watchpoint setting error
        LoongArch: Only allow OBJTOOL & ORC unwinder if toolchain supports -mthin-add-sub
      d4ba3313
    • Linus Torvalds's avatar
      Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm · fe37fe2a
      Linus Torvalds authored
      Pull kvm fixes from Paolo Bonzini:
       "ARM:
      
         - Fix dangling references to a redistributor region if the vgic was
           prematurely destroyed.
      
         - Properly mark FFA buffers as released, ensuring that both parties
           can make forward progress.
      
        x86:
      
         - Allow getting/setting MSRs for SEV-ES guests, if they're using the
           pre-6.9 KVM_SEV_ES_INIT API.
      
         - Always sync pending posted interrupts to the IRR prior to IOAPIC
           route updates, so that EOIs are intercepted properly if the old
           routing table requested that.
      
        Generic:
      
         - Avoid __fls(0)
      
         - Fix reference leak on hwpoisoned page
      
         - Fix a race in kvm_vcpu_on_spin() by ensuring loads and stores are
           atomic.
      
         - Fix bug in __kvm_handle_hva_range() where KVM calls a function
           pointer that was intended to be a marker only (nothing bad happens
           but kind of a mine and also technically undefined behavior)
      
         - Do not bother accounting allocations that are small and freed
           before getting back to userspace.
      
        Selftests:
      
         - Fix compilation for RISC-V.
      
         - Fix a "shift too big" goof in the KVM_SEV_INIT2 selftest.
      
         - Compute the max mappable gfn for KVM selftests on x86 using
           GuestMaxPhyAddr from KVM's supported CPUID (if it's available)"
      
      * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm:
        KVM: SEV-ES: Fix svm_get_msr()/svm_set_msr() for KVM_SEV_ES_INIT guests
        KVM: Discard zero mask with function kvm_dirty_ring_reset
        virt: guest_memfd: fix reference leak on hwpoisoned page
        kvm: do not account temporary allocations to kmem
        MAINTAINERS: Drop Wanpeng Li as a Reviewer for KVM Paravirt support
        KVM: x86: Always sync PIR to IRR prior to scanning I/O APIC routes
        KVM: Stop processing *all* memslots when "null" mmu_notifier handler is found
        KVM: arm64: FFA: Release hyp rx buffer
        KVM: selftests: Fix RISC-V compilation
        KVM: arm64: Disassociate vcpus from redistributor region on teardown
        KVM: Fix a data race on last_boosted_vcpu in kvm_vcpu_on_spin()
        KVM: selftests: x86: Prioritize getting max_gfn from GuestPhysBits
        KVM: selftests: Fix shift of 32 bit unsigned int more than 32 bits
      fe37fe2a
    • Uwe Kleine-König's avatar
      pwm: stm32: Fix error message to not describe the previous error path · f01af302
      Uwe Kleine-König authored
      "Failed to lock the clock" is an appropriate error message for
      clk_rate_exclusive_get() failing, but not for the clock running too
      fast for the driver's calculations.
      
      Adapt the error message accordingly.
      
      Fixes: d44d6356 ("pwm: stm32: Fix for settings using period > UINT32_MAX")
      Signed-off-by: default avatarUwe Kleine-König <u.kleine-koenig@baylibre.com>
      Link: https://lore.kernel.org/r/285182163211203fc823a65b180761f46e828dcb.1718979150.git.u.kleine-koenig@baylibre.comSigned-off-by: default avatarUwe Kleine-König <ukleinek@kernel.org>
      f01af302
    • Uwe Kleine-König's avatar
      pwm: stm32: Fix calculation of prescaler · dab8f9f0
      Uwe Kleine-König authored
      A small prescaler is beneficial, as this improves the resolution of the
      duty_cycle configuration. However if the prescaler is too small, the
      maximal possible period becomes considerably smaller than the requested
      value.
      
      One situation where this goes wrong is the following: With a parent
      clock rate of 208877930 Hz and max_arr = 0xffff = 65535, a request for
      period = 941243 ns currently results in PSC = 1. The value for ARR is
      then calculated to
      
      	ARR = 941243 * 208877930 / (1000000000 * 2) - 1 = 98301
      
      This value is bigger than 65535 however and so doesn't fit into the
      respective register field. In this particular case the PWM was
      configured for a period of 313733.4806027616 ns (with ARR = 98301 &
      0xffff). Even if ARR was configured to its maximal value, only period =
      627495.6861167669 ns would be achievable.
      
      Fix the calculation accordingly and adapt the comment to match the new
      algorithm.
      
      With the calculation fixed the above case results in PSC = 2 and so an
      actual period of 941229.1667195285 ns.
      
      Fixes: 8002fbee ("pwm: stm32: Calculate prescaler with a division instead of a loop")
      Signed-off-by: default avatarUwe Kleine-König <u.kleine-koenig@baylibre.com>
      Link: https://lore.kernel.org/r/b4d96b79917617434a540df45f20cb5de4142f88.1718979150.git.u.kleine-koenig@baylibre.comSigned-off-by: default avatarUwe Kleine-König <ukleinek@kernel.org>
      dab8f9f0
  2. 21 Jun, 2024 31 commits