X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=Documentation%2Fadmin-guide%2Fhw-vuln%2Fsrso.rst;h=f79cb11b080f67733c4a4d08699a991f95aeb015;hb=e6b40d2cb5aae35cc3659f9b74c999a01120ad30;hp=2f923c805802ffc7a0a2915749274af1be9af9bd;hpb=54dde78a50a8eb0d6a293c8416fcf6365d189af3;p=platform%2Fkernel%2Flinux-starfive.git

diff --git a/Documentation/admin-guide/hw-vuln/srso.rst b/Documentation/admin-guide/hw-vuln/srso.rst
index 2f923c8..f79cb11 100644
--- a/Documentation/admin-guide/hw-vuln/srso.rst
+++ b/Documentation/admin-guide/hw-vuln/srso.rst
@@ -124,8 +124,8 @@ sequence.
 To ensure the safety of this mitigation, the kernel must ensure that the
 safe return sequence is itself free from attacker interference.  In Zen3
 and Zen4, this is accomplished by creating a BTB alias between the
-untraining function srso_untrain_ret_alias() and the safe return
-function srso_safe_ret_alias() which results in evicting a potentially
+untraining function srso_alias_untrain_ret() and the safe return
+function srso_alias_safe_ret() which results in evicting a potentially
 poisoned BTB entry and using that safe one for all function returns.
 
 In older Zen1 and Zen2, this is accomplished using a reinterpretation