* Why current->uid is not working in 2.6.29 ?
@ 2009-05-23 4:22 Kunsheng Chen
2009-05-23 9:17 ` Ozan Çağlayan
0 siblings, 1 reply; 2+ messages in thread
From: Kunsheng Chen @ 2009-05-23 4:22 UTC (permalink / raw)
To: linux-kernel
Hello everyone,
I am new to kernel module programming and got some problem while compiling some old kernel code.
The
code is trying to get user id using current->uid, but it is not
working by reminding me 'task_struct; doesn't contain field uid '.
I checked the linux source code , uid is not there any more.
The 'current' is of task_struct, so could anyone tell me where is the new place for that uid ?
Thanks in advance,
-Kun
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Why current->uid is not working in 2.6.29 ?
2009-05-23 4:22 Why current->uid is not working in 2.6.29 ? Kunsheng Chen
@ 2009-05-23 9:17 ` Ozan Çağlayan
0 siblings, 0 replies; 2+ messages in thread
From: Ozan Çağlayan @ 2009-05-23 9:17 UTC (permalink / raw)
To: Kunsheng Chen; +Cc: linux-kernel
Kunsheng Chen wrote:
> Hello everyone,
>
> I am new to kernel module programming and got some problem while compiling some old kernel code.
>
> The
> code is trying to get user id using current->uid, but it is not
> working by reminding me 'task_struct; doesn't contain field uid '.
>
> I checked the linux source code , uid is not there any more.
>
They were replaced by some other calls. For example the following is a
snippet which ports the old code to the new API:
- address, current->uid);
+ address, current_uid());
The commit 1330deb0f6e89525c8e9fcbd6b13522c9243bfc0 is a good example of
what are the new replacements.
This is all that I know,
Ozan Caglayan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-05-23 9:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-23 4:22 Why current->uid is not working in 2.6.29 ? Kunsheng Chen
2009-05-23 9:17 ` Ozan Çağlayan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox