<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-toradex.git/arch/x86, 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 'bpf-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf</title>
<updated>2026-11-21T01:41:06+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-11-21T01:41:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=84afebd853437e44cb71f718be11d90e4c1a59dd'/>
<id>84afebd853437e44cb71f718be11d90e4c1a59dd</id>
<content type='text'>
Pull bpf fixes from Alexei Starovoitov:
 "Mostly sockmap fixes as promised, plus uprobe ctx rewrite via bpf and
  cgroup-bpf fixes.

   - Reject writable map iterators on read-only maps (Adethya
     Srinivasan)

   - Various sockmap fixes (Alexei Starovoitov):
       - Clear the redirect target before the sk_msg prog runs
       - Check that the redirected message is the cork
       - Leave sk_stream_wait_memory() once the socket is dead
       - Keep the rest of the cork after a redirect
       - Don't let an SK_PASS verdict cover the next message
       - Subtract all dropped bytes from the return value of sendmsg()
       - Clear the end mark of elements added by bpf_msg_push_data() and
         bpf_msg_pop_data()

   - Fix ring capacity invariant break in bpf_msg_push_data() (Bo Cao)

   - Report RCU-tasks quiescent states in do_check() to fix rcu_tasks
     stalls during a long verification (Breno Leitao)

   - Various sockmap fixes (Chris Mason):
       - Give no progs to a TCP listener
       - Check the target of an egress redirect before each send
       - Check the TCP state in recvmsg()
       - Reset the copy position when corking
       - Don't copy 0 bytes into a full cork

   - Use a dedicated workqueue for freeing BPF programs to fix a
     deadlock between pack_mutex waiters and the vmalloc purge work
     (Emil Tsalapatis)

   - Fix verifier model mismatch on a narrow read of
     __sk_buff.remote_port (Henry Martin)

   - Fix bpf-gcc CO-RE relocation in verifier_sockmap_mutate selftest
     (Jiayuan Chen)

   - Restrict uprobe ctx writes to the registers that ptrace can set
     (Jiri Olsa)

   - Various sockmap fixes (Josef Bacik):
       - Write sg.start when recvmsg() faults
       - Don't let an SK_DROP verdict stick
       - Clear the resume state of a stopped psock

   - Various fixes (Michal Luczaj):
       - Fix "unresolved symbol tcp_request_sock" build error with
         CONFIG_INET=n
       - Restrict iter-context sockmap updates to iter/sockmap
       - Restrict bpf_sock_destroy() to iter/{tcp,udp}
       - Mark bpf_iter__sockmap::sk as PTR_TRUSTED

   - Mark backing_file_alloc/free LSM hooks as untrusted (Sergei
     Nizovtsev)

   - Various cgroup-bpf fixes (Shakeel Butt):
       - Don't read freed effective arrays in BPF_PROG_QUERY
       - Don't attach to a removed cgroup
       - Protect cgroup_bpf state with its own mutex, so that queries
         and the release work don't wait for cgroup_mutex
       - Don't lose errors in effective BPF_LSM_CGROUP queries

   - Check variable-offset accesses against special fields (Shihuang
     Liu)"

