Mikado wrote: > Jan Engelhardt wrote: > >>>Is your code doing it like ipt_owner does? > > > It seems that ipt_owner does _not_ support PID match anymore: Yes, it was removed for two reasons: - it used tasklist_lock from bh-context, resulting in deadlocks - there is no 1:1 mapping between sockets (or packets) and processes. If you use corking even a single packet can be created in cooperation by multiple processes. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Which process is associated with process ID 0 (swapper)
- From: Jan Engelhardt <[email protected]>
- Re: Which process is associated with process ID 0 (swapper)
- From: Mikado <[email protected]>
- Re: Which process is associated with process ID 0 (swapper)
- References:
- Which process is associated with process ID 0 (swapper)
- From: Mikado <[email protected]>
- Re: Which process is associated with process ID 0 (swapper)
- From: "linux-os \(Dick Johnson\)" <[email protected]>
- Re: Which process is associated with process ID 0 (swapper)
- From: Mikado <[email protected]>
- Re: Which process is associated with process ID 0 (swapper)
- From: Jan Engelhardt <[email protected]>
- Re: Which process is associated with process ID 0 (swapper)
- From: Mikado <[email protected]>
- Which process is associated with process ID 0 (swapper)
- Prev by Date: Re: [(take 2)patch 6/7] Kprobes registers for notify page fault
- Next by Date: [PATCH] powerpc/pseries: avoid crash in PCI code if mem system not up.
- Previous by thread: Re: Which process is associated with process ID 0 (swapper)
- Next by thread: Re: Which process is associated with process ID 0 (swapper)
- Index(es):
 |