<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-toradex.git/arch, branch master</title>
<subtitle>Linux kernel for Apalis and Colibri modules</subtitle>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/'/>
<entry>
<title>Merge tag 'mm-hotfixes-stable-2026-11-17-19-55' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm</title>
<updated>2026-11-18T17:01:16+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-11-18T17:01:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=d866d5bafc5e1417032255002e95f8ec3121754b'/>
<id>d866d5bafc5e1417032255002e95f8ec3121754b</id>
<content type='text'>
Pull MM fixes from Andrew Morton:

 - "maple_tree fixes for 7.3" (Liam R. Howlett):

   Fix an RCU reader NULL dereference when the tree is emptied during a
   walk, including /proc/PID/maps racing with munmap(). Add tests and
   make debug WARN and BUG checks report failures properly

 - "mm/kasan: Detect double-free involving kfree_rcu_sheaf()" (Kuniyuki
   Iwashima):

   Detect double-free when an object enters an RCU sheaf. KASAN could
   previously miss it until the object was reused, leading to a later
   free of a live object. Add KUnit tests for the different free orders

 - "mm: Fix page-table teardown during memory hot-remove" (Muchun Song):

   Balance page-table constructors and destructors when hot-remove frees
   tables on x86-64, RISC-V and arm64. This fixes NR_PAGETABLE
   accounting for tables with and without constructors

 - "mm/damon: fix watermark state, kunit pid leak and selftest fake
   pass" (SJ Park):

   Recompute watermark wait state when DAMON schemes are removed, so
   kdamond resumes monitoring. Fix a pid reference leak in KUnit and a
   selftest that reports a skipped run as a pass

 - An XArray iterator could step backwards when a large page-cache entry
   was split, sending filemap_map_pages() outside the PTE page it
   locked. The XArray correction and a filemap bound check prevent
   out-of-bounds accesses and use-after-free. Another XArray fix
   prevents lockless walkers from following a parent pointer into a
   freed node

 - Userfaultfd now validates the whole write-protection range before
   changing any VMA, avoiding partial unprotect without waking blocked
   faults. Failed unmaps now abort queued UFFD_EVENT_UNMAPs; previously
   they could report a nonexistent unmap, leak the userfaultfd context
   and leave later operations returning -EAGAIN. A fork fix clears stale
   uffd PTE bits if the new context is released before its event is
   read

 - Moving the hugetlbfs inode trace event before RCU freeing avoids a
   use-after-free of its superblock. Shmem swapin no longer retries
   forever on reused swap slots containing a mismatched large swap-cache
   folio. Swapoff also avoids a cluster-list loop that can soft-lock
   reclaim and leave swapoff hung

 - Weighted interleave recalculation now uses one node set throughout,
   avoiding a divide-by-zero during memory hotplug. Hwpoison holds the
   folio lock when inspecting its mapping and no longer leaks a folio
   reference; it also updates poison statistics before notifying
   rasdaemon through a trace event

 - Cross-node migration now moves NR_FILE_THPS and NR_KERNEL_FILE_PAGES
   with page-cache folios, preventing per-node and memcg-node accounting
   from retaining stale counts or underflowing after the folios are
   freed

* tag 'mm-hotfixes-stable-2026-11-17-19-55' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (27 commits)
  xarray: fix index jumping backwards in xas_find()
  userfaultfd: validate the whole range before changing write protection
  maple_tree: update internal warning and bug_on code
  maple_tree: test emptying tree while RCU reading
  maple_tree: fix rcu reader NULL dereference after the tree is emptied
  mm/vma: read anon_vma carefully in validate_mm()
  hugetlbfs: move hugetlbfs_free_inode tracepoint to -&gt;destroy_inode()
  selftests/damon/sysfs_memcg_path_leak: define ksft_skip
  mm/damon/tests/sysfs-kunit: fix leaked pid reference in add_targets test
  mm/damon/core: reset watermark wait state on each iteration
  mm/filemap: stop fault-around when the walk steps back
  mm: memory-failure: update statistics before emitting the trace event
  mm/vma: undo userfaultfd unmap preparation when unmapping fails
  userfaultfd: clear uffd state in child PTEs if uffd is released during fork
  mm/memory-failure: fix folio refcount leak and min_order_for_split() locking
  mm/shmem: fix swapin livelock on a mismatched large swap cache folio
  mm/mempolicy: use one node set for interleave weights
  xarray: clear the new head's parent before freeing the old head
  arm64/mm: fix destructor for unconstructed hotplug page tables
  riscv/mm: fix missing destructor for hotplug PUD tables
  ...
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Pull MM fixes from Andrew Morton:

 - "maple_tree fixes for 7.3" (Liam R. Howlett):

   Fix an RCU reader NULL dereference when the tree is emptied during a
   walk, including /proc/PID/maps racing with munmap(). Add tests and
   make debug WARN and BUG checks report failures properly

 - "mm/kasan: Detect double-free involving kfree_rcu_sheaf()" (Kuniyuki
   Iwashima):

   Detect double-free when an object enters an RCU sheaf. KASAN could
   previously miss it until the object was reused, leading to a later
   free of a live object. Add KUnit tests for the different free orders

 - "mm: Fix page-table teardown during memory hot-remove" (Muchun Song):

   Balance page-table constructors and destructors when hot-remove frees
   tables on x86-64, RISC-V and arm64. This fixes NR_PAGETABLE
   accounting for tables with and without constructors

 - "mm/damon: fix watermark state, kunit pid leak and selftest fake
   pass" (SJ Park):

   Recompute watermark wait state when DAMON schemes are removed, so
   kdamond resumes monitoring. Fix a pid reference leak in KUnit and a
   selftest that reports a skipped run as a pass

 - An XArray iterator could step backwards when a large page-cache entry
   was split, sending filemap_map_pages() outside the PTE page it
   locked. The XArray correction and a filemap bound check prevent
   out-of-bounds accesses and use-after-free. Another XArray fix
   prevents lockless walkers from following a parent pointer into a
   freed node

 - Userfaultfd now validates the whole write-protection range before
   changing any VMA, avoiding partial unprotect without waking blocked
   faults. Failed unmaps now abort queued UFFD_EVENT_UNMAPs; previously
   they could report a nonexistent unmap, leak the userfaultfd context
   and leave later operations returning -EAGAIN. A fork fix clears stale
   uffd PTE bits if the new context is released before its event is
   read

 - Moving the hugetlbfs inode trace event before RCU freeing avoids a
   use-after-free of its superblock. Shmem swapin no longer retries
   forever on reused swap slots containing a mismatched large swap-cache
   folio. Swapoff also avoids a cluster-list loop that can soft-lock
   reclaim and leave swapoff hung

 - Weighted interleave recalculation now uses one node set throughout,
   avoiding a divide-by-zero during memory hotplug. Hwpoison holds the
   folio lock when inspecting its mapping and no longer leaks a folio
   reference; it also updates poison statistics before notifying
   rasdaemon through a trace event

 - Cross-node migration now moves NR_FILE_THPS and NR_KERNEL_FILE_PAGES
   with page-cache folios, preventing per-node and memcg-node accounting
   from retaining stale counts or underflowing after the folios are
   freed

* tag 'mm-hotfixes-stable-2026-11-17-19-55' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (27 commits)
  xarray: fix index jumping backwards in xas_find()
  userfaultfd: validate the whole range before changing write protection
  maple_tree: update internal warning and bug_on code
  maple_tree: test emptying tree while RCU reading
  maple_tree: fix rcu reader NULL dereference after the tree is emptied
  mm/vma: read anon_vma carefully in validate_mm()
  hugetlbfs: move hugetlbfs_free_inode tracepoint to -&gt;destroy_inode()
  selftests/damon/sysfs_memcg_path_leak: define ksft_skip
  mm/damon/tests/sysfs-kunit: fix leaked pid reference in add_targets test
  mm/damon/core: reset watermark wait state on each iteration
  mm/filemap: stop fault-around when the walk steps back
  mm: memory-failure: update statistics before emitting the trace event
  mm/vma: undo userfaultfd unmap preparation when unmapping fails
  userfaultfd: clear uffd state in child PTEs if uffd is released during fork
  mm/memory-failure: fix folio refcount leak and min_order_for_split() locking
  mm/shmem: fix swapin livelock on a mismatched large swap cache folio
  mm/mempolicy: use one node set for interleave weights
  xarray: clear the new head's parent before freeing the old head
  arm64/mm: fix destructor for unconstructed hotplug page tables
  riscv/mm: fix missing destructor for hotplug PUD tables
  ...
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'arc-fixes-7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc</title>
<updated>2026-11-18T02:55:10+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-11-18T02:55:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=20eef29b7c8465ac98d7dd6d6f2ac07a8d8056ca'/>
<id>20eef29b7c8465ac98d7dd6d6f2ac07a8d8056ca</id>
<content type='text'>
Pull ARC fix from Vineet Gupta:

 - workaround a GCC bug which has been causing upstream build fails

* tag 'arc-fixes-7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc:
  ARC: io: work around GCC PR127718 in __raw_write{w,l}()
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Pull ARC fix from Vineet Gupta:

 - workaround a GCC bug which has been causing upstream build fails

* tag 'arc-fixes-7.4' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc:
  ARC: io: work around GCC PR127718 in __raw_write{w,l}()
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'powerpc-7.4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux</title>
<updated>2026-11-18T02:27:24+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-11-18T02:27:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=7ccb044c27720d48175577080b851f047ddcfd1c'/>
<id>7ccb044c27720d48175577080b851f047ddcfd1c</id>
<content type='text'>
Pull powerpc fixes from Madhavan Srinivasan:

 - Handle of_property_count_u32_elems() error in parse_thread_groups()

 - Defer Nemo IRQ initialization

 - disable watchdog when watchdog_thresh=0

 - Reserve a PLT entry for ftrace_regs_caller

 - powerpc KVM fixes

 - misc fixes and cleanups

Thanks to Amit Machhiwal, Bradley Morgan, Christian Zigotzky, Christophe
Leroy, Gautam Menghani, Jiale Yao, Luiz Capitulino, Michael Ellerman,
Mohammad Shahid, Nathan Chancellor, Ritesh Harjani, Sasha Levin,
Shrikanth Hegde, and Timothy Pearson

* tag 'powerpc-7.4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
  powerpc/perf/vpa-dtl: use GFP_ATOMIC for DTL buffer allocation
  powerpc32/modules: Reserve a PLT entry for ftrace_regs_caller
  powerpc/watchdog: disable watchdog when watchdog_thresh=0
  selftests/powerpc: override EMIT_TESTS instead of the emit_tests rule
  powerpc/smp: Handle of_property_count_u32_elems() error in parse_thread_groups()
  powerpc/pasemi: Defer Nemo IRQ initialization
  KVM: PPC: Book3S HV: Avoid spurious interrupts caused by LPCR_MER bit
  KVM: PPC: Book3S HV: Take SRCU read lock around kvmppc_h_page_init() call
  KVM: PPC: Book3S HV: XICS: Avoid NULL ptr deref in kvmppc_xive_cleanup_vcpu()
  KVM: PPC: Book3S HV: XICS: Update irq_type for cleanup to work
  KVM: PPC: Book3S HV: Ensure that calls to idr_alloc are synchronized
  KVM: PPC: Book3S HV: Disable preemption around host-side HPT lock users
  powerpc/eeh: NUL-terminate force recovery input
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Pull powerpc fixes from Madhavan Srinivasan:

 - Handle of_property_count_u32_elems() error in parse_thread_groups()

 - Defer Nemo IRQ initialization

 - disable watchdog when watchdog_thresh=0

 - Reserve a PLT entry for ftrace_regs_caller

 - powerpc KVM fixes

 - misc fixes and cleanups

Thanks to Amit Machhiwal, Bradley Morgan, Christian Zigotzky, Christophe
Leroy, Gautam Menghani, Jiale Yao, Luiz Capitulino, Michael Ellerman,
Mohammad Shahid, Nathan Chancellor, Ritesh Harjani, Sasha Levin,
Shrikanth Hegde, and Timothy Pearson

