SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093487.html
** Description changed:
- Description: uprobes: fix SIGSEGVs with setjmp/longjmp
+ == SRU Justification ==
+ This commit fixes SIGSEGVs with setjmp/longjmp.
Symptom:
Setting a user space return probe on a function that does not
return because of a longjmp call may cause SIGSEGV or SIGILL.
- Problem:
+ Problem:
Userspace can do whatever it wants with its stack. Especially
stack modifications performed with longjmp cannot be handled 100%
correctly within the uprobes kernel part, which may lead to user
space observed crashed.
- Solution:
+ Solution:
Implement arch_uretprobe_is_alive() which improves the situation
a lot and works for many situations.
+ This commit has also been cc'd to upstream stable, but it has not landed
+ in Bionic as of yet.
+
+ == Fix ==
+ 783c3b53b950 ("s390/uprobes: implement arch_uretprobe_is_alive()")
+
+ == Regression Potential ==
+ Low. Limited to s390. The commit has also been cc'd to upstream
+ stable, so it has had additional upstream review.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
Upstream-ID: 783c3b53b9506db3e05daacfe34e0287eebb09d8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777840
Title:
uprobes: fix SIGSEGVs with setjmp/longjmp
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777840/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
