* current in OUTPUT
@ 2005-03-10 12:53 Juha Heljoranta
2005-03-10 13:13 ` Martin Josefsson
0 siblings, 1 reply; 2+ messages in thread
From: Juha Heljoranta @ 2005-03-10 12:53 UTC (permalink / raw)
To: netfilter-devel@lists.netfilter.org
'current' macro is not guaranteed to give a task that originated packet
when OUTPUT chain is been processed, right?
Regards,
Juha Heljoranta
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: current in OUTPUT
2005-03-10 12:53 current in OUTPUT Juha Heljoranta
@ 2005-03-10 13:13 ` Martin Josefsson
0 siblings, 0 replies; 2+ messages in thread
From: Martin Josefsson @ 2005-03-10 13:13 UTC (permalink / raw)
To: Juha Heljoranta; +Cc: netfilter-devel@lists.netfilter.org
On Thu, 10 Mar 2005, Juha Heljoranta wrote:
> 'current' macro is not guaranteed to give a task that originated packet
> when OUTPUT chain is been processed, right?
Right, there's some things that isn't sent from process context. Delayed
ACKs (timer context) and icmp replies (softirq context) are two examples.
/Martin
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-03-10 13:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-10 12:53 current in OUTPUT Juha Heljoranta
2005-03-10 13:13 ` Martin Josefsson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.