<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-linux/arch/powerpc/kernel, branch stable</title>
<subtitle>WireGuard for the Linux kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-linux/atom/arch/powerpc/kernel?h=stable</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-linux/atom/arch/powerpc/kernel?h=stable'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/'/>
<updated>2026-10-23T23:49:34Z</updated>
<entry>
<title>powerpc/irq: Fix build with CONFIG_PROC_FS=n</title>
<updated>2026-10-23T23:49:34Z</updated>
<author>
<name>Sasha Levin</name>
<email>sashal@kernel.org</email>
</author>
<published>2026-10-23T21:15:03Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=4169c9c90532df9585c0a2ae513337a58f5e59ab'/>
<id>urn:sha1:4169c9c90532df9585c0a2ae513337a58f5e59ab</id>
<content type='text'>
Commit fbb22ceaaf8f ("powerpc/irq: Make irqstats array based") made
arch_show_interrupts() call irq_proc_emit_counts(). That function lives
in kernel/irq/proc.c, which is only built with CONFIG_PROC_FS, so
kernels without procfs no longer link:

  powerpc64-linux-ld: arch/powerpc/kernel/irq.o: in function `arch_show_interrupts':
  arch/powerpc/kernel/irq.c:134:(.text+0x4b8c): undefined reference to `irq_proc_emit_counts'

arch_show_interrupts() is only called from irq_seq_show(), which is in
kernel/irq/proc.c as well, so build it only with CONFIG_PROC_FS, as x86
already does.

Fixes: fbb22ceaaf8f ("powerpc/irq: Make irqstats array based")
Reported-by: kernel test robot &lt;lkp@intel.com&gt;
Closes: https://lore.kernel.org/oe-kbuild-all/202609271531.8kf2NTjK-lkp@intel.com/
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'powerpc-7.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux</title>
<updated>2026-10-22T18:05:19Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-10-22T18:05:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=bb2235894a8a604c08b3f93f4e1082b9df03265a'/>
<id>urn:sha1:bb2235894a8a604c08b3f93f4e1082b9df03265a</id>
<content type='text'>
Pull powerpc updates from Madhavan Srinivasan:

 - powerpc/numa: Support coregroup on PowerNV

 - powerpc/irq: Move __softirq_pending out of irq_stat

 - powerpc/512x: Remove pdm360ng platform setup in favor of mpc512x_generic

 - powerpc/ps3: Simplify control flow in ps3_{virq,irq_plug}_setup()

 - KVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users

 - powerpc/syscall: Avoid atomic test_and_clear_thread_flag on fast path

 - pseries/plpks cleanup and fixes

 - Misc fixes and cleanup

Thanks to Abhishek Dubey, Amit Machhiwal, Anushree Mathur, Bui Nguyen
Nhu Quynh, Christophe Leroy (CS GROUP), Dmitry Torokhov, Gaurav Batra,
Gautam Menghani, Geert Uytterhoeven, Greg Joyce, Hari Bathini, Harsh
Prateek Bora, Karl Mehltretter, Link Mauve, Michal Suchánek, Mukesh
Kumar Chaurasiya (IBM), Nayna Jain, Ritesh Harjani (IBM), R Nageswara
Sastry, Saket Kumar Bhaskar, Samir Mulani, Shivang Upadhyay, Shrikanth
Hegde, Sourabh Jain, Srikar Dronamraju, Srish Srinivasan, Thorsten Blum,
Vaibhav Jain (IBM), Venkat Rao Bagalkote, and Yeswanth Krishna Tellakula

* tag 'powerpc-7.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux: (44 commits)
  powerpc/numa: Support coregroup on PowerNV
  powerpc/numa: Allow cpu_to_coregroup_id without PPC_SPLPAR
  powerpc/numa: Simplify find_primary_domain_index
  powerpc/fadump: collect dump when CPU_STATE_DATA is less than reserved
  powerpc/syscall: Avoid atomic test_and_clear_thread_flag on fast path
  powerpc/kasan: fix r2 corruption in mem*() on GENERIC_ENTRY with old compilers
  powerpc: fix NMI exit ordering: restore soft masks after irqentry_nmi_exit()
  powerpc/pseries/iommu: Add TCEs for 16GB pages when RAM is pre-mapped
  KVM: PPC: Book3S HV: Free the queue pages in error path
  KVM: PPC: Book3S HV: Add missing mappings for tracing exits
  powerpc/interrupt: Use early_radix_enabled() in NMI real-mode guard
  KVM: PPC: Fix get_d_signext() 12-bit displacement for paired-single D-form
  KVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users
  KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls
  pseries/plpks: update PKS documentation and MAINTAINERS entry
  pseries/plpks: rename the default wrapping key macro
  pseries/plpks: make narrowing conversions explicit
  pseries/plpks: hide wrapping_features when unsupported
  pseries/plpks: fix self-reference in plpks_var initializer
  pseries/plpks: clear SED key data after use
  ...
