* current->addr_limit
@ 2001-10-31 13:31 DINH Viet Hoa
2001-10-31 19:06 ` current->addr_limit H. Peter Anvin
0 siblings, 1 reply; 2+ messages in thread
From: DINH Viet Hoa @ 2001-10-31 13:31 UTC (permalink / raw)
To: linux-kernel
When changing current->addr_limit through the macros
get_fs() and set_fs() in the kernel or in a kernel thread,
do we need to lock anything to prevent anything else
from accessing our custom value of current->addr_limit ?
thanks.
--
DINH Viêt Hoà, ingénieur associé, projet PARIS
IRISA-INRIA, Campus de Beaulieu, 35042 Rennes cedex, France
Tél: +33 (0) 2 99 84 75 98, Fax: +33 (0) 2 99 84 25 28
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: current->addr_limit
2001-10-31 13:31 current->addr_limit DINH Viet Hoa
@ 2001-10-31 19:06 ` H. Peter Anvin
0 siblings, 0 replies; 2+ messages in thread
From: H. Peter Anvin @ 2001-10-31 19:06 UTC (permalink / raw)
To: linux-kernel
Followup to: <20011031143159.0bdc0981.vdinh@irisa.fr>
By author: DINH Viet Hoa <Viet-Hoa.Dinh@irisa.fr>
In newsgroup: linux.dev.kernel
>
> When changing current->addr_limit through the macros
> get_fs() and set_fs() in the kernel or in a kernel thread,
> do we need to lock anything to prevent anything else
> from accessing our custom value of current->addr_limit ?
>
No, the currently running process owns "current".
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-10-31 19:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-10-31 13:31 current->addr_limit DINH Viet Hoa
2001-10-31 19:06 ` current->addr_limit H. Peter Anvin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox