linux-kernel - [PATCH 0/2] ftrace updates

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: <20080816014003.978160137@goodmis.org>
Date:	Fri, 15 Aug 2008 21:40:03 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	David Miller <davem@...emloft.net>
Subject: [PATCH 0/2] ftrace updates

Due to the new mcount recording method, the assumptions about the records
that hold the mcount locations have changed.  Now we need to protect
reading and writing of the records between module load and reading of the
debugfs files. There is not much contention here, but they need to be
protected none the less.

I simply use the ftrace_lock to accomplish this. The ftrace_lock should
never be held under interrupt context so disabling interrupts should
not be necessary. I've run this under lockdep and lockdep has not
complained.

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