diff options
| author | Heiko Carstens <hca@linux.ibm.com> | 2026-01-27 12:16:52 +0100 |
|---|---|---|
| committer | Heiko Carstens <hca@linux.ibm.com> | 2026-01-27 12:16:52 +0100 |
| commit | 0875816a58d855d674305a7330c44d25ce27dca2 (patch) | |
| tree | e2ec8c062757effee4482a97e1550d3172b06771 /Documentation/features/debug/stackprotector | |
| parent | 88303fb68cc2e8b975f1505c84f215a934f6c2ad (diff) | |
| parent | 9f9d68c308cb63de67d35171925ce3875d076d4f (diff) | |
| download | linux-0875816a58d855d674305a7330c44d25ce27dca2.tar.gz linux-0875816a58d855d674305a7330c44d25ce27dca2.zip | |
Merge branch 'warn-exception'
Heiko Carstens says:
====================
v2:
- Use generic WARN() implementation in case of gcc-8, which avoids the need
to raise the minimum gcc version to gcc-9 for (only) s390
- Add couple of additional ifdef guards to avoid compile errors and
warnings
v1 ([1]):
Use the generic infrastructure introduced by Peter Zijlstra [2] to implement
an exception based WARN() and WARN_ONCE() similar to x86.
Due to some compiler oddities on s390 this requires to raise the minimum gcc
version to 9. Maybe there are ways to avoid this, but I failed to find a
working solution. Details are in the patch descriptions.
Just posting this now to also get some compile bot testing, since I'm afraid
there might be some compiler version / config option around where even this
new approach breaks.
Peter, since you were wondering: your generic infrastructure pieces work very
nice. Looking at the x86 and s390 implementation: it might be possible to make
things even more generic since both __WARN_printf(), and WARN_ONCE() are
identical; it looks like only __WARN_print_arg() needs to be provided.
[1] https://lore.kernel.org/all/20251209121701.1856271-1-hca@linux.ibm.com/
[2] https://lore.kernel.org/all/20251110114633.202485143@infradead.org/
====================
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'Documentation/features/debug/stackprotector')
0 files changed, 0 insertions, 0 deletions
