Tags

Tags give the ability to mark specific points in history as being important
  • v6.5.3

    238589d0 · Linux 6.5.3 ·
    This is the 6.5.3 stable release
    
  • v6.4.16

    ae4e4fc3 · Linux 6.4.16 ·
    This is the 6.4.16 stable release
    
  • v6.1.53

    09045dae · Linux 6.1.53 ·
    This is the 6.1.53 stable release
    
  • fix-scrub-6.6_2023-09-12

    xfs: fix out of bounds memory access in scrub
    This is a quick fix for a few internal syzbot reports concerning an
    invalid memory access in the scrub code.
    
    This has been lightly tested with fstests.  Enjoy!
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    
  • fix-efi-recovery-6.6_2023-09-12

    xfs: fix EFI recovery livelocks
    This series fixes a customer-reported transaction reservation bug
    introduced ten years ago that could result in livelocks during log
    recovery.  Log intent item recovery single-steps each step of a deferred
    op chain, which means that each step only needs to allocate one
    transaction's worth of space in the log, not an entire chain all at
    once.  This single-stepping is critical to unpinning the log tail since
    there's nobody else to do it for us.
    
    This has been lightly tested with fstests.  Enjoy!
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    
  • fix-iunlink-6.6_2023-09-12

    xfs: reload the last iunlink item
    It turns out that there are some serious bugs in how xfs handles the
    unlinked inode lists.  Way back before 4.14, there was a bug where a ro
    mount of a dirty filesystem would recover the log bug neglect to purge
    the unlinked list.  This leads to clean unmounted filesystems with
    unlinked inodes.  Starting around 5.15, we also converted the codebase
    to maintain a doubly-linked incore unlinked list.  However, we never
    provided the ability to load the incore list from disk.  If someone
    tries to allocate an O_TMPFILE file on a clean fs with a pre-existing
    unlinked list or even deletes a file, the code will fail and the fs
    shuts down.
    
    This first part of the correction effort adds the ability to load the
    first inode in the bucket when unlinking a file; and to load the next
    inode in the list when inactivating (freeing) an inode.
    
    This has been lightly tested with fstests.  Enjoy!
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    
  • fix-iunlink-list-6.6_2023-09-12

    xfs: reload entire iunlink lists
    This is the second part of correcting XFS to reload the incore unlinked
    inode list from the ondisk contents.  Whereas part one tackled failures
    from regular filesystem calls, this part takes on the problem of needing
    to reload the entire incore unlinked inode list on account of somebody
    loading an inode that's in the /middle/ of an unlinked list.  This
    happens during quotacheck, bulkstat, or even opening a file by handle.
    
    In this case we don't know the length of the list that we're reloading,
    so we don't want to create a new unbounded memory load while holding
    resources locked.  Instead, we'll target UNTRUSTED iget calls to reload
    the entire bucket.
    
    Note that this changes the definition of the incore unlinked inode list
    slightly -- i_prev_unlinked == 0 now means "not on the incore list".
    
    This has been lightly tested with fstests.  Enjoy!
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    
  • fix-larp-requirements-6.6_2023-09-12

    xfs: disallow LARP on old fses
    Before enabling logged xattrs, make sure the filesystem is new enough
    that it actually supports log incompat features.
    
    This has been lightly tested with fstests.  Enjoy!
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    
  • fix-percpu-lists-6.6_2023-09-12

    xfs: fix cpu hotplug mess [v2]
    
    Ritesh and Eric separately reported crashes in XFS's hook function for
    CPU hot remove if the remove event races with a filesystem being
    mounted.  I also noticed via generic/650 that once in a while the log
    will shut down over an apparent overrun of a transaction reservation;
    this turned out to be due to CIL percpu list aggregation failing to pick
    up the percpu list items from a dying CPU.
    
    Either way, the solution here is to eliminate the need for a CPU dying
    hook by using a private cpumask to track which CPUs have added to their
    percpu lists directly, and iterating with that mask.  This fixes the log
    problems and (I think) solves a theoretical UAF bug in the inodegc code
    too.
    
    v2: fix a few put_cpu uses, add necessary memory barriers, and use
        atomic cpumask operations
    
    This has been lightly tested with fstests.  Enjoy!
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    
  • fix-ro-mounts-6.6_2023-09-12

    xfs: fix ro mounting with unknown rocompat features [v2]
    
    Dave pointed out some failures in xfs/270 when he upgraded Debian
    unstable and util-linux started using the new mount apis.  Upon further
    inquiry I noticed that XFS is quite a hot mess when it encounters a
    filesystem with unrecognized rocompat bits set in the superblock.
    
    Whereas we used to allow readonly mounts under these conditions, a
    change to the sb write verifier several years ago resulted in the
    filesystem going down immediately because the post-mount log cleaning
    writes the superblock, which trips the sb write verifier on the
    unrecognized rocompat bit.  I made the observation that the ROCOMPAT
    features RMAPBT and REFLINK both protect new log intent item types,
    which means that we actually cannot support recovering the log if we
    don't recognize all the rocompat bits.
    
    Therefore -- fix inode inactivation to work when we're recovering the
    log, disallow recovery when there's unrecognized rocompat bits, and
    don't clean the log if doing so would trip the rocompat checks.
    
    v2: change direction of series to allow log recovery on ro mounts
    
    This has been lightly tested with fstests.  Enjoy!
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    
  • fix-fsmap-6.6_2023-09-12

    xfs: fix fsmap cursor handling [v2]
    
    This patchset addresses an integer overflow bug that Dave Chinner found
    in how fsmap handles figuring out where in the record set we left off
    when userspace calls back after the first call filled up all the
    designated record space.
    
    v2: add RVB tags
    
    This has been lightly tested with fstests.  Enjoy!
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    
  • Ubuntu-lowlatency-5.15.0-85.94

    Ubuntu-lowlatency-5.15.0-85.94
    
  • Ubuntu-hwe-5.15-5.15.0-85.95_20.04.2

    Ubuntu-hwe-5.15-5.15.0-85.95~20.04.2
    
  • v6.6-rc1

    0bb80ecc · Linux 6.6-rc1 ·
    Linux 6.6-rc1
    
  • x86-urgent-2023-09-10

    Fix preemption delays in the SGX code, remove unnecessarily UAPI-exported code,
    fix a ld.lld linker (in)compatibility quirk and make the x86 SMP init code a bit
    more conservative to fix kexec() lockups.
    
    Signed-off-by: Ingo Molnar <mingo@kernel.org>
    
  • perf-urgent-2023-09-10

    Work around a firmware bug in the uncore PMU driver,
    affecting certain Intel systems.
    
    Signed-off-by: Ingo Molnar <mingo@kernel.org>