lkml.org 
[lkml]   [2005]   [Apr]   [29]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
DateFri, 29 Apr 2005 12:12:16 +0400
FromKirill Korotaev <>
Subject[QUESTION] why redhat and others disable lcall7/lcall27?
All redhat kernels contain the patch given below which disables 
lcall7/lcall27. Why? I've heared from some people that these calls are
insecure or something like that. But what is the real problem with it?
Why mainstream kernel still keeps these calls then?

Kirill

diff -urNp linux-1130/arch/i386/kernel/traps.c
linux-10000/arch/i386/kernel/traps.c
--- linux-1130/arch/i386/kernel/traps.c
+++ linux-10000/arch/i386/kernel/traps.c
@@ -1021,9 +1021,10 @@ void __init trap_init(void)
* default LDT is a single-entry callgate to lcall7 for iBCS
* and a callgate to lcall27 for Solaris/x86 binaries
*/
+#if 0
set_call_gate(&default_ldt[0],lcall7);
set_call_gate(&default_ldt[4],lcall27);
-
+#endif
/*
* Should be a barrier for any external CPU state.
*/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-04-29 10:06    [from the cache]
©2003-2009