</content>
</entry>
<entry>
<title>powerpc/align: use get_user_instr() for a user-mode instruction</title>
<updated>2026-10-20T20:14:13Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-10-20T20:05:40Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=5dcf33085cd095010eecf42d04c9101821361d8d'/>
<id>urn:sha1:5dcf33085cd095010eecf42d04c9101821361d8d</id>
<content type='text'>
fix_alignment() already reads the instruction with
copy_inst_from_kernel_nofault() when the PC is a kernel address, and
only uses __get_user_instr() when it is not.  That pointer is an
ordinary user address, so read it with get_user_instr().  On powerpc
__get_user() already does might_fault() and opens user access for the
read itself, so the only difference is the address check.

This is part of getting rid of __get_user() and __put_user() entirely.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>powerpc/signal64: use scoped user access in setup_trampoline()</title>
<updated>2026-10-20T20:13:50Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-10-20T20:05:11Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=52907f0e4765cba370ef07d536cf4e4ecea8c0ba'/>
<id>urn:sha1:52907f0e4765cba370ef07d536cf4e4ecea8c0ba</id>
<content type='text'>
setup_trampoline() writes the seven words of the on-stack sigreturn
trampoline with __put_user(), relying on the frame having been checked
when the frame setup opened its user write access.  It is called after
that access has been closed again, so each of the seven writes opens and
closes user access on its own.

Write them inside one scoped_user_write_access_size() covering the
whole trampoline instead.  Everything in it is a store, so a write-only
window is enough, and the instruction cache flush stays outside it.

This is part of getting rid of __get_user() and __put_user() entirely.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>powerpc/signal64: use get_user() for the single context reads</title>
<updated>2026-10-20T20:13:50Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-10-20T20:04:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=2f0bb47c0007d9293154e192a0598f8978a97b96'/>
<id>urn:sha1:2f0bb47c0007d9293154e192a0598f8978a97b96</id>
<content type='text'>
swapcontext and rt_sigreturn read the signal mask with
__get_user_sigset(), and rt_sigreturn also reads the MSR and uc_link
words of the transactional-memory path, each with one __get_user()
after an access_ok() on the whole context.

Make the helper get_user_sigset(), built on get_user(), and use
get_user() for the other two.  On powerpc __get_user() already does
might_fault() and opens user access for the read itself, so the only
difference is the address check, which these pointers pass anyway.

This is part of getting rid of __get_user() and __put_user() entirely.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>powerpc/signal32: use get_user() for the single context reads</title>
<updated>2026-10-20T20:13:50Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-10-20T20:03:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=cc3ff64abc0dae390d72770e961be1776d580d93'/>
<id>urn:sha1:cc3ff64abc0dae390d72770e961be1776d580d93</id>
<content type='text'>
A few places in the 32-bit and compat signal code read a single field
with __get_user(): the uc_regs and MSR words in swapcontext and the
transactional-memory sigreturn and setcontext paths, and uc_link in
rt_sigreturn.  They are not part of a run of accesses, and either rely
on an earlier access_ok() or on compat pointers being below 4GB.

Use get_user().  On powerpc __get_user() already does might_fault() and
opens user access for the read itself, so the only difference is the
address check, which these pointers pass anyway.

This is part of getting rid of __get_user() and __put_user() entirely.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>powerpc/syscall: Avoid atomic test_and_clear_thread_flag on fast path</title>
<updated>2026-10-12T04:01:44Z</updated>
<author>
<name>Mukesh Kumar Chaurasiya (IBM)</name>
<email>mkchauras@gmail.com</email>
</author>
<published>2026-09-29T07:17:44Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=66236558dfac63d9bea5b0b6a66a4d717529c118'/>
<id>urn:sha1:66236558dfac63d9bea5b0b6a66a4d717529c118</id>
<content type='text'>
In system_call_exception(), test_and_clear_thread_flag(TIF_SYSCALL_RET)
performs an atomic bit test-and-clear operation on every system call entry.
This introduces an unnecessary performance regression on the syscall fast
path.