* tag 'powerpc-7.4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
  powerpc/perf/vpa-dtl: use GFP_ATOMIC for DTL buffer allocation
  powerpc32/modules: Reserve a PLT entry for ftrace_regs_caller
  powerpc/watchdog: disable watchdog when watchdog_thresh=0
  selftests/powerpc: override EMIT_TESTS instead of the emit_tests rule
  powerpc/smp: Handle of_property_count_u32_elems() error in parse_thread_groups()
  powerpc/pasemi: Defer Nemo IRQ initialization
  KVM: PPC: Book3S HV: Avoid spurious interrupts caused by LPCR_MER bit
  KVM: PPC: Book3S HV: Take SRCU read lock around kvmppc_h_page_init() call
  KVM: PPC: Book3S HV: XICS: Avoid NULL ptr deref in kvmppc_xive_cleanup_vcpu()
  KVM: PPC: Book3S HV: XICS: Update irq_type for cleanup to work
  KVM: PPC: Book3S HV: Ensure that calls to idr_alloc are synchronized
  KVM: PPC: Book3S HV: Disable preemption around host-side HPT lock users
  powerpc/eeh: NUL-terminate force recovery input
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'x86-urgent-2026-11-15' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip</title>
<updated>2026-11-15T17:18:05+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-11-15T17:18:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=fa2933aac170dd19c6a7f0d7b81a8f537e40915c'/>
<id>fa2933aac170dd19c6a7f0d7b81a8f537e40915c</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'perf-urgent-2026-11-15' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip</title>
<updated>2026-11-15T17:01:48+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-11-15T17:01:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=ca6709295ae5420d1a391f32e6a7f23b7fda14b3'/>
<id>ca6709295ae5420d1a391f32e6a7f23b7fda14b3</id>
<content type='text'>
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-&gt;hrtimer_interval (Benjamin Segall)

 - Do not resurrect cpuctx-&gt;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-&gt;cgrp after last cgroup event exit
  perf: Fix racy update of cpc-&gt;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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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-&gt;hrtimer_interval (Benjamin Segall)

 - Do not resurrect cpuctx-&gt;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-&gt;cgrp after last cgroup event exit
  perf: Fix racy update of cpc-&gt;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
</pre>
</div>
</content>
</entry>
<entry>
<title>x86/mm: Ensure write visibility during LDT installation</title>
<updated>2026-11-15T11:53:02+00:00</updated>
<author>
<name>Dave Hansen</name>
<email>dave.hansen@linux.intel.com</email>
</author>
<published>2026-11-10T17:27:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=0dc2a4dac3d04e9e4479aeb0b46172feab1cca0a'/>
<id>0dc2a4dac3d04e9e4479aeb0b46172feab1cca0a</id>
<content type='text'>
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-&gt;context.ldt. The LDT-installing CPU
writes mm-&gt;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-&gt;context.ldt. Make
mm-&gt;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 &lt;jjy600901@snu.ac.kr&gt;
Signed-off-by: Dave Hansen &lt;dave.hansen@linux.intel.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;
Tested-by: Jaeyoung Chung &lt;jjy600901@snu.ac.kr&gt;
Acked-by: Linus Torvalds &lt;torvalds@linuxfoundation.org&gt;
Acked-by: Peter Zijlstra (Intel) &lt;peterz@infradead.org&gt;
Cc: &lt;stable@vger.kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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-&gt;context.ldt. The LDT-installing CPU
writes mm-&gt;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-&gt;context.ldt. Make
mm-&gt;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 &lt;jjy600901@snu.ac.kr&gt;
Signed-off-by: Dave Hansen &lt;dave.hansen@linux.intel.com&gt;
Signed-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;
Tested-by: Jaeyoung Chung &lt;jjy600901@snu.ac.kr&gt;
Acked-by: Linus Torvalds &lt;torvalds@linuxfoundation.org&gt;
Acked-by: Peter Zijlstra (Intel) &lt;peterz@infradead.org&gt;
Cc: &lt;stable@vger.kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ARC: io: work around GCC PR127718 in __raw_write{w,l}()</title>
<updated>2026-11-14T05:21:13+00:00</updated>
<author>
<name>Vineet Gupta</name>
<email>vgupta@kernel.org</email>
</author>
<published>2026-09-25T04:16:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=603b4fd69b4e77770761ea03451e2164186f8590'/>
<id>603b4fd69b4e77770761ea03451e2164186f8590</id>
<content type='text'>
The __raw_write{w,l}() accessors use inline asm with an "m" operand for
the store destination. GCC's ARC backend lets "m" match any legitimate
address, including the register-indexed [b,c] forms that only loads
support: stores only have [reg], [reg,s9] and [limm] addressing. With
newer GCC (late-combine in GCC 15, combine in GCC 16), a writew() with a
scaled, non-constant offset gets

	stw.as r2,[r0,r1]

which the assembler rejects:

  Error: inappropriate arguments for opcode 'stw'

With GCC 16 this breaks even hsdk_defconfig (drivers/net/pcs/
pcs-xpcs-plat.c) and axs101_defconfig. allyesconfig additionally trips
in drivers/pinctrl/renesas/pinctrl-rza2.c and drivers/video/fbdev/
s3c-fb.c.

Work around it by passing the address in a register and using a fixed
[%1] address in the asm template, so the compiler can't pick an
addressing mode that stores don't support. This is the minimal fix.
The next patch drops the inline asm altogether.

Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127718
Cc: stable@vger.kernel.org
Signed-off-by: Vineet Gupta &lt;vgupta@kernel.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The __raw_write{w,l}() accessors use inline asm with an "m" operand for
the store destination. GCC's ARC backend lets "m" match any legitimate
address, including the register-indexed [b,c] forms that only loads
support: stores only have [reg], [reg,s9] and [limm] addressing. With
newer GCC (late-combine in GCC 15, combine in GCC 16), a writew() with a
scaled, non-constant offset gets

	stw.as r2,[r0,r1]

which the assembler rejects:

  Error: inappropriate arguments for opcode 'stw'

With GCC 16 this breaks even hsdk_defconfig (drivers/net/pcs/
pcs-xpcs-plat.c) and axs101_defconfig. allyesconfig additionally trips
in drivers/pinctrl/renesas/pinctrl-rza2.c and drivers/video/fbdev/
s3c-fb.c.

Work around it by passing the address in a register and using a fixed
[%1] address in the asm template, so the compiler can't pick an
addressing mode that stores don't support. This is the minimal fix.
The next patch drops the inline asm altogether.

Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127718
Cc: stable@vger.kernel.org
Signed-off-by: Vineet Gupta &lt;vgupta@kernel.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux</title>
<updated>2026-11-13T21:44:27+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-11-13T21:44:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=97d73c8251226cf27cc6656b4c542869bb8c69fa'/>
<id>97d73c8251226cf27cc6656b4c542869bb8c69fa</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>arm64: suspend: Only track cpuidle context for idle tasks</title>
<updated>2026-11-13T17:12:34+00:00</updated>
<author>
<name>Uladzislau Zhauniarovich</name>
<email>uladzislau.zhauniarovich@gmail.com</email>
</author>
<published>2026-11-05T20:19:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=ad3fc05c7e65009355effeea06aa629a687acef2'/>
<id>ad3fc05c7e65009355effeea06aa629a687acef2</id>
<content type='text'>
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: &lt;stable@vger.kernel.org&gt;
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 &lt;uladzislau.zhauniarovich@gmail.com&gt;
Tested-by: Uladzislau Zhauniarovich &lt;uladzislau.zhauniarovich@gmail.com&gt;
Link: https://lore.kernel.org/r/3e92ccb0-2952-4317-af4c-45457c15efae@gmail.com
Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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: &lt;stable@vger.kernel.org&gt;
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 &lt;uladzislau.zhauniarovich@gmail.com&gt;
Tested-by: Uladzislau Zhauniarovich &lt;uladzislau.zhauniarovich@gmail.com&gt;
Link: https://lore.kernel.org/r/3e92ccb0-2952-4317-af4c-45457c15efae@gmail.com
Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>arm64: ptrace: don't warn on missing siginfo in a group-stop</title>
<updated>2026-11-13T14:10:36+00:00</updated>
<author>
<name>Zhao Gongyi</name>
<email>zhaogongyi@bytedance.com</email>
</author>
<published>2026-11-05T11:30:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=5306f124f3171289b2ef5bac1e08aad175f66d1e'/>
<id>5306f124f3171289b2ef5bac1e08aad175f66d1e</id>
<content type='text'>
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 &lt;zhaogongyi@bytedance.com&gt;
Acked-by: Oleg Nesterov &lt;oleg@redhat.com&gt;
Acked-by: Will Deacon &lt;will@kernel.org&gt;
[catalin.marinas@arm.com: modified comment as per Will's suggestion]
Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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 &lt;zhaogongyi@bytedance.com&gt;
Acked-by: Oleg Nesterov &lt;oleg@redhat.com&gt;
Acked-by: Will Deacon &lt;will@kernel.org&gt;
[catalin.marinas@arm.com: modified comment as per Will's suggestion]
Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
