diff options
| author | Lai Jiangshan <[email protected]> | 2021-02-04 23:27:06 +0800 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2021-02-05 20:13:11 +0100 |
| commit | c4bed4b96918ff1d062ee81fdae4d207da4fa9b0 (patch) | |
| tree | c5fc2afad245c4b6f8116a139fbc3e5e2a8df1f5 /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | 25a068b8e9a4eb193d755d58efcb3c98928636e0 (diff) | |
x86/debug: Prevent data breakpoints on __per_cpu_offset
When FSGSBASE is enabled, paranoid_entry() fetches the per-CPU GSBASE value
via __per_cpu_offset or pcpu_unit_offsets.
When a data breakpoint is set on __per_cpu_offset[cpu] (read-write
operation), the specific CPU will be stuck in an infinite #DB loop.
RCU will try to send an NMI to the specific CPU, but it is not working
either since NMI also relies on paranoid_entry(). Which means it's
undebuggable.
Fixes: eaad981291ee3("x86/entry/64: Introduce the FIND_PERCPU_BASE macro")
Signed-off-by: Lai Jiangshan <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Cc: [email protected]
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions