linux-kernel - Re: suspicious RCU usage (perf)

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130826182907.GB25202@redhat.com>
Date:	Mon, 26 Aug 2013 14:29:07 -0400
From:	Dave Jones <davej@...hat.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	paulmck@...ux.vnet.ibm.com,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: suspicious RCU usage (perf)

On Mon, Aug 26, 2013 at 02:18:14PM -0400, Steven Rostedt wrote:
 > On Mon, 26 Aug 2013 13:50:12 -0400
 > Dave Jones <davej@...hat.com> wrote:
 > > 
 > > This was triggered as a regular user fwiw.
 > > I had not been running perf, or any other tracing. It was just left
 > > fuzzing over the weekend with no interaction at all.
 > 
 > So you are telling me that ftrace was enabled by a regular user? If so,
 > that's a huge issue.
 
quite.

 > So my question to you. If you were not running perf or any other
 > tracing, and this is all just non-root user. How the hell did perf
 > function tracing get started on your box????

What mechanisms are available that would trigger it being enabled ?

Is there some path through sys_perf_open_event that might be
missing a capability check perhaps ?

	Dave

--
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/