| Age | Commit message (Collapse) | Author |
|
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext
Pull sched_ext fixes from Tejun Heo:
- With proxy execution or core scheduling, a CPU could run a task that
had been requeued on another CPU while dispatch had the rq lock
dropped.
- Unregistering a scheduler could return while its teardown was still
running, letting the teardown call into BPF code that was already
freed.
- A CPU coming online could call into the BPF scheduler before the
scheduler was told that the CPU is online.
- A parent scheduler could be asked to attach a sub-scheduler to a
cgroup that was already removed.
- Hardening: more kfuncs that take a queue lock are rejected in tracing
programs, where they could deadlock the CPU, and a queue iterator no
longer restarts after reaching the end, which the BPF verifier
assumes can't happen.
- Smaller fixes: tasks needlessly sent back to the BPF scheduler on
idle CPUs, stale scheduling state carried into a task's next
scheduler, and uneven CPU shards with partially populated SMT cores.
* tag 'sched_ext-for-7.4-rc2-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext:
sched_ext: Reject DSQ iterator kfuncs in tracing programs
sched_ext: make DSQ iterator stay drained after NULL
sched_ext: Fix partial-SMT core counting in calc_shard_layout()
sched_ext: Reset task fields on exit of an SCX_TASK_READY task
sched_ext: Read exit_kind before flushing in scx_flush_disable_work()
sched_ext: Reject scx_bpf_destroy_dsq() in tracing programs
sched_ext: Fix ops.enqueue/dispatch() calls before ops.cpu_online()
sched_ext: Factor out drain_offline_rq()
sched_ext: Fix stale pick when the donor changes during dispatch
sched_ext: Call ops.sub_attach() only while the cgroup is online
sched_ext: Fix scx_bpf_dsq_reenq() kerneldoc claiming NMI calls are allowed
sched_ext: Avoid unnecessary IMMED reenqueues on idle CPUs
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup
Pull cgroup fixes from Tejun Heo:
- A file notification racing the file's removal could re-arm the
notification timer after it was shut down, corrupting the timer wheel
or firing on freed memory.
- The v1 freezer could leave an exiting task frozen forever after its
cgroup was thawed or removed.
- With memcg built without the block cgroup controller, memcg reclaim
waited on writeback and could deadlock against a filesystem freeze.
memcg now selects the controller.
- cpuset partition state could go wrong when CPUs move between nested
partitions or go offline: isolated CPUs leaked or went missing,
invalid partitions kept exclusive CPUs or came back with no usable
CPU, and expanding a remote partition could fail. Separately, a
forked child could inherit a corrupted memory node mask.
* tag 'cgroup-for-7.4-rc2-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup:
cgroup/cpuset: Don't revive invalid partition without active CPU on hotplug
cgroup/cpuset: Remove redundant WARN_ON_ONCE() in remote_cpus_update()
memcg: make MEMCG select BLK_CGROUP
cpuset: generalize the validate_partition() interface
cpuset: settle isolation state when CPUs are given back to parent
cgroup/cpuset: Correctly set isolated_cpus when switching partition state
cgroup/cpuset: Protect current->mems_allowed read in cpuset_fork()
selftests/cgroup: Fix "test_cpuset_prs.sh -v" failures
cpuset: add early empty cpumask check in partition_xcpus_add/del
cgroup/cpuset: Reset partition data when an invalid partition stays invalid
cgroup/freezer: Fix exiting tasks left frozen forever after rmdir
cgroup/freezer: walk exiting tasks in the v1 freezer
cgroup: arm the notify timer only while the file exists
cgroup/cpuset: Do housekeeping check when isolated child with root parent may get more xcpus
cgroup/cpuset: Recompute effective cpumask in update_cpumasks_hier() after calling update_parent_effective_cpumask()
cgroup/cpuset: Fix incorrect CPU accounting with parent's effective_xcpus expansion
|
|
Pull NFS client fixes from Anna Schumaker:
- Various NFS and SunRPC fixes from Avi Weiss
- Various localio fixes from Mike Snitzer
- Delegated timestamp fixes from Jeff Layton
- CB_NOTIFY_LOCK fixes from Olga Kornievskaia
- Various sunrpc, flexfiles, and xprtrdma fixes from Tim Menninger
* tag 'nfs-for-7.4-2' of git://git.linux-nfs.org/projects/anna/linux-nfs: (26 commits)
NFSv4: Prevent indefinite waits for out-of-order OPEN stateids
NFSv4/flexfiles: limit transport disconnects when cancelling I/O
SUNRPC: add request-scoped disconnects when cancelling tasks
pNFS: avoid repeatedly cancelling I/O for the same lseg
xprtrdma: serialize unmap_sync with xprt_disconnect
NFSv4: remember that the server may send CB_NOTIFY_LOCK
NFSv4: wake blocking lock waiters when a delegated lock is released
NFS: stamp after the server's ctime following a CLONE
NFS: stamp after the server's ctime when truncating under delegated times
NFS: don't let delegated c/mtime stamps go backward
NFS/localio: give the LOCALIO probe a short timeout of its own
NFS/localio: probe again for LOCALIO when localio_enabled is set to Y
NFS/localio: hold the client across an asynchronous LOCALIO probe
SUNRPC: Balance queue accounting when relocating a task
SUNRPC: Balance switch queue length on transport removal
SUNRPC: Fix TCP-with-TLS transport class identification
SUNRPC: preserve transport security policy when cloning clients
SUNRPC: preserve timeout policy when cloning clients
SUNRPC: preserve fatal network errors during RPC binding
sunrpc: instantiate rpc_pipefs dentry before publishing it
...
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
Pull device mapper fixes from Mikulas Patocka:
"dm:
- fix infinite loop when removing a zoned device
- fix misbehavior if kobject_init_and_add fails
- fix refcount underflow if zone reset failed
- fix misbehavior if we attempt to load a table after previous table
load failed
- fix use-after-free if we open a device read-only and then re-open
it read-write
- fix error being ignored if flush failed
dm-pcache:
- fix misbehavior on flush failure
dm-raid:
- validate array_position after it is read from the superblock
dm-cache:
- fix a crash if dm_kcopyd_client_create fails
- fix divide by zero on extremely large device
- fix NULL pointer dereference on open failure
- fix misbehavior if dm_bitset_cursor_begin fails
dm-snapshot:
- properly advertise discard_granularity in the queue limits
- fix data corruption on unaligned discards
dm-crypt:
- fix a crash on invalid table line
- fix scheduling in atomic context when using no_write_workqueue and
asynchronous completion cipher
- fix misbehavior if percpu_counter_init fails
dm-thin:
- fix integer overflow if no_space_timeout is too high
- fix data corruption if discard races with regular I/O
- fix leak if __set_snapshot_details fails
- fix parsing of feature arguments
dm-mpath:
- fix buffer overflow when parsing the table string
- fix integer overflow in queue_if_no_path_timeout_secs
dm-log-userspace:
- fix open device leak on initialization error
dm-zoned:
- back off when reclaim cannot make progress
- do not reclaim a random zone into another random zone
dm-integrity:
- don't recalculate with HMAC because of a dirty bitmap
- don't attempt to commit journal on disabled device
dm-persistent-data:
- don't ignore the return value of node_copy
- fix buffer leak if find_leaf fails
dm-verity:
- don't restart or panic on errors during system shutdown
dm-raid:
- flush a work item in raid_dtr, fix use-after-free"
* tag 'for-7.4/dm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm: (34 commits)
dm: fail a REQ_PREFLUSH bio with data when its preflush fails
dm-raid: fix use-after-free in raid_dtr()
dm-integrity: don't attempt to commit journal on disabled device
dm-verity: don't restart or panic on errors during system shutdown
dm crypt: fix use of uninitialized percpu_counter in ctr error path
dm: fix use-after-free when dm_get_device() widens the open mode
dm persistent data: don't leak bufio buffer if find_leaf fails
dm persistent data: don't ignore writeback errors
dm persistent data: test return value of node_copy
dm-thin: fix parsing of feature arguments
dm-thin: fix leak if __set_snapshot_details fails
dm-thin: fix data corruption if discard races with regular I/O
dm-cache: fix ending a cursor that never began
dm-cache: fix NULL pointer dereference on open failure
dm-crypt: defer async write submission to write thread
dm mpath: cap queue_if_no_path_timeout_secs
dm cache: validate the discard block size before narrowing
dm: Reject table setup after queue or disk teardown
dm: avoid double-dropping the zone reset submission reference
dm-sysfs: fix misbehavior if kobject_init_and_add fails
...
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi
Pull spi fixes from Mark Brown:
"There's a few small collection of driver fixes here, the usual story
where none of them are super remarkable if you don't have the have the
hardware. The largest batch is the Tegra fixes which are mainly around
error handling"
* tag 'spi-fix-v7.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi:
spi: axi-spi-engine: Start the program length at zero
spi: virtio: move teardown to .remove()
spi: dt-bindings: pl022: Allow a power domain
spi: tegra210-quad: Unmap DMA buffers on transfer timeout
spi: tegra210-quad: Track DMA mapping state
spi: tegra210-quad: don't overwrite refreshed status with lost-IRQ snapshot
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator
Pull regulator fixes from Mark Brown:
"A small change adding support for the Silergy SYM827 which is a
variation on the FAN53555 so needs some quirk data and a new DT
compatible"
* tag 'regulator-fix-v7.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator:
regulator: fan53555: Add support for Silergy SYM827
regulator: dt-bindings: fan53555: Add Silergy SYM827
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core
Pull driver core fix from Danilo Krummrich:
- Fix a use-after-free during device removal when a child device reuses
its parent's managed software node (affecting Xe)
* tag 'driver-core-7.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core:
software node: only let the owner release a managed node
|
|
When a CPU hotplug leaves no CPU outside of the partitions for the top
cpuset, cpuset_handle_hotplug() clears subpartitions_cpus and gives all
the active CPUs back to the top cpuset. cpuset_hotplug_update_tasks()
then walks the hierarchy and invalidates the partitions, as
subpartitions_cpus is empty.
However, an invalid partition visited in the same walk may be revived
if its effective_xcpus is not empty. tasks_nocpu_error() doesn't catch
it when its CPUs are all offline but it has no task. Its CPUs are put
back into subpartitions_cpus, and the valid partitions visited after it
are no longer invalidated, as subpartitions_cpus is not empty any more.
The top cpuset is left with CPUs overlapping with these partitions.
It can be reproduced on a system with 8 CPUs:
# cd /sys/fs/cgroup
# echo +cpuset > cgroup.subtree_control
# mkdir A1 B1
# echo 1 > A1/cpuset.cpus
# echo 1 > A1/cpuset.cpus.exclusive
# echo 0,2-7 > B1/cpuset.cpus
# echo root > B1/cpuset.cpus.partition
# echo root > A1/cpuset.cpus.partition
# cat A1/cpuset.cpus.partition
root invalid (Parent unable to distribute cpu downstream)
# echo 0 > /sys/devices/system/cpu/cpu1/online
# cat A1/cpuset.cpus.partition B1/cpuset.cpus.partition
root
root
# cat cpuset.cpus.effective
0,2-7
A1 can't take CPU 1, the last CPU of the root cgroup which has tasks.
When CPU 1 is offlined, A1 is revived without any active CPU, and B1
stays valid while its CPUs are also in the effective CPUs of the root
cgroup, which triggers
WARNING: kernel/cgroup/cpuset.c:919 at rebuild_sched_domains_locked
Only revive an invalid partition in hotplug if its effective_xcpus has
an active CPU, the same as what is required to create a partition with
tasks. With that, A1 and B1 are both invalidated in the above case.
Fixes: 0c7f293efc87 ("cgroup/cpuset: Add cpuset.cpus.exclusive.effective for v2")
Cc: stable@vger.kernel.org # v6.7+
Reported-by: Sashiko <sashiko-bot@kernel.org>
Link: https://sashiko.dev/#/patchset/20261114083124.1340140-1-ridong.chen%40linux.dev?part=11
Signed-off-by: Ridong Chen <chenridong@xiaomi.com>
Reviewed-by: Waiman Long <longman@redhat.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
|
|
remote_cpus_update() warns if the CPUs to be added to a remote partition
intersect subpartitions_cpus, and then checks the very same condition
right below to set PERR_NOCPUS and invalidate the partition:
WARN_ON_ONCE(cpumask_intersects(tmp->addmask, subpartitions_cpus));
if (!capable(CAP_SYS_ADMIN))
WRITE_ONCE(cs->prs_err, PERR_ACCESS);
else if (cpumask_intersects(tmp->addmask, subpartitions_cpus) ||
cpumask_subset(top_cpuset.effective_cpus, tmp->addmask))
WRITE_ONCE(cs->prs_err, PERR_NOCPUS);
Sashiko reported that the warning could be triggered by a write to a
cpuset control file, before the CAP_SYS_ADMIN check, which would panic a
system with panic_on_warn set.
The warning was added by commit 86888c7bd117 ("cgroup/cpuset: Add
warnings to catch inconsistency in exclusive CPUs") as an assertion that
such CPUs have been filtered out before. No way to trigger it with the
current interfaces has been found, as these CPUs are rejected when
cpuset.cpus.exclusive is written. But the warning is redundant, as the
conflict is handled right below anyway.
Remove the warning and rely on the PERR_NOCPUS check, the same as
remote_partition_enable() already does for this conflict.
Reported-by: Sashiko <sashiko-bot@kernel.org>
Link: https://sashiko.dev/#/patchset/20261114083124.1340140-1-ridong.chen%40linux.dev?part=6
Signed-off-by: Ridong Chen <chenridong@xiaomi.com>
Reviewed-by: Waiman Long <longman@redhat.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull x86 fixes from Ingo Molnar:
- Don't print reset reason in VMs, to fix Xen PV domU boot
regression on AMD Zen CPUs (Jason Andryuk)
- Preserve the default VGA fallback for legacy modes, to fix
regression where a SeaBIOS QEMU guest with bochs and VKMS
the boot VGA (bochs) loses its DRM boot_display attribute
(Hengyu Liang)
- Ensure write visibility during LDT installation (Dave Hansen)
* tag 'x86-urgent-2026-11-15' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
x86/mm: Ensure write visibility during LDT installation
x86/video: Preserve the default VGA fallback for legacy modes
x86/CPU/AMD: Don't print reset reason in VMs
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull timer fixes from Ingo Molnar::
- Add VDSO_UNALIGNED_PACKED config option for targets without efficient
unaligned memory accesses (such as ARMv5), and turn it on for
!CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS platforms.
Propagate these changes into tooling headers as well (Ian Rogers)
- Read getboottime64() offsets under the tk_core.seq sequence counter
(Hungyu Lin)
- Keep tsacct task begin times stable across suspend (Hungyu Lin)
- Reject cross timestamps for invalid AUX clocks (Avi Weiss)
- Refresh auxiliary timekeeper base before offset validation (Avi
Weiss)
* tag 'timers-urgent-2026-11-15' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
timekeeping: Refresh auxiliary base before offset validation
timekeeping: Reject cross timestamps for invalid AUX clocks
tsacct: Keep task begin times stable across suspend
timekeeping: Read getboottime64() offsets under the sequence counter
tools headers: Update the vdso/unaligned.h copy with the kernel sources
vdso: Add VDSO_UNALIGNED_PACKED config option
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull scheduler fixes from Ingo Molnar:
- Fix spurious SYS_sched_setattr() -EPERM for migration-disabled
tasks (Andrea Parri)
- Reject clamp values above SCHED_CAPACITY_SCALE (Andrea Parri)
- Fix cpuset_mutex double unlock in __sched_setscheduler()
(Andrea Parri)
- Don't use fits_capacity() to compare thread and CPU counts in
in invalid_llc_nr() (Zhan Xusheng)
- Do not touch SMT siblings that have not joined the core yet
during CPU onlining (Seiji Nishikawa)
* tag 'sched-urgent-2026-11-15' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
sched/core: Do not touch SMT siblings that have not joined the core yet
sched/cache: Don't use fits_capacity() to compare thread and CPU counts
sched/core: Fix cpuset_mutex double unlock in __sched_setscheduler()
sched/uclamp: Reject clamp values above SCHED_CAPACITY_SCALE
sched/deadline: Fix spurious -EPERM for migration-disabled tasks
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull perf events fixes from Ingo Molnar:
- Avoid AMD uncore context migration from non-owners (Sandipan Das)
- Clear stop state in perf_trace_add(), to fix self-profilers such as
async-profiler. Also fix a similar bug in hw_breakpoint_add() (Paolo
Bertinetti)
- Fix racy update of cpc->hrtimer_interval (Benjamin Segall)
- Do not resurrect cpuctx->cgrp after last cgroup event exit, to fix
UAF bug (Phat Dinh)
* tag 'perf-urgent-2026-11-15' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
perf/core: Do not resurrect cpuctx->cgrp after last cgroup event exit
perf: Fix racy update of cpc->hrtimer_interval
perf/hw_breakpoint: Clear stop state in hw_breakpoint_add()
tracing/perf: Clear stop state in perf_trace_add()
perf/x86/amd/uncore: Avoid context migration from non-owners
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull core syscall fixes from Ingo Molnar:
- Two generic syscall entry code fixes for return code
data type definitions (Florian Bezdeka)
* tag 'core-urgent-2026-11-15' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
entry: Complete syscall_enter_from_user_mode_work() to bool migration
entry: Fix return type of syscall_trace_enter()
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux
Pull liveupdate fixes from Mike Rapoport:
- avoid address translation in is_kho_boot() before the linear map is
initialized, fixing early boot BUG_ONs on arm64
- check for duplicate session names before growing the sessions
preservations block set to avoid preserving an empty block that
causes restoration to panic()
* tag 'fixes-2026-11-15' of git://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux:
kho: check fdt_phys in is_kho_boot()
liveupdate: check for duplicate session before growing block set
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux
Pull kexec MAINTAINERS update from Mike Rapoport:
"Remove Dave Young as kdump reviewer"
* tag 'kexec-fixes-2026-11-15' of git://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux:
Remove myself as a kdump reviewer
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
Pull probe fixes from Masami Hiramatsu:
"Fix ftrace ops switching and optprobe state transitions:
- Switch an armed ftrace-based kprobe from kprobe_ftrace_ops to
kprobe_ipmodify_ops in register_aggr_kprobe() when adding a probe
with a post_handler, so later disarming does not fail with -ENOENT
and leave the probe armed
- Queue forcibly unoptimized probes onto the generation's
cooling_list in force_unoptimize_kprobe() so unregister_kprobes()
waits for Tasks RCU before freeing the optinsn slot, preventing a
use-after-free
- Skip arch_arm_kprobe() in __arm_kprobe() when a probe is queued for
unoptimization so the active relative jump instruction is not
partially overwritten with a breakpoint before the optimizer runs
- Re-queue any jump-optimized sibling probe covering a disabled
probe's address when that probe finishes cooling in
optprobe_finalize_generation(), matching the freeing_list path
Fix multiprobe lifecycle and boot kprobe setup
- Return early in setup_boot_kprobe_events() when the kprobe_event=
boot buffer is empty to avoid contending on event_mutex with
asynchronous eval-map work during normal boot
- Verify that a multiprobe event is neither enabled nor busy before
unlinking any sibling kprobe, fprobe, uprobe, or eprobe so active
probes cannot be unlinked and freed via dynamic_events
- Register and enable a newly appended fprobe or uprobe immediately
when the target multiprobe event is already enabled so the probe
fires and disable or perf cleanup does not act on an unregistered
probe
- Free the temporary event name string with __free(kfree) in
__trace_uprobe_create() to prevent a memory leak if a subsequent
allocation fails
Fix BTF parsing and string array fetch handling:
- Compute BTF bitfield byte and bit offsets consistently, select the
smallest unsigned fetch type covering the bitfield, and size
FETCH_OP_MOD_BF from that type to prevent an 8-byte out-of-bounds
write on smaller ring buffer slots
- Validate BTF_KIND_PTR and non-NULL BTF_KIND_INT types in
btf_type_is_char_ptr() and btf_type_is_char_array() before reading
inner type metadata to avoid misinterpreting byte sizes as type IDs
or reading out of bounds
- Check for FETCH_OP_UDEREF before advancing the fetch instruction
slot in finalize_fetch_insn() so user-space dereference string
arrays emit FETCH_OP_ST_USTRING instead of reading kernel memory
- Reject string array counts when the preceding fetch operation is
not a memory dereference so non-dereference string sources ($comm,
immediate strings, eprobe fields) do not emit invalid
FETCH_OP_LP_ARRAY loops
Fix signed 1-byte field fetch and fprobe target check:
- Use explicit fixed-width integer types (s8/u8, s16/u16, s32/u32) in
get_event_field() so 1-byte signed event fields are sign-extended
instead of zero-extended under -funsigned-char
- Exclude TRACE_EVENT_FL_FPROBE events in find_and_get_event() so
eprobes cannot attach to fprobe or tprobe events
Fix typo in kprobes documentation:
- Remove a stray closing parenthesis in Documentation/trace/kprobes.rst"
* tag 'probes-fixes-v7.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace:
tracing/uprobes: Fix memory leak of tail in __trace_uprobe_create()
tracing/probes: Reject array count on non-dereference string sources
tracing/probes: Fix user-space dereference string array store type
tracing/eprobe: Disallow attaching eprobes to fprobe events
tracing/eprobe: Fix 1-byte signed field fetch in get_event_field()
tracing/probes: Fix missing BTF kind checks in char pointer/array helpers
tracing/probes: Fix BTF bitfield parsing and out-of-bounds buffer write
tracing/probes: Enable newly appended probe when target event is enabled
tracing/probes: Check enabled and busy state before unlinking sibling probes
kprobes: Re-optimize blocked sibling probe when cooling finishes
kprobes: Do not overwrite jump instruction when re-arming unoptimizing probe
kprobes: Fix UAF and queue cooling probes on forced unoptimization
kprobes: Switch ftrace ops when adding probe with post_handler
docs, kprobes: Fix bracket
tracing: skip boot kprobe setup when no events were requested
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
Pull bootconfig fixes from Masami Hiramatsu:
- bootconfig: Allow keys with the maximum supported depth
Check the array capacity before storing the next key component in
xbc_node_compose_key_after() so keys at XBC_DEPTH_MAX (16) are
composed instead of failing with -ERANGE when listing keys or
creating /proc/bootconfig.
- bootconfig: Trim unquoted values at end of file
Trim trailing whitespace from unquoted values in __xbc_parse_value()
after scanning finishes so values at end of input without a trailing
newline do not retain extra whitespace.
- tools/bootconfig: Close only opened braces in compact output
Check key children while skipping value nodes when backtracking in
xbc_show_compact_tree() so a brace is not closed when a single subkey
under a valued key was printed in dotted notation.
- tools/bootconfig: Test listing keys at the maximum depth
Add regression tests verifying that a 16-component key can be
attached and listed in full while a 17-component key is rejected.
* tag 'bootconfig-fixes-v7.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace:
bootconfig: Trim unquoted values at end of file
tools/bootconfig: Close only opened braces in compact output
tools/bootconfig: Test listing keys at the maximum depth
bootconfig: Allow keys with the maximum supported depth
|
|
Memcg reclaim only relies on writeback throttling if
writeback_throttling_sane() does. Since commit 97c9341f7271 ("mm:
vmscan: disable memcg direct reclaim stalling if cgroup writeback
support is in use") that's the case if the memory controller is on the
default hierarchy and CONFIG_CGROUP_WRITEBACK is set. Otherwise
shrink_folio_list() sleeps in folio_wait_writeback() for a folio that
is under writeback and already marked for reclaim if the allocation may
enter the filesystem.
CONFIG_CGROUP_WRITEBACK is enabled whenever CONFIG_MEMCG and
CONFIG_BLK_CGROUP are. So with CONFIG_MEMCG=y and CONFIG_BLK_CGROUP=n
memcg reclaim on cgroup v2 waits for writeback just like it does on
cgroup v1.
That wait can deadlock against freezing a filesystem. Loop takes freeze
protection on the backing filesystem for its writes. A task in the
middle of a write() to the backing filesystem holds freeze protection
as well.
If that task enters memcg reclaim it can end up waiting for writeback of
a folio that belongs to a filesystem on the loop device. If a freeze of
the backing filesystem is pending the loop worker blocks when it tries
to write that folio out. And the freeze waits for the task in reclaim to
drop its freeze protection. The same applies to other drivers that serve
block I/O by writing to a file on a local filesystem and take freeze
protection for it, e.g., the scsi target's fileio backend.
Make CONFIG_MEMCG select CONFIG_BLK_CGROUP if CONFIG_BLOCK is set. Then
CONFIG_CGROUP_WRITEBACK is always enabled together with memcg and memcg
reclaim on cgroup v2 doesn't sleep in folio_wait_writeback() anymore.
a
Without CONFIG_BLOCK there are no block devices that could deadlock
like this.
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
Signed-off-by: Tejun Heo <tj@kernel.org>
|
|
During LDT installation, the intent is to overwrite the old per-mm
LDT value, then send an IPI to the mm user CPUs to have each load
the new value.
But there is an ordering problem: a new mm user CPU sets itself in
mm_cpumask() and then reads mm->context.ldt. The LDT-installing CPU
writes mm->context.ldt and then reads mm_cpumask(). But, there is
nothing which orders the LDT installation side actions. The CPU
can read mm_cpumask() before its write becomes visible.
Ensure that new mm user CPUs see the new mm->context.ldt. Make
mm->context.ldt visible before reading mm_cpumask().
Also convert the smp_store_release() over to a WRITE_ONCE().
smp_store_release() has an internal barrier which is weaker than
the new smp_mb(). Avoid an extra barrier by converting it to
WRITE_ONCE().
Also refresh/correct misleading comments. READ/WRITE_ONCE() do not
"synchronize" anything themselves.
Reported-by: Jaeyoung Chung <jjy600901@snu.ac.kr>
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Tested-by: Jaeyoung Chung <jjy600901@snu.ac.kr>
Acked-by: Linus Torvalds <torvalds@linuxfoundation.org>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: <stable@vger.kernel.org>
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip
Pull xen fixes from Juergen Gross:
"A bunch of isolated fixes of Xen related drivers"
* tag 'for-linus-7.4a-rc3-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip:
Xen/gnttab: improve error handling in gnttab_dma_{alloc,free}_pages()
xen: don't allow gnttab_dma_[alloc|free]_pages() in PV guest
xen/pvcalls: destroy the per-socket workqueue on release
xen/pvcalls: unwind pvcalls_new_active_socket() step by step
xen/privcmd: fix double free when an irqfd is shut down twice
xen/gntdev: fix deadlock between map ioctl and mmap
xen/platform-pci: Disable device before releasing PCI regions
xen/grant-table: annotate on-stack work in gnttab_unmap_refs_sync()
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging
Pull hwmon fixes from Guenter Roeck:
- Read tracking-mode voltage fault limits dynamically in the mp2975
PMBus driver instead of caching probe-time snapshots, avoiding false
over-voltage alarms when CPU voltage changes at runtime.
- Fix SCMI sensor probe by enabling supported sensors via firmware IDs
before exposing channels and checking channel config allocations.
- Fix runtime PM enable and reference count imbalances during probe and
teardown in the gpio-fan driver.
- Fix max31760 fan controller initialization and reporting, including
leaving standby at probe, initial 0 RPM reporting, and swapped
temperature limit registers.
- Assorted minor sensor reading, interval clamping, and register
handling fixes in other drivers.
* tag 'hwmon-for-v7.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging:
hwmon: (aht10) Fix update_interval overflow on 64-bit
hwmon: (scmi) Configure sensors before exposing channels
hwmon: (scmi) Check channel config allocation
hwmon: (nct6775) Handle dual use registers
hwmon: (scmi) Enable temperature sensors using their sensor IDs
hwmon: (pmbus/mp2975) Get vout fault limits dynamically
hwmon: (sy7636a) fix negative temperatures
hwmon: (max31760) Report 0 RPM before the first fan speed measurement
hwmon: (max31760) Leave standby mode at probe
hwmon: (max31760) Fix the local temperature limit registers
hwmon: (gpio-fan) Fix runtime PM imbalance in probe and teardown
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs
Pull overlayfs fixes from Amir Goldstein:
- Fixes for data-only layers (composefs), some for regressions from
v6.16, which relaxed the requirements for redirects to data-only
layers
- Fix a use-after-free in lookup of a hardlink with a FUSE upper,
reported by Sashiko
- Fix a mount failure right after unmount of an overlay with the same
upperdir
- Reject lower layers on the same fs with different idmaps, which could
decode file handles through the wrong layer
- Minor fixes for a memory leak, an error message and readdir d_ino
* tag 'ovl-fixes-7.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs:
selftests: overlayfs: reject different lower idmaps on same fs
ovl: reject different lower idmaps on the same fs
ovl: bump the impure dir version when linking a file with origin
ovl: return EIO if the lowerdata is missing
ovl: follow lower to lowerdata redirects from any lower layer
ovl: report the requested redirect_dir mode in conflicting options
ovl: do not allow nfs_export with data-only layers
ovl: do not check the deferred lowerdata redirect on index lookup
ovl: fix leak of lowerdata redirect on ovl_get_inode() failure
ovl: do not always clear absolute_redirect
ovl: release the upperdir/workdir in-use locks before the umount sync
ovl: do not read the flags of a put upper dentry in lookup
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/ntfs
Pull ntfs fixes from Namjae Jeon:
- Validate that $INDEX_ALLOCATION is open and non-resident before
reading or writing index blocks, preventing NULL pointer dereferences
when an earlier index operation has not opened it
- Check that index allocation inodes are non-resident and child VCNs
are non-negative and within bounds before directory lookup reads,
preventing a deadlock when $INDEX_ALLOCATION is missing or damaged
- Validate file names against the index entry's key length, preventing
out-of-bounds reads when directory enumeration resumes using a copied
key
- Return -ENOENT for NTFS_IOC_LIST_STREAMS on deleted base files and
fix unsigned underflow in its buffer bounds check, preventing
out-of-bounds writes when the sizing and filling passes disagree
- Use kfree() for the temporary runlist allocated with kmalloc() on
merge failure, resolving the Coccinelle allocation/free mismatch
warning
* tag 'ntfs-for-7.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/ntfs:
ntfs: open the index allocation before reading or writing an index block
ntfs: do not read an index block outside $INDEX_ALLOCATION
ntfs: silence kmalloc/kvfree mismatch warning
ntfs: check the file name against the key length of an index entry
ntfs: fix out-of-bounds write race in NTFS_IOC_LIST_STREAMS
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/smb
Pull smb server fixes from Namjae Jeon:
- Evaluate explicit-access requests in DACL order with exact SID
matching, and prevent guest and anonymous sessions from matching
Authenticated Users
- Apply Unix group and OWNER RIGHTS ACEs, and keep their denials when
POSIX ACL fallback determines access
- Allow the parent directory’s DACL to grant explicitly requested
DELETE and FILE_READ_ATTRIBUTES through FILE_DELETE_CHILD and
FILE_LIST_DIRECTORY
- Exclude metadata-only file and stream opens from sharing conflicts
and stream delete-sharing checks, while accounting for writes implied
by overwrites and named-stream creation
- Return STATUS_ACCESS_DENIED for reads on files lacking FMODE_READ,
preventing warnings in __kernel_read() and potential panics
- Pin parent dentries during SMB2 CREATE permission, status, and ACL
inheritance operations to prevent use-after-free races with
concurrent rename and removal
- Keep expired sessions bound to their original user during NTLM
reauthentication, preventing identity changes and a user-object leak
* tag 'ksmbd-for-7.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/smb:
ksmbd: keep group denials when a POSIX ACL entry decides access
ksmbd: refuse reauthentication of an expired session as another user
ksmbd: pin parent dentries in SMB2 CREATE ACL path
ksmbd: let the parent's DACL grant DELETE and FILE_READ_ATTRIBUTES
ksmbd: evaluate the DACL in order for explicit access requests
ksmbd: skip metadata-only stream opens in the delete check
ksmbd: skip metadata-only opens in sharing checks
ksmbd: refuse to read a handle that is not open for reading
ksmbd: grant a caller what its groups and OWNER RIGHTS ACEs allow
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd
Pull key fixes from Jarkko Sakkinen:
- Invoke the match callback before the state checks in
keyring_search_iterator(), so that a non-matching revoked,
expired or invalidated key cannot decide the search result
- Take key->sem for reading around the ->asym_*() method calls
in the keyctl pkey operations, as a key reference does not
pin the module providing the key type
* tag 'keys-v7.4-rc3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd:
KEYS: Protect pkey method checks against type removal
KEYS: do not let an unmatched key decide the search result
|
|
Pull drm fixes from Dave Airlie:
"Weekly drm fixes, this is a bit bigger as we missed xe last week due
to a tree screw up, so it's mostly xe and amdgpu, then the usual
scattering of fixes across drivers.
sched:
- Ensure stopped entity cannot be re-added to the run-queue
bridge:
- ssd2825: Fix panel enable sequence
- sii902x: validate I2S data lane values
display:
- hdmi: Fixes to SCDC
i915:
- Fix for PTL GitLab #9196: eDP-2 on DDI B ends up in a state where
any enable fails
- PSR fixes
amdgpu:
- DCN 6 DML2 fix
- VCE fixes
- GC 11.0.2 fix
- SMU 15 fix
- Error handling fixes
- Partition fix
- IMU firmware clean up fix
- TLB fence handling fix
amdkfd:
- SVM fixes
- CRIU fixes
xe:
- select configfs
- Sync Wa_16023105232 in xe_was to match OOB rule
- Program LMTT directory pointer from each GT init path
- Demote uncorrectable local error log on CRI
- Apply tile workarounds after PCODE init
- VRAM offlining fixes
- ras: Fix sysctrl and drm-ras discrepancy
- pat: Return error from xe_pat_init_early() on unknown
- Prevent VF memory IRQ from accessing a torn-down engine
- guc: Protect timeout handling from device unplug
- gt: Disable GT reset worker before engine teardown
- Various hwmon fixes
- tuning: Restrict Anyhit NULL-query tuning to render engines
- gsc: Fix NVL-S GSC compatibility number
- Don't abort the shrinker walk on -EBUSY
- Mark xe_vma_ops_alloc() noinline for error injection
- lrc: Restore CTX_CS_INDIRECT_CTX_OFFSET programming for pre-Xe2
- Fix build with DRM_XE=y and CONFIGFS_FS=m
- madvise: use already clamped pat_index
- Various wedging fixes
- Rebind BOs evicted before the first LR queue
- Toggle the D3Cold enable flag at runtime resume
- Access GT MMIO after pcode init
- xe_late_bind_fw: Fix firmware leak on missing manifest entry
- svm: Preserve default PAT index when resetting VMA attributes
- Unwrap sync fences before adding them as job dependencies
- Schedule disable G2H fixes
gud:
- Avoid divide error in gud_stats_debugfs
meson:
- load ENCL gamma table while ENCL is disabled
nouveau:
- disp: Set atomic functions in struct drm_mode_config_funcs
- gsp: Handle only IRQs routed to host
panfrost:
- Fixes to perfcnt
vc4:
- Fix firmware reference leak
- Hold runtime PM reference while allocating the binner BO
- Rebuild V3D interrupt mask on every power transition
- Re-enable the V3D interrupt after a GPU reset"
* tag 'drm-fixes-2026-11-14' of https://gitlab.freedesktop.org/drm/kernel: (81 commits)
drm/vc4: Re-enable the V3D interrupt after a GPU reset
drm/vc4: Rebuild the V3D interrupt mask on every power transition
drm/vc4: Hold a runtime PM reference while allocating the binner BO
drm: xe: select configfs
drm/xe: Sync Wa_16023105232 in xe_was to match OOB rule
drm/xe/pf: Program LMTT directory pointer from each GT's init path
drm/xe/guc: Demote uncorrectable local error log on CRI
drm/xe/pm: Apply tile workarounds after PCODE initialization
drm/gud: avoid divide error in gud_stats_debugfs
drm/nouveau/disp: Set drm_mode_config_funcs.atomic_(check|commit) (attempt 2)
drm/amdgpu: fix TLB invalidation fence handling v4
drm/amdkfd: check CRIU SVM priv data bounds before allocating
drm/amdgpu: release the IMU firmware with the other GFX microcode
drm/amdgpu: Allow cancelling a requested NPS mode
drm/amdgpu: fix the error handling of amdgpu_vm_init_entities()
drm/amdgpu: use supported SMU clock messages on SMU 15.0.0
drm/amdkfd: skip GPUs without a VM when checkpointing the BO mappings
drm/amdkfd: Acquire cwsr buffer during CRIU resume
drm/amdkfd: Acquire buffers in CRIU queue restore (again)
drm/amdgpu: Fix VCE buffer size check for DPB and input surface
...
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging
Pull watchdog fixes from Guenter Roeck:
- gunyah_wdt: Re-enable the watchdog on resume
- mediatek: Register reset controller before watchdog device
- meson_gxbb_wdt: fix suspend/resume handling of HW_RUNNING watchdog
- mtk_wdt: Stop a running watchdog over system sleep even if not opened
- npcm: fix clock prepare leak when setting timeout on a running
watchdog
- omap: Fix early_enable handling in omap_wdt_probe()
- orion_wdt: load the pretimeout counter on Armada 370/XP start
- rzv2h: Drop runtime PM handling from WDTDCR init, and use
pm_runtime_put_sync()
- sbsa_gwdt: Limit the MediaTek WS0 race workaround to revision 0
- sc1200wdt: add missing MODULE_DEVICE_TABLE()
- sp5100_tco: Use release_mem_region() for EFCH MMIO resource
* tag 'watchdog-fixes-for-v7.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging:
watchdog: rzv2h: Drop runtime PM handling from WDTDCR init
watchdog: rzv2h: Use pm_runtime_put_sync()
watchdog: omap: Fix early_enable handling in omap_wdt_probe()
watchdog: npcm: fix clock prepare leak when setting timeout on a running watchdog
watchdog: gunyah_wdt: Re-enable the watchdog on resume
watchdog: mediatek: Register reset controller before watchdog device
watchdog: sp5100_tco: Use release_mem_region() for EFCH MMIO resource
watchdog: sbsa_gwdt: Limit the MediaTek WS0 race workaround to revision 0
watchdog: meson_gxbb_wdt: fix suspend/resume handling of HW_RUNNING watchdog
watchdog: mtk_wdt: Stop a running watchdog over system sleep even if not opened
watchdog: orion_wdt: load the pretimeout counter on Armada 370/XP start
watchdog: sc1200wdt: add missing MODULE_DEVICE_TABLE()
|
|
https://gitlab.freedesktop.org/drm/misc/kernel into drm-fixes
Short summary of fixes pull:
bridge:
- ssd2825: Fix panel enable sequence
- sii902x: validate I2S data lane values
display:
- hdmi: Fixes to SCDC
gud:
- Avoid divide error in gud_stats_debugfs
meson:
- load ENCL gamma table while ENCL is disabled
nouveau:
- disp: Set atomic functions in struct drm_mode_config_funcs
- gsp: Handle only IRQs routed to host
panfrost:
- Fixes to perfcnt
sched:
- Ensure stopped entity cannot be re-added to the run-queue
vc4:
- Fix firmware reference leak
- Hold runtime PM reference while allocating the binner BO
- Rebuild V3D interrupt mask on every power transition
- Re-enable the V3D interrupt after a GPU reset
Signed-off-by: Dave Airlie <airlied@redhat.com>
From: Thomas Zimmermann <tzimmermann@suse.de>
Link: https://patch.msgid.link/20261113074438.GA14592@linux.fritz.box
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Pull arm64 fixes from Catalin Marinas:
"Fix hugetlb write fault livelock, permission overlay and GCS state
preservation across CPU suspend, cpuidle context tracking during
system suspend, GCS mode handling on signal return, AMU counter errata
workarounds, kexec loading of images with a non-zero text_offset and a
spurious ptrace warning:
- Fix hugetlb write fault livelocks caused by stale read-only TLB
entries after another CPU makes the page writable and only performs
a local invalidate. Unlike the generic fault path, hugetlb has no
fix_spurious_fault() fallback
- Save and restore POR_EL0, GCSPR_EL0 and GCSCRE0_EL1 across CPU
suspend
- Restrict cpuidle context tracking in cpu_suspend() to idle tasks,
avoiding context tracking warnings during system suspend
- Ignore attempts to change GCS mode through signal return, which
updated the software state without updating the hardware. Changes
made through prctl() in the signal handler are preserved. This
changes the documented ABI but no known userspace relies on it.
Allowing mode changes through both prctl() and signal return also
creates confusing interactions, with signal return potentially
undoing changes deliberately made by the handler
- Extend the AMU constant counter workaround to additional CPUs and
add a core cycle counter workaround for Cortex-A715/A720, treating
the affected counters as unavailable
- Avoid CMA allocations when loading a kexec Image with a non-zero
text_offset, fixing an incorrect entry point and a memory leak when
freeing the image
- Remove a spurious ptrace warning when setting the syscall number of
a task in a non-seized group-stop without siginfo"
* tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
arm64: suspend: Only track cpuidle context for idle tasks
arm64: ptrace: don't warn on missing siginfo in a group-stop
arm64: kexec_file: Do not use CMA for images with a non-zero text_offset
arm64: errata: Add Cortex-A715/A720 AMU core counter workaround
arm64: errata: Extend the workaround for broken AMEVCNTR01 counter
arm64/gcs: Ignore attempts to change GCS mode during signal return
arm64: hugetlb: Prevent write fault livelocks on stale TLB entries
arm64: suspend: Save GCS state over suspend
arm64: suspend: Save POR_EL0 over suspend
|
|
For a bio with REQ_PREFLUSH and data, dm core may send an empty flush
first. If the flush fails, __dm_io_complete() still reissues the bio
without REQ_PREFLUSH and drops the error. When that write succeeds,
the XFS log keeps running and fsync() can return 0.
End the bio with the flush error instead of writing the data, as
blk-mq does.
Fixes: 6a8736d10cb4 ("dm: relax ordering of bio-based flush implementation")
Cc: stable@vger.kernel.org
Signed-off-by: Daejun Park <daejun7.park@samsung.com>
Acked-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
|
|
On 64-bit, update_interval writes are clamped to LONG_MAX ms, but
ms_to_ktime() overflows above 9223372036854 ms and the interval wraps.
LONG_MAX becomes -1 ms, so every read starts a new measurement and
update_interval reads back -1.
Clamp to INT_MAX like sht4x, so the limit is the same on all platforms.
Fixes: 8c78f0dee437 ("hwmon: Add AHT10 Temperature and Humidity Sensor Driver")
Cc: stable@vger.kernel.org
Signed-off-by: Rupesh Majhi <zoone.rupert@gmail.com>
Link: https://patch.msgid.link/20261108172651.220121-1-zoone.rupert@gmail.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
|
|
SCMI hwmon enables sensors with SENSOR_CONFIG_SET, but only after
registering the hwmon device and only for temperature sensors. This
leaves other sensor classes disabled on firmware that defaults sensors
to off, and exposes temperature channels before they are ready.
Configure each supported sensor while building the channel list, before
registering the hwmon device. Leave failed sensors out of the list so
their channels remain hidden, while continuing with other sensors.
Cc: Marek Vasut <marek.vasut@mailbox.org>
Reported-by: Sashiko <sashiko-bot@kernel.org>
Closes: https://sashiko.dev/#/bug/linux-4bdf9a68-22d5-4305-b684-f11fe6d1dbcc
Fixes: 72804d1631b3 ("hwmon: (scmi) Enable sensors to assure they can be read")
Cc: stable@vger.kernel.org
Signed-off-by: Sudeep Holla <sudeep.holla@kernel.org>
Link: https://patch.msgid.link/20261109151927.1672956-2-sudeep.holla@kernel.org
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
|
|
scmi_hwmon_add_chan_info() can fail to allocate a channel's config
array. Ignoring that error leaves a channel with a NULL config pointer
in the hwmon chip info, which hwmon dereferences while registering the
device.
Check the helper's return value and abort probe on failure.
Reported-by: Sashiko <sashiko-bot@kernel.org>
Closes: https://sashiko.dev/#/bug/linux-d10ced6b-a6f0-403b-9619-f5a6573f9e7f
Fixes: b23688aefb8b ("hwmon: add support for sensors exported via ARM SCMI")
Cc: stable@vger.kernel.org
Signed-off-by: Sudeep Holla <sudeep.holla@kernel.org>
Link: https://patch.msgid.link/20261109151927.1672956-1-sudeep.holla@kernel.org
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
|
|
The REG_TARGET register has different meaning, depending on if pwm is in
thermal_cruise or speed_cruise.
This means we can't assume it's always word sized, so we need to handle
it differently depending on which mode we're in.
The code already does this, but the register was configured as word
sized for the speed_cruise mode, which would do the wrong thing in
thermal_cruise mode.
Fixes: 6c009501ff20 ("hwmon: (nct6775) Add support for NCT6102D/6106D")
Fixes: 29c7cb485b32 ("hwmon: (nct6775) Integrate new model nct6116")
Fixes: 437b3c2a4bdc ("hwmon: (nct6775) Add support for NCT6126D")
Cc: stable@vger.kernel.org
Signed-off-by: Anton Lundin <glance@ac2.se>
Link: https://patch.msgid.link/20261109082511.851377-2-glance@ac2.se
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
|
|
scmi_hwmon_probe() groups sensors by hwmon type, so the index in
scmi_sensors->info[hwmon_temp] is not necessarily the SCMI sensor ID.
Passing that index to config_set() targets a different sensor if the
platform exposes non-temperature sensors ahead of temperature sensors.
The intended temperature sensor can remain disabled, causing subsequent
readings to fail. If configuring the wrong sensor fails, thermal
registration of the intended sensor is also skipped.
Use the firmware sensor ID, as the read and thermal registration paths
already do, so temperature sensors are enabled correctly.
The patch was reviewed and the commit message expanded with OpenCode
AI assistance.
Fixes: 72804d1631b3 ("hwmon: (scmi) Enable sensors to assure they can be read")
Cc: stable@vger.kernel.org
Signed-off-by: Xu Rao <raoxu@uniontech.com>
Reviewed-by: Sudeep Holla <sudeep.holla@kernel.org>
Link: https://patch.msgid.link/AED18609B941BCFD+20261109082854.3739085-1-raoxu@uniontech.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
|
|
The over- and under-voltage fault limits of the tracking mode are
relative to the voltage reference, which follows the VID/AVS requests
issued to the device and therefore changes at runtime.
The driver reads the voltage reference once during probe and derives the
limits from that snapshot, which the PMBus core caches in addition. As a
result in2_crit and in2_lcrit reflect the operating point at probe, rather
than the thresholds the device enforces. On systems where the device
supplies the CPU core voltage, in2_crit was reported anywhere between
1.15V and 1.70V across identical systems, causing false over-voltage
reports once the CPU voltage exceeded the value latched at probe.
Read the voltage reference and the over-voltage offset selector whenever
a limit is requested, and mark both limits with pmbus_set_update(), so
that the core does not cache them. The voltage reference is available on
page 3 only. Let the core change the page, so that the page it caches
matches the device, except for a single rail configuration, for which the
core does not issue PAGE commands, and the page is changed directly.
With the selector read at runtime, a device configured with an
unsupported selector no longer fails to probe. The OVP1 threshold, which
does not depend on the selector, is reported for it instead, with a
warning.
Clamp the under-voltage limit to zero, since the offset can exceed a low
voltage reference, while a negative value would be reported as a read
error.
Fixes: 2c6fcbb21149 ("hwmon: (pmbus) Add support for MPS Multi-phase mp2975 controller")
Cc: stable@vger.kernel.org
Signed-off-by: Felix Radensky <fradensky@nvidia.com>
Reviewed-by: Vadim Pasternak <vadimp@nvidia.com>
Link: https://patch.msgid.link/20261105193200.1570996-1-fradensky@nvidia.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
|
|
The thermistor readout is a signed 8-bit value in degrees Celsius.
Fixes: de34a4053250 ("hwmon: sy7636a: Add temperature driver for sy7636a")
Cc: stable@vger.kernel.org
Signed-off-by: Pablo Mazzini <pmazzini@gmail.com>
Link: https://patch.msgid.link/20261108093602.329554-3-pmazzini@gmail.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
|
|
Refactor validate_partition() to take the parent partition, the new
partition root state, the new effective exclusive CPUs and the CPUs to
be deleted, instead of a trial cpuset. A NULL parent stands for a
remote partition, whose CPUs come from top_cpuset. This makes the
interface flexible enough to handle both local and remote partition
validation.
This also fixes a false PERR_NOCPUS error when expanding a remote
partition. The no CPU left for tasks check in partition_cpus_change()
is done against the cgroup parent, but the CPUs of a remote partition
come from top_cpuset, not from its parent. For example, on a 4-CPU
system:
echo 2-3 > P/cpuset.cpus
echo 2-3 > P/cpuset.cpus.exclusive
echo 2-3 > P/C/cpuset.cpus
echo 2 > P/C/cpuset.cpus.exclusive
echo root > P/C/cpuset.cpus.partition
(a task in P)
echo 2-3 > P/C/cpuset.cpus.exclusive
cat P/C/cpuset.cpus.partition
root invalid (Parent is not a partition root)
The effective_cpus of P is 3, a subset of the new exclusive CPUs 2-3 of
C, and P has a task, so the expansion is rejected. However, P is not a
partition root and does not give any CPU to C, and top_cpuset still has
CPUs 0-1 for the task. Enabling C directly with exclusive CPUs 2-3
succeeds, as remote_partition_enable() checks top_cpuset instead.
The no CPU left for tasks check now uses the given parent instead of
parent_cs(cs), and top_cpuset for a remote partition, as that is where
its CPUs are taken from.
The housekeeping conflict check is folded into validate_partition(). It
is skipped when the parent is not a valid partition root, as @cs can't
be a valid local partition in that case.
Use the new interface for local partition enablement in
update_parent_effective_cpumask() and in partition_cpus_change(),
replacing the open-coded checks there. The order of the checks is now
the same for both paths: empty CPUs, housekeeping conflict, then no CPU
left for tasks.
Add a test case to test_cpuset_prs.sh for the remote partition
expansion above.
Fixes: 181c8e091aae ("cgroup/cpuset: Introduce remote partition")
Signed-off-by: Ridong Chen <chenridong@xiaomi.com>
Reviewed-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
Reviewed-by: Waiman Long <longman@redhat.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
|
|
partition_xcpus_del() only updates isolated_cpus when the partition that
gives back the CPUs has a different state than its parent. CPUs that were
further distributed to descendant isolated partitions are not taken into
account, so isolated_cpus_release() has to be called afterwards in
several places to walk up the ancestors and fix isolated_cpus.
This misses some cases and leaks isolated CPUs, as reported by Guopeng.
An isolated partition can be invalidated after its parent has already
become invalid, and its CPUs are left in isolated_cpus. For example, on a
32-CPU system with all CPUs online and without isolcpus= or nohz_full=
boot parameters:
cd /sys/fs/cgroup
echo +cpuset > cgroup.subtree_control
mkdir A
echo 0,2-31 > A/cpuset.cpus
echo root > A/cpuset.cpus.partition
echo +cpuset > A/cgroup.subtree_control
mkdir A/B
echo 2-3 > A/B/cpuset.cpus
echo isolated > A/B/cpuset.cpus.partition
cat cpuset.cpus.isolated
2-3
echo 0 > /sys/devices/system/cpu/cpu1/online
cat A/B/cpuset.cpus.partition
isolated invalid
cat cpuset.cpus.isolated
2-3
When A is invalidated, partition_xcpus_del() gives CPUs 0,2-31 back to
top cpuset. Both A and top cpuset are root partitions, so isolated_cpus
is left untouched although CPUs 2-3 were distributed to the isolated B.
B is then invalidated with an invalid parent, and nothing releases CPUs
2-3 either.
Make partition_xcpus_del() always set the isolation state of the given
back CPUs to the state of the parent that receives them. As the
effective_xcpus of a partition covers the CPUs distributed to its
descendants, the isolation state of those CPUs is settled at the same
time. Boot-time isolated CPUs are still preserved by isolated_cpu_update().
compute_partition_effective_cpumask() invalidates a child partition
without going through partition_xcpus_del(), so do the same there: the
CPUs of the invalidated child take the isolation state of its parent.
As the parent may be shrunk and its effective_xcpus not updated yet,
only do so for the CPUs the parent still owns. This is to keep the
isolation state correct for now, the in-place invalidation here will be
removed later in the partition rework.
isolated_cpus_update() assumes the old and new states are different,
which no longer holds now that partition_xcpus_del() proceeds regardless
of the states. Drop its @old_prs argument and the WARN_ON_ONCE() so that
it simply sets the isolation state of the given CPUs, and use it
everywhere. The state check in partition_xcpus_add() is dropped as well,
as setting the state is a no-op when the states are the same.
isolated_cpus_release() is no longer needed and is removed.
Fixes: 11e5f407b64a ("cgroup/cpuset: Keep track of CPUs in isolated partitions")
Reported-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
Closes: https://lore.kernel.org/all/20261105130344.664336-4-guopeng.zhang@linux.dev/
Signed-off-by: Ridong Chen <chenridong@xiaomi.com>
Reviewed-by: Guopeng Zhang <zhangguopeng@kylinos.cn>
Reviewed-by: Waiman Long <longman@redhat.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
Pull sound fixes from Takashi Iwai:
"A collection of small fixes as usual. A couple of regression fixes are
included in addition to the various quirks and device-specific fixes.
ALSA Core:
- PCM: Fix potential inconsistent PCM state reporting after XRUN
HD-audio:
- Fix sysfs hint parser
- Revert CS4208 fixup for MacBookAir 7,2 due to regressions
- ACPI _DSD fixes for CS35L41 side-codec on various HP laptops
- Device quirks for Acer (Predator, TravelLite) and Dell (Pro QC1255,
XPS 8940)
USB-audio:
- Fix for USB controller bugs reporting oversized packets
- Fix UAF on disconnect in caiaq
- Quirks for NiceHCK Octave DAC and RYDZ Technology Piva AC20
ASoC:
- Fix a regression due to the conversion to devm_kzalloc_flex() that
initialized the counter unexpectedly
- Copy DAI link names into card device to survive component rebind
- SOF: Fix pin format memory leak in IPC4 process widget setup,
- SOF: Support alternatively signed firmware loading on AMD platforms
- AMD: Guard SoundWire context with NULL checks in IRQ handlers
- AMD: SoundWire support on LG gram 16Z95U, fix speaker pop noise on
ACP3x with ES83xx codecs, quirks for Acer, ASUS, Huawei, and Lenovo
- Qualcomm: Fix headset jack at card rebind, PCM position fix on
q6asm
- Apple: Fix clock selection for clock consumer FEs in MCA driver
- Intel: SoundWire jack-detection quirk for Dell Latitude 9420
- Codecs: Fixes for CS43130 (power down on close), ES9356 (gain dB
scale), and MAX98090 (preserve mic boost)"
* tag 'sound-7.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound: (34 commits)
ALSA: aw2-alsa: select SND_PCM
ALSA: usb-audio: Add native DSD support for NiceHCK Octave
Revert "ALSA: hda/cs420x: Add CS4208 fixup for MacBookAir 7,2"
ALSA: hda/realtek: Update quirk for Acer Predator PHN16-72
ALSA: hda/realtek - remove headphone MIC support for Dell Pro QC1255
ALSA: caiaq: Kill EP1 URB before unregistering the input device
ALSA: pcm: update state after xrun
ASoC: max98090: keep the MIC boost across mic input power-up
ALSA: hda/realtek: Fix the Dell XPS 8940 headset microphone
ASoC: amd: acp70: Add rt713 + rt1320 SoundWire machine for LG gram 16Z95U
ASoC: amd: acp: Add ACP70 ACPI flag override for LG gram 16Z95U
ASoC: apple: mca: Fix clock selection for clock consumer FEs
ASoC: soc-core: reset rtd->num_components after allocation
ASoC: SOF: ipc4-topology: Fix pin format leak in process widget setup
ALSA: usb-audio: Drop capture packets with bogus actual_length
ALSA: usb-audio: Add iface reset and delay quirk for RYDZ Technology Piva AC20
ASoC: amd: acp: Add Lenovo Legion 5 15AGP11 to ACP70 override table
ASoC: SOF: amd: Load alternatively signed firmware with an "_l" suffix
ASoC: es9356: fix the capture gain dB scale
ASoC: amd: acp: es83xx: Enable speaker amplifier after the codec output
...
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux
Pull block fixes from Jens Axboe:
- ublk fixes: don't publish a new device in the idr until it's fully
set up, and don't hold ublk_ctl_mutex across device removal, as a
stuck filesystem on one device otherwise blocked ADD_DEV and DEL_DEV
for every other ublk device.
- s390/dasd fixes: re-initialize the RCD buffer magic before every
request start, fix a wrong free and refcount leak in the check_tcw
error path, don't trust the userspace-supplied result field in the
format check, and a typo fix.
* tag 'block-7.4-20261112' of git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux:
s390/dasd: Don't trust userspace-supplied result field in format check
s390/dasd: Fix wrong free and refcount leak in build_check_tcw error path
s390/dasd: Re-initialize RCD buffer with "V1.0" before every start
s390/dasd: Fix typo 'immediatly' -> 'immediately'
ublk: don't take ublk_ctl_mutex in DEL_DEV
ublk: publish a new device by its id only once it is set up
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux
Pull io_uring fix from Jens Axboe:
- Don't end the NAPI busy poll early on need_resched() when a single
NAPI is registered, as that left the rest of the wait timeout
sleeping in schedule_hrtimeout() rather than busy polling.
* tag 'io_uring-7.4-20261112' of git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux:
io_uring/napi: don't end the single NAPI busy poll early on need_resched()
|
|
Pull smb client fixes from Paulo Alcantara:
- Fix silent data loss in writeback
Since the move to netfslib a transient failure (a reconnect, a lost
handle, an interrupted wait, -ENOMEM, or a task killed while close()
flushes its dirty pages) ended writeback with the folios clean and
no error, dropping the write.
Retry it instead, bounded by the hard and retrans mount options, and
have umount -f abort the retries and the reconnect and credit waits
so the unmount's own sync can't hang
- Prefer a non-O_DIRECT handle for writeback, as Windows rejects
unaligned I/O on O_DIRECT handles and silently dropped about 1% of
the writes in generic/051
- netfs: keep the prepare_read() and prepare_write() errno across a
reissue, and don't hang a read whose retry is abandoned (the
writeback fixes depend on these)
- Fix an out-of-bounds write when compounding an encrypted SMB2_IOCTL
with a large input, which an unprivileged user can trigger with a
long symlink target
- Fix an out-of-bounds read parsing a DFS target referral, and a
double conversion of the DFS path in setup_dfs_ref()
- Validate security descriptor headers before allocating the query
result, and compare owner and group SIDs by their encoded lengths
- Hold a server reference while queueing reconnect work so the server
can't be freed under the worker
- Hold the inode across cifs_oplock_break() so dropping the handle
reference can't free it before the break is acknowledged
- Flush an inode's deferred handles before opening another of its hard
links, so the open doesn't reuse the lease key under a mismatched
name and get rejected with STATUS_INVALID_PARAMETER
- Skip a NULL channel in __cifs_put_smb_ses()
- Bound the invalid NTLMSSP signature diagnostic
* tag 'cifs-fixes-7.4-rc3' of https://git.manguebit.org/linux: (29 commits)
smb: client: flush deferred handles of other names before a hard link open
smb: client: hold the inode across cifs_oplock_break()
smb: client: stop reconnecting and replaying during a forced unmount
smb: client: fail writeback sends and reopens fast when the server is gone
smb: client: don't replay handle reopens inside SMB2_open()
smb: client: let umount -f stop waiting for reconnects on hard mounts
smb: client: retry writeback after losing the connection, share or handle
smb: client: retry writes that couldn't be issued due to a reconnect
smb: client: don't block dying tasks waiting for writeback on fsync
smb: client: retry writeback on interrupts and allocation failures
smb: client: don't fail writeback preparation if the task is dying
smb: client: issue writes from a worker if the task is dying
smb: client: don't block dying tasks waiting for writeback on close
smb: client: don't spend read retries on reads cut short by a reconnect
smb: client: don't retry failed writes forever regardless of mount options
smb: client: don't give up writeback on the first replayable error
smb: client: let umount -f abort retried reads and writes
netfs: don't hang a read whose retry is abandoned
netfs: keep the prepare_read errno when abandoning read retries
netfs: preserve prepare_write errno on reissue
...
|
|
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs
Pull erofs fixes from Gao Xiang:
- Fix stacked fs check for file-backed mounts with extra devices
- Disallow file-backed mounts on shared backing inodes
- Reset metadata offsets when fsoffset= is used to fix xattr reads
inside and outside the metabox in ont shot
- Refine on-disk format summary
* tag 'erofs-for-7.4-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs:
docs: erofs: refine the on-disk overview
erofs: reset buf->off in erofs_init_metabuf()
erofs: treat files shared by inode_share as stacked
erofs: apply the stacked fs check to extra file-backed devices
|
|
Commit 19235e472798 ("cpuidle, arm64: Fix the ARM64 cpuidle logic") moved
the calls to ct_cpuidle_enter() and ct_cpuidle_exit() into cpu_suspend() so
that arm64 cpuidle could keep RCU watching longer and manage context
tracking internally. However, cpu_suspend() is called not only by cpuidle
via psci_cpu_suspend_enter() (which runs in the context of the idle task),
but also during system suspend via psci_system_suspend_enter() (which runs
in the context of the task initiating suspend, such as a process writing to
/sys/power/state).
When entering system suspend, current is a non-idle task. Calling
ct_cpuidle_enter() invokes ct_kernel_exit() from kernel space (!user) on a
non-idle task. With CONFIG_RCU_EQS_DEBUG enabled, this violates context
tracking invariants and triggers a warning:
WARNING: kernel/context_tracking.c:120 at ct_kernel_exit+0x1b4/0x1f4
kernel/context_tracking.c:118
Call trace:
ct_kernel_exit+0x1b4/0x1f4 kernel/context_tracking.c:118
ct_idle_enter+0x20/0x34 kernel/context_tracking.c:299
ct_cpuidle_enter include/linux/cpuidle.h:134 [inline]
cpu_suspend+0x264/0x474 arch/arm64/kernel/suspend.c:136
psci_system_suspend_enter+0x4c/0x80 drivers/firmware/psci/psci.c:544
suspend_enter kernel/power/suspend.c:468 [inline]
suspend_devices_and_enter+0x88c/0xd0c kernel/power/suspend.c:533
enter_state kernel/power/suspend.c:618 [inline]
pm_suspend+0x498/0x698 kernel/power/suspend.c:644
state_store+0x14c/0x1fc kernel/power/main.c:819
kobj_attr_store+0x6c/0x90 lib/kobject.c:842
sysfs_kf_write+0xe0/0x108 fs/sysfs/file.c:145
kernfs_fop_write_iter+0x260/0x3b8 fs/kernfs/file.c:345
vfs_write+0x51c/0xa0c fs/read_write.c:687
ksys_write+0x12c/0x228 fs/read_write.c:739
A corresponding warning is subsequently triggered in ct_kernel_enter() via
ct_cpuidle_exit() upon resume.
Fix this by checking is_idle_task(current) in cpu_suspend() and only
invoking ct_cpuidle_enter() and ct_cpuidle_exit() when executing in the
context of an idle task.
Fixes: 19235e472798 ("cpuidle, arm64: Fix the ARM64 cpuidle logic")
Cc: <stable@vger.kernel.org>
Assisted-by: Gemini:gemini-3.8-flash Gemini:gemini-3.1-pro-preview syzbot
Reported-by: syzbot+79883955da3a62652a80@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=79883955da3a62652a80
Link: https://syzkaller.appspot.com/ai_job?id=5359e16f-013b-4850-9cbc-ddfb3bac95e5
Signed-off-by: Uladzislau Zhauniarovich <uladzislau.zhauniarovich@gmail.com>
Tested-by: Uladzislau Zhauniarovich <uladzislau.zhauniarovich@gmail.com>
Link: https://lore.kernel.org/r/3e92ccb0-2952-4317-af4c-45457c15efae@gmail.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|
|
spi_engine_optimize_message() allocates the program with kzalloc_flex(),
which sets the __counted_by() counter "length" to the allocated size when
the compiler supports __builtin_counted_by_ref(). The program is then
filled by spi_engine_program_add_cmd(), which increments "length" and
stores at length - 1, expecting it to start at zero as it did when the
program came from kzalloc().
Reset "length" after the allocation, since it is a "usage" counter, not
a "total allocation" counter.
Build tested ARCH=x86_64 defconfig with CONFIG_SPI_AXI_SPI_ENGINE=m and
W=1, with GCC 16.2.0.
Reported-by: Dennis Gilmore <dennis@ausil.us>
Closes: https://lore.kernel.org/all/20261112025252.71375-1-dennis@ausil.us/
Fixes: 69050f8d6d075 ("treewide: Replace kmalloc with kmalloc_obj for non-scalar types")
Cc: stable@vger.kernel.org
Signed-off-by: Kees Cook <kees@kernel.org>
Reviewed-by: David Lechner <dlechner@baylibre.com>
Link: https://patch.msgid.link/20261113065508.i.606-kees@kernel.org
Signed-off-by: Mark Brown <broonie@kernel.org>
|
|
PTRACE_ATTACH to a group-stopped child can enter do_jobctl_trap(),
which calls ptrace_stop() without siginfo. If the tracer writes
NT_ARM_SYSTEM_CALL, system_call_set() can change syscallno from
NO_SYSCALL before update_syscall_orig_x0_after_ptrace() checks
last_siginfo. WARN_ON_ONCE(!info) then fires for a valid ptrace stop.
Keep the early return when siginfo is absent, but remove the warning.
This leaves orig_x0 untouched at a non-seized group-stop and preserves
the existing syscall-exit-stop handling.
Fixes: 88b839ce497c ("arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry")
Cc: stable@vger.kernel.org
Signed-off-by: Zhao Gongyi <zhaogongyi@bytedance.com>
Acked-by: Oleg Nesterov <oleg@redhat.com>
Acked-by: Will Deacon <will@kernel.org>
[catalin.marinas@arm.com: modified comment as per Will's suggestion]
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
|
|
When generating a default event name in __trace_uprobe_create(), tail is
allocated with kstrdup() without __free(kfree). If the subsequent
kmalloc() for buf fails, the function returns -ENOMEM immediately and
leaks tail.
Declare tail with __free(kfree) so it is automatically freed on all
exit paths.
Link: https://lore.kernel.org/all/179455856197.403392.16569431894958507645.stgit@devnote2/
Reported-by: Sashiko <sashiko-bot@kernel.org>
Closes: https://lore.kernel.org/all/sashiko-outbox-204240@kernel.org/
Fixes: 97e8230f89a3 ("tracing: uprobe-event: Allocate string buffers from heap")
Cc: stable@vger.kernel.org
Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
|