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> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Oct 31 2001 - 21:00:45 EST