Wierd Problem with Current Task Struct

[Tom Handal]

Greetings

     I am currently having a problem with the "current" task struct in the
2.4.18-4GB SUSE80 Kernel ... I am writing a kernel module that is calling
down through a system call... The system call is getting the PID and FS
pointer from the Current task struct, but the FS pointer is NULL and the PID
is 0 .... Is this normal? Should current->fs ever be NULL? I haven't noticed
anyone checking it in the Linux Kernel, so I think it is assumed to always
be a good value... Can anyone shed light on this?

Thanks in advance....
Tom

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/