[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87bpvme76p.fsf@basil.nowhere.org>
Date: Mon, 08 Dec 2008 21:35:42 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: Eric Lacombe <goretux@...il.com>,
Arjan van de Ven <arjan@...radead.org>,
Ingo Molnar <mingo@...e.hu>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
linux-kernel@...r.kernel.org
Subject: Re: [x86] do_arch_prctl
Jeremy Fitzhardinge <jeremy@...p.org> writes:
>>
>> The task_struct is also updated in sys_arch_prctl (ARCH_SET_FS and
>> ARCH_SET_GS), so not just on a context switch.
>> How the task structure could be out of date wrt thread.gs and thread.fs?
>> What could be a typical scenario that could induced gs or fs to be
>> modified and not thread.gs and thread.fs?
>>
>
> Not sure. It could just be redundant.
The process has just changed fs/gs, but not done a context switch yet.
-Andi
--
ak@...ux.intel.com
--
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/
Powered by blists - more mailing lists