linux-kernel - Re: [PATCH/RFC 2/3] ftrace: introduce nohotpatch function attribute

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: <20150128053645.GA4633@osiris>
Date:	Wed, 28 Jan 2015 06:36:45 +0100
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Dominik Vogt <vogt@...ux.vnet.ibm.com>,
	Masami Hiramatsu <maasami.hiramatsu.pt@...achi.com>,
	Vojtech Pavlik <vojtech@...e.cz>,
	Jiri Kosina <jkosina@...e.cz>, Jiri Slaby <jslaby@...e.cz>,
	Andreas Krebbel <krebbel@...ux.vnet.ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH/RFC 2/3] ftrace: introduce nohotpatch function attribute

On Tue, Jan 27, 2015 at 09:42:28AM -0500, Steven Rostedt wrote:
> On Tue, 27 Jan 2015 07:19:42 +0100
> Dominik Vogt <vogt@...ux.vnet.ibm.com> wrote:
>  
> > While the kernel may use only profiling or hotpatch at the same
> > time, Gcc is able to generate both for the same function.
> 
> Understood, but would that be useful for the kernel?

Right now not. We may change that anyway in the future if needed.

Steven, how do we proceed with this small series?

Since there don't seem to be any objections, I'll repost with the
changed notrace define. However I think the whole stuff should go
upstream via the ftrace tree. Is that ok with you?

FWIW, the s390 gcc hotpatch feature was merged in the meantime:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=11762b8363737591bfb9c66093bc2edf289b917f

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