* tag 'bpf-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf: (38 commits)
  selftests/bpf: Test which ctx registers a uprobe prog can write
  bpf: Restrict uprobe ctx writes to the registers ptrace can set
  selftests/bpf: Fix bpf-gcc CO-RE relocation in verifier_sockmap_mutate
  bpf, cgroup: Don't lose errors in effective BPF_LSM_CGROUP queries
  bpf, cgroup: Protect cgroup_bpf state with its own mutex
  bpf, cgroup: Don't attach to a removed cgroup
  bpf, cgroup: Don't read freed effective arrays in BPF_PROG_QUERY
  bpf: Fix verifier model mismatch on __sk_buff.remote_port narrow read
  bpf: Fix "unresolved symbol tcp_request_sock" build error
  selftests/bpf: Add iter/sockmap bpf_sock_destroy() negative test
  bpf: Mark bpf_iter__sockmap::sk as PTR_TRUSTED
  bpf: Restrict bpf_sock_destroy() to iter/{tcp,udp}
  bpf, docs: Document BPF_ITER_NOSLEEP
  selftests/bpf: Add negative test for sockmap update from non-sockmap iter
  bpf, sockmap: Restrict iter-context sockmap updates to iter/sockmap
  selftests/bpf: Remove sockmap update from bpf_iter_unix
  bpf, lsm: Mark backing_file_alloc/free LSM hooks as untrusted
  bpf: Report RCU-tasks quiescent states in do_check()
  bpf: Check variable-offset accesses against special fields
  bpf: Use dedicated workqueue for freeing BPF programs
  ...
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Pull bpf fixes from Alexei Starovoitov:
 "Mostly sockmap fixes as promised, plus uprobe ctx rewrite via bpf and
  cgroup-bpf fixes.

   - Reject writable map iterators on read-only maps (Adethya
     Srinivasan)

   - Various sockmap fixes (Alexei Starovoitov):
       - Clear the redirect target before the sk_msg prog runs
       - Check that the redirected message is the cork
       - Leave sk_stream_wait_memory() once the socket is dead
       - Keep the rest of the cork after a redirect
       - Don't let an SK_PASS verdict cover the next message
       - Subtract all dropped bytes from the return value of sendmsg()
       - Clear the end mark of elements added by bpf_msg_push_data() and
         bpf_msg_pop_data()

   - Fix ring capacity invariant break in bpf_msg_push_data() (Bo Cao)

   - Report RCU-tasks quiescent states in do_check() to fix rcu_tasks
     stalls during a long verification (Breno Leitao)

   - Various sockmap fixes (Chris Mason):
       - Give no progs to a TCP listener
       - Check the target of an egress redirect before each send
       - Check the TCP state in recvmsg()
       - Reset the copy position when corking
       - Don't copy 0 bytes into a full cork

   - Use a dedicated workqueue for freeing BPF programs to fix a
     deadlock between pack_mutex waiters and the vmalloc purge work
     (Emil Tsalapatis)

   - Fix verifier model mismatch on a narrow read of
     __sk_buff.remote_port (Henry Martin)

   - Fix bpf-gcc CO-RE relocation in verifier_sockmap_mutate selftest
     (Jiayuan Chen)

   - Restrict uprobe ctx writes to the registers that ptrace can set
     (Jiri Olsa)

   - Various sockmap fixes (Josef Bacik):
       - Write sg.start when recvmsg() faults
       - Don't let an SK_DROP verdict stick
       - Clear the resume state of a stopped psock

   - Various fixes (Michal Luczaj):
       - Fix "unresolved symbol tcp_request_sock" build error with
         CONFIG_INET=n
       - Restrict iter-context sockmap updates to iter/sockmap
       - Restrict bpf_sock_destroy() to iter/{tcp,udp}
       - Mark bpf_iter__sockmap::sk as PTR_TRUSTED

   - Mark backing_file_alloc/free LSM hooks as untrusted (Sergei
     Nizovtsev)

   - Various cgroup-bpf fixes (Shakeel Butt):
       - Don't read freed effective arrays in BPF_PROG_QUERY
       - Don't attach to a removed cgroup
       - Protect cgroup_bpf state with its own mutex, so that queries
         and the release work don't wait for cgroup_mutex
       - Don't lose errors in effective BPF_LSM_CGROUP queries

   - Check variable-offset accesses against special fields (Shihuang
     Liu)"

