Patch "tracing: Fix clear of RECORDED_TGID flag when disabling trace event" has been added to the 4.13-stable tree

This is a note to let you know that I've just added the patch titled

tracing: Fix clear of RECORDED_TGID flag when disabling trace event

to the 4.13-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
tracing-fix-clear-of-recorded_tgid-flag-when-disabling-trace-event.patch
and it can be found in the queue-4.13 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

From: Chunyu Hu <[email protected]>
Date: Tue, 5 Sep 2017 13:36:46 +0800
Subject: tracing: Fix clear of RECORDED_TGID flag when disabling trace event

From: Chunyu Hu <[email protected]>

commit 7685ab6c58557c6234f3540260195ecbee7fc4b3 upstream.

When disabling one trace event, the RECORDED_TGID flag in the event file is not correctly cleared. It's clearing RECORDED_CMD flag when it should clear RECORDED_TGID flag.

---
 kernel/trace/trace_events.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

@@ -406,7 +406,7 @@ static int __ftrace_event_enable_disable
 
 			if (file->flags & EVENT_FILE_FL_RECORDED_TGID) {
 				tracing_stop_tgid_record();
-				clear_bit(EVENT_FILE_FL_RECORDED_CMD_BIT, &file->flags);
+				clear_bit(EVENT_FILE_FL_RECORDED_TGID_BIT, &file->flags);
 			}
 
 			call->class->reg(call, TRACE_REG_UNREGISTER, file);

Patches currently in stable-queue which might be from [email protected] are

queue-4.13/tracing-fix-clear-of-recorded_tgid-flag-when-disabling-trace-event.patch