kernel-shark: Be more careful with kshark-su-record
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | kernel-shark: Execute kshark-record from same dir as kshark-su-recordkernel-shark/ | +2 | 4 replies | |
| 2/2 | kernel-shark: Set the DISPLAY environment for pkexec kshark-recordkernel-shark/ | +1 | 1 reply |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Yordan Karadzhov (VMware) |
|---|---|
| 1/2 | |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] kernel-shark: Be more careful with kshark-su-record
Two issues with kshark-su-record.
1) It just calls kshark-record with no path, which can be an issue if pkexec removes PATH variable, or sets it to something that kshark-record is not in.
2) Need to set DISPLAY variable, because on some of my machines, the kshark-record failed to execute due to pkexec removing the DISPLAY variable.
Steven Rostedt (VMware) (2):
kernel-shark: Execute kshark-record from same dir as kshark-su-record
kernel-shark: Set the DISPLAY environment for pkexec kshark-record
----
kernel-shark/bin/kshark-su-record | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)