Bug 204941

Summary:	Reset CPU mask after setting it in trace-cmd record with option -M
Product:	Tools	Reporter:	Steven Rostedt (rostedt)
Component:	Trace-cmd/Kernelshark	Assignee:	Default virtual assignee for Trace-cmd and kernelshark (tools_tracecmd_kernelshark)
Status:	RESOLVED CODE_FIX
Severity:	normal	CC:	tz.stoyanov
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	N/A	Subsystem:
Regression:	No	Bisected commit-id:

Description Steven Rostedt 2019-09-21 18:09:37 UTC

I recorded a test case with:

 trace-cmd record -e all -M 4 ./userspin

And then ran

 trace-cmd record -e all ./userspin

and saw that the tracing CPU mask was still set with 4  when I wanted all CPUs.

The trace-cmd record should put back the original value after using -M for the tracing cpu masks.

Comment 1 Steven Rostedt 2019-09-21 18:10:40 UTC

 I'm currently traveling and may be slow to respond. I'll be back at my normal
 hours on Monday, September 30th.

-- Steve

Comment 2 Tzvetomir Stoyanov (VMware) 2019-09-25 11:10:40 UTC

Fixed by commit 
https://patchwork.kernel.org/patch/11160423/

Comment 3 Steven Rostedt 2019-09-25 11:11:45 UTC

 I'm currently traveling and may be slow to respond. I'll be back at my normal
 hours on Monday, September 30th.

-- Steve

Comment 4 Steven Rostedt 2020-01-31 20:02:39 UTC

Fixed by: 4d4db27bd911 ("trace-cmd: Reset CPU mask after setting it in trace-cmd record with option -M")