From: Eric Lacombe <goretux@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: [x86] do_arch_prctl - bug?
Date: Tue, 18 Nov 2008 15:33:32 +0100 [thread overview]
Message-ID: <200811181533.33108.goretux@gmail.com> (raw)
Hello,
I would like to know why the ARCH_SET_GS action of sys_arch_prctl, write the
MSR MSR_KERNEL_GS_BASE and not the MSR MSR_GS_BASE when the variable "doit"
equals 1? Is that a bug?
In other words, why the following code :
...
if (doit) {
load_gs_index(0);
ret = checking_wrmsrl(MSR_KERNEL_GS_BASE, addr)
}
...
is not the following one :
...
if (doit) {
ret = checking_wrmsrl(MSR_GS_BASE, addr)
load_gs_index(0);
}
...
I copy for clarity the beginning of the function "do_arch_prctl" :
long do_arch_prctl(struct task_struct *task, int code, unsigned long addr)
{
int ret = 0;
int doit = task == current;
int cpu;
switch (code) {
case ARCH_SET_GS:
if (addr >= TASK_SIZE_OF(task))
return -EPERM;
cpu = get_cpu();
/* handle small bases via the GDT because that's faster to
switch. */
if (addr <= 0xffffffff) {
set_32bit_tls(task, GS_TLS, addr);
if (doit) {
load_TLS(&task->thread, cpu);
load_gs_index(GS_TLS_SEL);
}
task->thread.gsindex = GS_TLS_SEL;
task->thread.gs = 0;
} else {
task->thread.gsindex = 0;
task->thread.gs = addr;
if (doit) {
load_gs_index(0);
ret = checking_wrmsrl(MSR_KERNEL_GS_BASE, addr);
}
}
put_cpu();
break;
[...]
Regards,
Eric
next reply other threads:[~2008-11-18 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 14:33 Eric Lacombe [this message]
2008-11-18 14:45 ` [x86] do_arch_prctl - bug? Arjan van de Ven
[not found] ` <200811181820.04064.goretux@gmail.com>
2008-11-18 17:35 ` Eric Lacombe
-- strict thread matches above, loose matches on Subject: below --
2008-11-18 17:35 Eric Lacombe
2008-11-18 23:44 ` Eric Lacombe
2008-11-19 1:07 ` Jeremy Fitzhardinge
2008-11-19 9:23 ` Eric Lacombe
2008-11-19 21:06 ` Jeremy Fitzhardinge
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=200811181533.33108.goretux@gmail.com \
--to=goretux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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