From: Andi Kleen <andi@firstfloor.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Eric Lacombe <goretux@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
Ingo Molnar <mingo@elte.hu>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [x86] do_arch_prctl
Date: Mon, 08 Dec 2008 21:35:42 +0100 [thread overview]
Message-ID: <87bpvme76p.fsf@basil.nowhere.org> (raw)
In-Reply-To: <493D7117.9050503@goop.org> (Jeremy Fitzhardinge's message of "Mon, 08 Dec 2008 11:10:15 -0800")
Jeremy Fitzhardinge <jeremy@goop.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@linux.intel.com
next prev parent reply other threads:[~2008-12-08 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 23:02 [x86] do_arch_prctl Eric Lacombe
2008-12-08 19:10 ` Jeremy Fitzhardinge
2008-12-08 20:35 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-18 17:35 [x86] do_arch_prctl - bug? Eric Lacombe
2008-11-19 9:23 ` Eric Lacombe
2008-11-19 21:06 ` Jeremy Fitzhardinge
2008-11-19 23:35 ` [x86] do_arch_prctl Eric Lacombe
2008-11-20 0:07 ` Jeremy Fitzhardinge
2008-11-20 0:22 ` Eric Lacombe
2008-11-24 12:24 ` Eric Lacombe
2008-11-24 18:22 ` Jeremy Fitzhardinge
2008-11-24 19:28 ` Eric Lacombe
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=87bpvme76p.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=goretux@gmail.com \
--cc=jeremy@goop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.