[lkml]   [2006]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets
On Saturday 18 February 2006 14:25, Christoph Hellwig wrote:
> > - I need to lock the task_list
> > - task_list lock export might be gone some day?
> yes. in exactly half a year from now, and no new users are not allowed.
So I'll have to remove all code that relies on the task_list. Is
proc_check_exe_fown() the only function that is affected by this?
> > - is locking tasklist when inside a softirq allowed?
> no. for that reason we already removed a broken match from ipt_owner.
Is there an alternative for locking the tasklist, and iterating through all
the threads to: find out the struct task* given a struct fown_struct*. Or is
there any other way to find out the inode, and mountpoint of that process?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-02-18 13:35    [W:0.135 / U:1.928 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site