* tag 'bpf-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf: (38 commits)
  selftests/bpf: Test which ctx registers a uprobe prog can write
  bpf: Restrict uprobe ctx writes to the registers ptrace can set
  selftests/bpf: Fix bpf-gcc CO-RE relocation in verifier_sockmap_mutate
  bpf, cgroup: Don't lose errors in effective BPF_LSM_CGROUP queries
  bpf, cgroup: Protect cgroup_bpf state with its own mutex
  bpf, cgroup: Don't attach to a removed cgroup
  bpf, cgroup: Don't read freed effective arrays in BPF_PROG_QUERY
  bpf: Fix verifier model mismatch on __sk_buff.remote_port narrow read
  bpf: Fix "unresolved symbol tcp_request_sock" build error
  selftests/bpf: Add iter/sockmap bpf_sock_destroy() negative test
  bpf: Mark bpf_iter__sockmap::sk as PTR_TRUSTED
  bpf: Restrict bpf_sock_destroy() to iter/{tcp,udp}
  bpf, docs: Document BPF_ITER_NOSLEEP
  selftests/bpf: Add negative test for sockmap update from non-sockmap iter
  bpf, sockmap: Restrict iter-context sockmap updates to iter/sockmap
  selftests/bpf: Remove sockmap update from bpf_iter_unix
  bpf, lsm: Mark backing_file_alloc/free LSM hooks as untrusted
  bpf: Report RCU-tasks quiescent states in do_check()
  bpf: Check variable-offset accesses against special fields
  bpf: Use dedicated workqueue for freeing BPF programs
  ...
