> Mike Smith wrote:
> > > During a system call inside the kernel, can I safely assume that curproc
> > > points to the process that issued the call? For example, will looking at
> > > curproc in ip_output() tell me which process is responsible for generating
> > > the packet?
> >
> > No.
>
> Too
Mike Smith wrote:
> > During a system call inside the kernel, can I safely assume that curproc
> > points to the process that issued the call? For example, will looking at
> > curproc in ip_output() tell me which process is responsible for generating
> > the packet?
>
> No.
Too bad. In which cas
> Quick question:
>
> During a system call inside the kernel, can I safely assume that curproc
> points to the process that issued the call? For example, will looking at
> curproc in ip_output() tell me which process is responsible for generating
> the packet?
No.
--
... every activity meets w
Quick question:
During a system call inside the kernel, can I safely assume that curproc
points to the process that issued the call? For example, will looking at
curproc in ip_output() tell me which process is responsible for generating
the packet?
Thanks,
Lars
--
Lars Eggert <[EMAIL PROTECTED]
4 matches
Mail list logo