Combine the TIF_SYSCALL_RET check with the unlikely error condition from
syscall_enter_from_user_mode_randomize_stack() using non-atomic
test_thread_flag(). If the flag is set or entry failed, only then clear the
flag via clear_thread_flag() and return the error value.

Signed-off-by: Mukesh Kumar Chaurasiya (IBM) &lt;mkchauras@gmail.com&gt;
Signed-off-by: Madhavan Srinivasan &lt;maddy@linux.ibm.com&gt;
Link: https://patch.msgid.link/20260929071744.2965058-1-mkchauras@gmail.com

</content>
</entry>
<entry>
<title>powerpc/kasan: fix r2 corruption in mem*() on GENERIC_ENTRY with old compilers</title>
<updated>2026-10-12T04:00:48Z</updated>
<author>
<name>Mukesh Kumar Chaurasiya (IBM)</name>
<email>mkchauras@gmail.com</email>
</author>
<published>2026-10-03T09:40:06Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=de5a7fedf5061bdf6823eb509353bd7c128e34b5'/>
<id>urn:sha1:de5a7fedf5061bdf6823eb509353bd7c128e34b5</id>
<content type='text'>
commit bee25f97ad24 ("powerpc: Enable GENERIC_ENTRY feature") introduced
a bug that, when CONFIG_CC_HAS_KASAN_MEMINTRINSIC_PREFIX is not
set, expand to two consecutive ELFv2 global entry points for the
same function body:

  _GLOBAL_TOC_KASAN(memcpy) expands to:
    _GLOBAL_TOC(memcpy);
    _GLOBAL_TOC(__memcpy)

On powerpc64le this produces:

  memcpy:
    addis r2,r12,(.TOC.-0b)@ha     &lt;- global entry, sets up r2
    addi  r2,r2,(.TOC.-0b)@l
    .localentry memcpy,.-memcpy    &lt;- local entry at memcpy+8
  __memcpy:
    addis r2,r12,(.TOC.-0b)@ha    &lt;- memcpy+8: __memcpy global entry
    addi  r2,r2,(.TOC.-0b)@l
    .localentry __memcpy,.-__memcpy

The assembler sets memcpy's st_other field so its local entry offset is
8 bytes past the global entry point.  The linker resolves same-TOC
calls to the local entry, so every same-TOC caller of memcpy() lands
at memcpy+8 — which is the beginning of the __memcpy global-entry TOC
prologue.  That prologue uses r12 as the base to recompute r2, but r12
holds whatever the caller left in it (not the address of memcpy+8).
The result is r2 pointing at garbage on return.  Same-TOC callers do
not reload r2 after the call, so the first TOC-relative access after
returning from memcpy() or memmove() crashes or silently corrupts data.

With GENERIC_ENTRY selected, mm/kasan/shadow.c no longer provides its
own memcpy()/memmove()/memset() wrappers, so on a toolchain without
-mllvm -asan-kernel-mem-intrinsic-prefix=1 (e.g. GCC 9) every
instrumented file resolves mem*() directly to the assembly symbols and
hits this corrupt-r2 path.  This manifests as an early boot hang unique
to powerpc with GCC 9 and CONFIG_KASAN=y.

Fix this by removing the dual-entry macros entirely.  The assembly
files in mem_64.S, memcpy_64.S and copy_32.S now use plain
_GLOBAL()/_GLOBAL_TOC() for memset/memcpy/memmove, emitting a single
correct ELFv2 entry point.  The __mem* aliases required by mm/kasan
(used in mm/kasan/shadow.c and mm/kasan/generic.c as raw backends to
bypass KASAN checking) are provided entirely through the #define
redirections in asm/string.h, which already handles both the
CC_HAS_KASAN_MEMINTRINSIC_PREFIX and non-prefix cases in C.

As a consequence the _GLOBAL_KASAN(), _GLOBAL_TOC_KASAN() and
EXPORT_SYMBOL_KASAN() macros have no remaining users and are removed
from asm/kasan.h.  The has_renamed_memintrinsics() branch in
prom_init_check.sh, which conditionally whitelisted __memcpy/__memset
when CONFIG_CC_HAS_KASAN_MEMINTRINSIC_PREFIX was absent, is dead code
after this change and is removed; the whitelist now unconditionally
lists memcpy and memset.

