linux-kernel - Add to stable: tracing: change CPU ring buffer state from tracing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1341243809.6578.5.camel@gandalf.stny.rr.com>
Date:	Mon, 02 Jul 2012 11:43:29 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	stable <stable@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Vaibhav Nagarnaik <vnagarnaik@...gle.com>
Subject: Add to stable: tracing: change CPU ring buffer state from
 tracing_cpumask

Hi Greg,

Thomas pointed out that the buffering for tracing (other than function
tracer - and other "tracers") is not affected by the tracing_cpumask.
This goes back to 3.0 (and probably before that).

It's fixed with this commit: 71babb2705e2203a64c27ede13ae3508a0d2c16c
"tracing: change CPU ring buffer state from tracing_cpumask"

Which looks to have made it into 3.5-rc1. Can you apply this to all the
stable trees from 3.0 and beyond.

Thanks,

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/