> 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 cases wouldn't it point at the "correct" process? Maybe I
> could tolerate those.
Anytime the upcall process had been blocked, or when NATing, or when
routing.
Have a look at the way that per-UID limites are implemented in ipfw...
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