Fixes: bee25f97ad24 ("powerpc: Enable GENERIC_ENTRY feature")
Reported-by: Venkat Rao Bagalkote &lt;venkat88@linux.ibm.com&gt;
Closes: https://lore.kernel.org/all/96dae110-f79b-4e54-8a9b-514369019b5d@linux.ibm.com
Tested-by: Venkat Rao Bagalkote &lt;venkat88@linux.ibm.com&gt;
Signed-off-by: Mukesh Kumar Chaurasiya (IBM) &lt;mkchauras@gmail.com&gt;
[Maddy: Fixed commit message to avoid checkpatch error]
Signed-off-by: Madhavan Srinivasan &lt;maddy@linux.ibm.com&gt;
Link: https://patch.msgid.link/20261003094006.3404731-1-mkchauras@gmail.com
</content>
</entry>
<entry>
<title>Merge tag 'random-7.3-rc6-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/crng/random</title>
<updated>2026-10-02T18:28:45Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-10-02T18:28:45Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=ac7445c28e7a28d5131bc9f9a143261e79495027'/>
<id>urn:sha1:ac7445c28e7a28d5131bc9f9a143261e79495027</id>
<content type='text'>
Pull random number generator fixes from Jason Donenfeld:

 - VMGENID memory needs to be mapped with the decrypted tag, so that
   SEV-SNP machines can boot

 - A fix for an initialization race in VMGENID, followed by a cleanup

 - Trivial kernel doc cleanups in siphash and random.c

 - A fix for a new compilation failure with recent clang on PPC and
   RISC-V, due to generating an out-of-line memset in the vDSO

* tag 'random-7.3-rc6-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/crng/random:
  random: vDSO: avoid call to memset() when zeroing reserved parameter
  random: fix vgetrandom_opaque_params kernel-doc
  random: vDSO: fix repeated word 'to' in comment
  siphash: clean up kernel-doc comments
  virt: vmgenid: move to using dev_set/get_drvdata
  virt: vmgenid: set driver_data before registering notification handlers
  virt: vmgenid: remap memory as decrypted
</content>
</entry>
<entry>
<title>random: vDSO: avoid call to memset() when zeroing reserved parameter</title>
<updated>2026-10-02T10:12:13Z</updated>
<author>
<name>Nathan Chancellor</name>
<email>nathan@kernel.org</email>
</author>
<published>2026-09-25T21:46:32Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-linux/commit/?id=eb13a1ff271b0d180687eebb30611b0b276d5193'/>
<id>urn:sha1:eb13a1ff271b0d180687eebb30611b0b276d5193</id>
<content type='text'>
After a recent change in LLVM [1], builds with the random vDSO
implementation, such as PowerPC and RISC-V, fail when checking the vDSO:

  arch/powerpc/kernel/vdso/vdso32.so.dbg: dynamic relocations are not supported
  arch/riscv/kernel/vdso/vdso.so.dbg: dynamic relocations are not supported

memset() is now generated when zeroing params-&gt;reserved for some builds
because LLVM has an optimization (now run in more instances) that can
recognize at compile time when it is assigning a static value to a
contiguous area of memory and turn that into a call to memset(). Both
clang and GCC assume memset() is always available [2].

Clang has an internal fiddly hook, -max-store-memset, which we can set
to a high number, to disable generating out of line memset calls [3].
Similarly, GCC has -finline-stringops=memset to do the same [4], should
this issue ever hit future version of GCC. While these options wouldn't
make sense for normal kernel code, it is fine for the extremely limited
and intentionally compact vDSO code.

Link: https://github.com/llvm/llvm-project/commit/90cebef1411617fc3eedd359bdf00cb44b1c2439 [1]
Link: https://gcc.gnu.org/onlinedocs/gcc-16.2.0/gcc/Standards.html#index-ffreestanding [2]
Link: https://github.com/llvm/llvm-project/commit/b28eeb28bea39148738dc375e8a97072a1907e64 [3]
Link: https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-finline-stringops [4]
Closes: https://github.com/ClangBuiltLinux/linux/issues/2183
Cc: stable@vger.kernel.org # v6.12+
Signed-off-by: Nathan Chancellor &lt;nathan@kernel.org&gt;
Signed-off-by: Jason A. Donenfeld &lt;Jason@zx2c4.com&gt;
</content>
</entry>
</feed>
