diff options
| author | Alexander Shishkin <alexander.shishkin@linux.intel.com> | 2025-11-18 10:29:08 -0800 |
|---|---|---|
| committer | Dave Hansen <dave.hansen@linux.intel.com> | 2025-11-18 10:38:26 -0800 |
| commit | 42fea0a3a707249cf88ee24aece1dfaba4953b97 (patch) | |
| tree | 8f79e8fe61aba82a1c7b30d1a376b16729c1e587 /net/unix/af_unix.c | |
| parent | 731d43750cf8d3c67df7aabc78cc567c6d684111 (diff) | |
x86/traps: Communicate a LASS violation in #GP message
A LASS violation typically results in a #GP. With LASS active, any
invalid access to user memory (including the first page frame) would be
reported as a #GP, instead of a #PF.
Unfortunately, the #GP error messages provide limited information about
the cause of the fault. This could be confusing for kernel developers
and users who are accustomed to the friendly #PF messages.
To make the transition easier, enhance the #GP Oops message to include a
hint about LASS violations. Also, add a special hint for kernel NULL
pointer dereferences to match with the existing #PF message.
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Signed-off-by: Sohil Mehta <sohil.mehta@intel.com>
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com>
Link: https://patch.msgid.link/20251118182911.2983253-7-sohil.mehta%40intel.com
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions