Tags

5.4.241-254

5.4.241-417

x86_misc_for_v6.4_rc1

- Add a x86 hw vulnerabilities section to MAINTAINERS so that the folks
  involved in it can get CCed on patches

- Add some more CPUID leafs to the kcpuid tool and extend its
  functionality to be more useful when grepping for CPUID bits

x86_cpu_for_v6.4_rc1

- Add Emerald Rapids to the list of Intel models supporting PPIN

- Finally use a CPUID bit for split lock detection instead of
  enumerating every model

- Make sure automatic IBRS is set on AMD, even though the AP bringup
  code does that now by replicating the MSR which contains the switch

x86_acpi_for_v6.4_rc1

- Improve code generation in ACPI's global lock's acquisition function

ras_core_for_v6.4_rc1

 - Just cleanups and fixes this time around: make threshold_ktype const,
   an objtool fix and use proper size for a bitmap

rocm-5.5.0

ROCm release v5.5.0

core-entry-2023-04-24

Update for entry and ptrace:

  Provide a ptrace set/get interface for syscall user dispatch. The main
  purpose is to enable checkpoint/restore (CRIU) to handle processes which
  utilize syscall user dispatch correctly.

core-debugobjects-2023-04-24

A single update to debugobjects:

  Prevent a race vs. statically initialized objects. Such objects are
  usually not initialized via an init() function. They are special cased
  and detected on first use under the assumption that they are already
  correctly initialized via the static initializer.

  This works correctly unless there are two concurrent debug object
  operations on such an object.

  The first one detects that the object is not yet tracked and tries to
  establish a tracking object after dropping the debug objects hash bucket
  lock. The concurrent operation does the same. The one which wins the
  race ends up modifying the state of the object which makes the other one
  fail resulting in a bogus debug objects warning.

  Prevent this by making the detection of a static object and the
  allocation of a tracking object atomic under the hash bucket lock. So the
  first one to acquire the hash bucket lock will succeed and the second one
  will observe the correct tracking state.

  This race existed forever but was only exposed when the timer wheel code
  added a debug_object_assert_init() call outside of the timer base locked
  region. This replaced the previous warning about timer::function being
  NULL which had to be removed when the timer_shutdown() mechanics were
  added.

pull-lock_rename_child

lock_rename_child() (for ksmbd folks)

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

pull-old-dio

legacy direct-io cleanup

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

pull-nios2

nios2 minor cleanup

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

pull-misc

misc pile

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

pull-write-one-page

write_one_page series

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

pull-fd

fget() to fdget() conversions

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

v6.3

Linux 6.3

irq_urgent_for_v6.3

- Remove an over-zealous sanity check of the array of MSI-X vectors to
  be allocated for a device

x86_urgent_for_v6.3

- Fix for older binutils which do not support C-syntax constant suffixes

iomap-6.4-merge-1

New code for 6.4:

 * Remove an unused symbol.
 * Add tracepoints for the directio code.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>

v6.2.12

This is the 6.2.12 stable release