</pre>
</div>
</content>
</entry>
<entry>
<title>bpf: Restrict uprobe ctx writes to the registers ptrace can set</title>
<updated>2026-11-20T02:30:59+00:00</updated>
<author>
<name>Jiri Olsa</name>
<email>jolsa@kernel.org</email>
</author>
<published>2026-11-18T08:44:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=ca44731a7009da1dbcdf1979438d1985d93331d1'/>
<id>ca44731a7009da1dbcdf1979438d1985d93331d1</id>
<content type='text'>
Since commit 7384893d970e ("bpf: Allow uprobe program to change context
registers") a uprobe program can write any field of struct pt_regs.
Some of those fields are not plain user registers. The exit to user
space loads them into the CPU:

  arch    field   exit path                        ptrace
  ------  ------  -------------------------------  ------------------
  riscv   status  csrw CSR_STATUS, a0              not in the regset
  arm64   pstate  msr spsr_el1, x22                valid_user_regs()
  x86-64  cs, ss  (cs &amp; 3) == 0: iretq to ring 0   set_segment_reg()
  x86-64  flags   iretq loads IF and IOPL          set_flags()

On riscv a program that sets sstatus.SPP in pt_regs.status makes
ret_from_exception return to user code in supervisor mode. On x86-64 a
program that writes a kernel selector to cs makes iretq return to
ring 0.
ptrace guards these fields, but the bpf verifier does not.

Add arch_uprobe_regs_writable(). Each arch lists the registers that
ptrace can set to any value, and kprobe_prog_is_valid_access() rejects
writes to any other offset when the program is loaded:

  arm64:   x0 to x30, sp, pc
  riscv:   epc, ra to t6
  x86-64:  r15 to di, ip, sp

The default is no writes, so arches without a list (and 32-bit x86)
lose ctx writes for uprobe programs. Reads are not affected.

flags on x86-64 and pstate on arm64 become read-only, including the
condition bits that ptrace would let a debugger change. orig_ax is
read-only too.

Kprobe programs that write ctx were already rejected when they were
attached. Those that write one of these fields now fail to load.

Fixes: 7384893d970e ("bpf: Allow uprobe program to change context registers")
Reported-by: rtm@csail.mit.edu
Suggested-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Signed-off-by: Jiri Olsa &lt;jolsa@kernel.org&gt;
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Cc: stable@vger.kernel.org
Link: https://patch.msgid.link/20261118084451.12590-2-jolsa@kernel.org
Closes: https://lore.kernel.org/bpf/30318.1794850523@30-11-166.wireless.csail.mit.edu/
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Since commit 7384893d970e ("bpf: Allow uprobe program to change context
registers") a uprobe program can write any field of struct pt_regs.
Some of those fields are not plain user registers. The exit to user
space loads them into the CPU:

  arch    field   exit path                        ptrace
  ------  ------  -------------------------------  ------------------
  riscv   status  csrw CSR_STATUS, a0              not in the regset
  arm64   pstate  msr spsr_el1, x22                valid_user_regs()
  x86-64  cs, ss  (cs &amp; 3) == 0: iretq to ring 0   set_segment_reg()
  x86-64  flags   iretq loads IF and IOPL          set_flags()

On riscv a program that sets sstatus.SPP in pt_regs.status makes
ret_from_exception return to user code in supervisor mode. On x86-64 a
program that writes a kernel selector to cs makes iretq return to
ring 0.
ptrace guards these fields, but the bpf verifier does not.

Add arch_uprobe_regs_writable(). Each arch lists the registers that
ptrace can set to any value, and kprobe_prog_is_valid_access() rejects
writes to any other offset when the program is loaded:

  arm64:   x0 to x30, sp, pc
  riscv:   epc, ra to t6
  x86-64:  r15 to di, ip, sp

The default is no writes, so arches without a list (and 32-bit x86)
lose ctx writes for uprobe programs. Reads are not affected.

flags on x86-64 and pstate on arm64 become read-only, including the
condition bits that ptrace would let a debugger change. orig_ax is
read-only too.

Kprobe programs that write ctx were already rejected when they were
attached. Those that write one of these fields now fail to load.

Fixes: 7384893d970e ("bpf: Allow uprobe program to change context registers")
Reported-by: rtm@csail.mit.edu
Suggested-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Signed-off-by: Jiri Olsa &lt;jolsa@kernel.org&gt;
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Cc: stable@vger.kernel.org
Link: https://patch.msgid.link/20261118084451.12590-2-jolsa@kernel.org
Closes: https://lore.kernel.org/bpf/30318.1794850523@30-11-166.wireless.csail.mit.edu/
</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>x86/video: Preserve the default VGA fallback for legacy modes</title>
<updated>2026-11-13T04:01:18+00:00</updated>
<author>
<name>Hengyu Liang</name>
<email>hengyul@cs.unc.edu</email>
</author>
<published>2026-11-03T03:16:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=3b4c98b47ba7c3c57bcf54fb85f54a854622041c'/>
<id>3b4c98b47ba7c3c57bcf54fb85f54a854622041c</id>
<content type='text'>
Commit

  596b3678326d ("x86/video: Only fall back to vga_default_device() without screen info")

made video_is_primary_device() rely exclusively on screen_info resources
whenever any are available.

However, screen_info_resources() also returns legacy I/O and memory ranges for
VGA text modes. These ranges are not PCI BARs, so pci_find_resource() does not
find them and the default VGA fallback is skipped. As a result, no device is
primary in VGA text mode.

On a SeaBIOS QEMU guest with bochs and VKMS, the boot VGA (bochs) loses its
DRM boot_display attribute. VKMS registers fb0 and bochs registers fb1. VKMS
is not a PCI device, so it is not primary either. With no primary device,
fbcon keeps the console on fb0 and never remaps it to bochs. This can be
checked with:

  cat /sys/class/drm/card1/boot_display
  stty -F /dev/tty1 size

Without the fix, boot_display is missing and tty1 is 48 rows by 128 columns.
With it, boot_display contains 1 and tty1 is 50 rows by 160 columns. VKMS only
makes the console part visible. Without VKMS, tty1 has the same size with and
without the fix, but boot_display is still missing without it.

Use resource-based selection only for linear framebuffers. Fall back to
vga_default_device() for legacy display modes, while keeping EFI and VESA
framebuffer ownership authoritative.

Fixes: 596b3678326d ("x86/video: Only fall back to vga_default_device() without screen info")
Signed-off-by: Hengyu Liang &lt;hengyul@cs.unc.edu&gt;
Signed-off-by: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;
Reviewed-by: Mario Limonciello (AMD) &lt;superm1@kernel.org&gt;
Reviewed-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;
Cc: stable@vger.kernel.org
Link: https://patch.msgid.link/20261103031630.2085194-1-hengyul@cs.unc.edu
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Commit

  596b3678326d ("x86/video: Only fall back to vga_default_device() without screen info")

made video_is_primary_device() rely exclusively on screen_info resources
whenever any are available.

However, screen_info_resources() also returns legacy I/O and memory ranges for
VGA text modes. These ranges are not PCI BARs, so pci_find_resource() does not
find them and the default VGA fallback is skipped. As a result, no device is
primary in VGA text mode.

On a SeaBIOS QEMU guest with bochs and VKMS, the boot VGA (bochs) loses its
DRM boot_display attribute. VKMS registers fb0 and bochs registers fb1. VKMS
is not a PCI device, so it is not primary either. With no primary device,
fbcon keeps the console on fb0 and never remaps it to bochs. This can be
checked with:

  cat /sys/class/drm/card1/boot_display
  stty -F /dev/tty1 size

Without the fix, boot_display is missing and tty1 is 48 rows by 128 columns.
With it, boot_display contains 1 and tty1 is 50 rows by 160 columns. VKMS only
makes the console part visible. Without VKMS, tty1 has the same size with and
without the fix, but boot_display is still missing without it.

Use resource-based selection only for linear framebuffers. Fall back to
vga_default_device() for legacy display modes, while keeping EFI and VESA
framebuffer ownership authoritative.

Fixes: 596b3678326d ("x86/video: Only fall back to vga_default_device() without screen info")
Signed-off-by: Hengyu Liang &lt;hengyul@cs.unc.edu&gt;
Signed-off-by: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;
Reviewed-by: Mario Limonciello (AMD) &lt;superm1@kernel.org&gt;
Reviewed-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;
Cc: stable@vger.kernel.org
Link: https://patch.msgid.link/20261103031630.2085194-1-hengyul@cs.unc.edu
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'x86_bugs_tsa_zen5' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip</title>
<updated>2026-11-10T00:44:12+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-11-10T00:44:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=05e72bd3385972828b30354be4917fcd5ab2d6d2'/>
<id>05e72bd3385972828b30354be4917fcd5ab2d6d2</id>
<content type='text'>
Pull x86 TSA fix from Borislav Petkov:

 - A mitigation for AMD Zen5's version of TSA

* tag 'x86_bugs_tsa_zen5' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  x86/bugs: Mitigate TSA on AMD Zen5
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Pull x86 TSA fix from Borislav Petkov:

 - A mitigation for AMD Zen5's version of TSA

* tag 'x86_bugs_tsa_zen5' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  x86/bugs: Mitigate TSA on AMD Zen5
</pre>
</div>
</content>
</entry>
<entry>
<title>x86/CPU/AMD: Don't print reset reason in VMs</title>
<updated>2026-11-09T07:25:40+00:00</updated>
<author>
<name>Jason Andryuk</name>
<email>jason.andryuk@amd.com</email>
</author>
<published>2026-11-04T01:30:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=ea51d1a4c31fc8320c34f897dc5296a0bfc5c7ca'/>
<id>ea51d1a4c31fc8320c34f897dc5296a0bfc5c7ca</id>
<content type='text'>
print_s5_reset_status_mmio() expects to read FCH MMIO on baremetal.  VMs don't
have emulated FCH registers, so there is nothing to check.  Add an early exit
when running on a hypervisor.

The real motivation is Xen PV domUs can't boot on Zen CPUs.  PV domUs PTEs
contain system physical addresses - they don't have the concept of guest
physical addresses.  domUs can only map physical addresses they are assigned, so
a domU fails to map the FCH MMIO addresses.

However set_pte() does not return failure, so ioremap() returns a pointer while
the PTEs are unpopulated.  print_s5_reset_status_mmio() faults when reading
through the pointer, breaking the boot.

Limit the reset reason printing to baremetal only where it actually makes sense.

  [ bp: Massage commit message. ]

Fixes: ab8131028710 ("x86/CPU/AMD: Print the reason for the last reset")
Suggested-by: Borislav Petkov &lt;bp@alien8.de&gt;
Signed-off-by: Jason Andryuk &lt;jason.andryuk@amd.com&gt;
Signed-off-by: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;
Reviewed-by: Mario Limonciello (AMD) &lt;superm1@kernel.org&gt;
Reviewed-by: Yazen Ghannam &lt;yazen.ghannam@amd.com&gt;
Reviewed-by: Juergen Gross &lt;jgross@suse.com&gt;
Cc: stable@vger.kernel.org
Link: https://patch.msgid.link/20261104013026.185392-1-jason.andryuk@amd.com
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
print_s5_reset_status_mmio() expects to read FCH MMIO on baremetal.  VMs don't
have emulated FCH registers, so there is nothing to check.  Add an early exit
when running on a hypervisor.

The real motivation is Xen PV domUs can't boot on Zen CPUs.  PV domUs PTEs
contain system physical addresses - they don't have the concept of guest
physical addresses.  domUs can only map physical addresses they are assigned, so
a domU fails to map the FCH MMIO addresses.

However set_pte() does not return failure, so ioremap() returns a pointer while
the PTEs are unpopulated.  print_s5_reset_status_mmio() faults when reading
through the pointer, breaking the boot.

Limit the reset reason printing to baremetal only where it actually makes sense.

  [ bp: Massage commit message. ]

Fixes: ab8131028710 ("x86/CPU/AMD: Print the reason for the last reset")
Suggested-by: Borislav Petkov &lt;bp@alien8.de&gt;
Signed-off-by: Jason Andryuk &lt;jason.andryuk@amd.com&gt;
Signed-off-by: Borislav Petkov (AMD) &lt;bp@alien8.de&gt;
Reviewed-by: Mario Limonciello (AMD) &lt;superm1@kernel.org&gt;
Reviewed-by: Yazen Ghannam &lt;yazen.ghannam@amd.com&gt;
Reviewed-by: Juergen Gross &lt;jgross@suse.com&gt;
Cc: stable@vger.kernel.org
Link: https://patch.msgid.link/20261104013026.185392-1-jason.andryuk@amd.com
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'devm_kmalloc_obj-v7.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux</title>
<updated>2026-11-08T22:55:54+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-11-08T22:55:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=e0d8e8de8bcb1ef7b749033b5af5518ba8df7bec'/>
<id>e0d8e8de8bcb1ef7b749033b5af5518ba8df7bec</id>
<content type='text'>
Pull devm_kmalloc_obj conversion from Kees Cook:

 - treewide refresh of kmalloc_obj() conversions

 - devm_kmalloc_obj conversion rules added to Coccinelle scripting

 - treewide conversion of devm_kmalloc() family to devm_kmalloc_obj()

* tag 'devm_kmalloc_obj-v7.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux:
  treewide: Convert devm_kmalloc() family to the devm_kmalloc_obj() family
  coccinelle: kmalloc_obj: Include devm_kmalloc_obj conversion rules
  treewide: refresh kmalloc_obj() conversions
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Pull devm_kmalloc_obj conversion from Kees Cook:

 - treewide refresh of kmalloc_obj() conversions

 - devm_kmalloc_obj conversion rules added to Coccinelle scripting

 - treewide conversion of devm_kmalloc() family to devm_kmalloc_obj()

* tag 'devm_kmalloc_obj-v7.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux:
  treewide: Convert devm_kmalloc() family to the devm_kmalloc_obj() family
  coccinelle: kmalloc_obj: Include devm_kmalloc_obj conversion rules
  treewide: refresh kmalloc_obj() conversions
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'x86-urgent-2026-11-08' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip</title>
<updated>2026-11-08T18:29:22+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2026-11-08T18:29:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=11b6438b9e9f30e2eead2f232a58ef3f71a206be'/>
<id>11b6438b9e9f30e2eead2f232a58ef3f71a206be</id>
<content type='text'>
Pull x86 fixes from Ingo Molnar:

 - Select the BHI mitigation based on the attack vector properly
   (Breno Leitao)

 - Fix i386-gcov build bug in csum_ipv6_magic() due to overly
   strict asm constraints that cannot be met in that build mode
   (Rosen Penev)

 - Fix Vmware-guest i386 high-bandwidth hypercall arguments
   under UNWINDER_GUESS &amp; disabled frame-pointers (Zack Rusin)

 - Fix resctrl AMD ABMC counter ID field width (Babu Moger)

 - Fix restctrl pqos tool ABI breakage by reverting the
   mbm_assign_mode to default mode at boot (Babu Moger)

 - Initialize wall clock in get_rtc_noop() (Naman Jain)

 - Fix ptrace historic ABI quirk regression (Thomas Gleixner)

 - Add Drew Fustini as resctrl reviewer and Ben Horgan
   as fs/resctrl reviewer

 - Clear SEV RMPOPT when segmented RMP is disabled by firmware but
   is advertised as available (Ashish Kalra)

 - Set up SEV RMPOPT only on an active SNP host (Ashish Kalra)

 - Don't emit KCFI_REFERENCE() in modules (Ridge Lomont)

 - Ignore negative NMI handler durations (Breno Leitao)

 - Fix off-by-one error in boot-time sme_clear_pgd() (Thorsten Blum)

 - Fix ASID allocation bug (Chris Mason)

* tag 'x86-urgent-2026-11-08' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  x86/mm: Fix global ASID handed out to two processes
  x86/boot: Fix off-by-one error in sme_clear_pgd()
  MAINTAINERS: Add Ben Horgan as fs/resctrl reviewer
  x86/nmi: Ignore negative NMI handler durations
  x86/kcfi: Don't emit KCFI_REFERENCE() in modules
  x86/sev: Set up RMPOPT only on an active SNP host
  x86/sev: Clear RMPOPT when segmented RMP is disabled by firmware
  MAINTAINERS: resctrl: Add myself as reviewer
  x86/entry: Fix ptrace regression
  x86/init: Initialize wall clock in get_rtc_noop()
  x86,fs/resctrl: Keep mbm_assign_mode in default mode at boot
  x86/resctrl: Correct ABMC counter ID field width
  x86/vmware: Fix i386 high-bandwidth hypercall arguments
  x86/csum: Relax the len and proto constraints in 32-bit csum_ipv6_magic()
  x86/bugs: Select the BHI mitigation based on the attack vector properly
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Pull x86 fixes from Ingo Molnar:

 - Select the BHI mitigation based on the attack vector properly
   (Breno Leitao)

 - Fix i386-gcov build bug in csum_ipv6_magic() due to overly
   strict asm constraints that cannot be met in that build mode
   (Rosen Penev)

 - Fix Vmware-guest i386 high-bandwidth hypercall arguments
   under UNWINDER_GUESS &amp; disabled frame-pointers (Zack Rusin)

 - Fix resctrl AMD ABMC counter ID field width (Babu Moger)

 - Fix restctrl pqos tool ABI breakage by reverting the
   mbm_assign_mode to default mode at boot (Babu Moger)

 - Initialize wall clock in get_rtc_noop() (Naman Jain)

 - Fix ptrace historic ABI quirk regression (Thomas Gleixner)

 - Add Drew Fustini as resctrl reviewer and Ben Horgan
   as fs/resctrl reviewer

 - Clear SEV RMPOPT when segmented RMP is disabled by firmware but
   is advertised as available (Ashish Kalra)

 - Set up SEV RMPOPT only on an active SNP host (Ashish Kalra)

 - Don't emit KCFI_REFERENCE() in modules (Ridge Lomont)

 - Ignore negative NMI handler durations (Breno Leitao)

 - Fix off-by-one error in boot-time sme_clear_pgd() (Thorsten Blum)

 - Fix ASID allocation bug (Chris Mason)

* tag 'x86-urgent-2026-11-08' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  x86/mm: Fix global ASID handed out to two processes
  x86/boot: Fix off-by-one error in sme_clear_pgd()
  MAINTAINERS: Add Ben Horgan as fs/resctrl reviewer
  x86/nmi: Ignore negative NMI handler durations
  x86/kcfi: Don't emit KCFI_REFERENCE() in modules
  x86/sev: Set up RMPOPT only on an active SNP host
  x86/sev: Clear RMPOPT when segmented RMP is disabled by firmware
  MAINTAINERS: resctrl: Add myself as reviewer
  x86/entry: Fix ptrace regression
  x86/init: Initialize wall clock in get_rtc_noop()
  x86,fs/resctrl: Keep mbm_assign_mode in default mode at boot
  x86/resctrl: Correct ABMC counter ID field width
  x86/vmware: Fix i386 high-bandwidth hypercall arguments
  x86/csum: Relax the len and proto constraints in 32-bit csum_ipv6_magic()
  x86/bugs: Select the BHI mitigation based on the attack vector properly
</pre>
</div>
</content>
</entry>
</feed>
