From: Kirill Korotaev <dev@sw.ru>
To: linux-kernel@vger.kernel.org
Subject: [QUESTION] why redhat and others disable lcall7/lcall27?
Date: Fri, 29 Apr 2005 12:12:16 +0400 [thread overview]
Message-ID: <4271EC60.6020809@sw.ru> (raw)
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.
*/
reply other threads:[~2005-04-29 8:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4271EC60.6020809@sw.ru \
--to=dev@sw.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox