linux-kernel - Some confusion about the period of updating new function in

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: <20151211105242.GA2826@dhcp-129-201.nay.redhat.com>
Date:	Fri, 11 Dec 2015 18:52:42 +0800
From:	Minfei Huang <mnfhuang@...il.com>
To:	rostedt@...dmis.org
Cc:	mhuang@...hat.com, linux-kernel@...r.kernel.org
Subject: Some confusion about the period of updating new function in

ftrace
Reply-To: 

Hi, Steven.

There is a confusion which blocks my step to go further for ftrace.

Does ftrace guarantee that the replaced function is finished while
ftrace is replacing the functions? In the other word, is there a
possible that new function starts to run, while old function is also
running (maybe this function is called before replacing the function).

Function schedule_on_each_cpu maybe fails to excute, if there is no
enough memory to be allocated? Then kernel may be unstable, if ftrace
continues, without handling the error, does it?

Previously, I posted a patch to fix this issue, and you nacked it.

[PATCH] workqueue: Add the allocation flags to function
schedule_on_each_cpu_gfp

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