All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Török Edwin" <edwin@gurde.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: netfilter-devel@lists.netfilter.org,
	fireflier-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, martinmaurer@gmx.at
Subject: Re: [PATCH 2.6.15.4 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets
Date: Sat, 18 Feb 2006 14:32:14 +0200	[thread overview]
Message-ID: <200602181432.14483.edwin@gurde.com> (raw)
In-Reply-To: <20060218122512.GG911@infradead.org>

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?


Thanks,
Edwin

  reply	other threads:[~2006-02-18 12:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18 12:10 [PATCH 2.6.15.4 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets Török Edwin
2006-02-18 12:25 ` Christoph Hellwig
2006-02-18 12:32   ` Török Edwin [this message]
2006-02-18 12:37     ` Christoph Hellwig
2006-02-18 12:47       ` Török Edwin
2006-02-18 13:10         ` Arjan van de Ven
2006-02-18 14:15           ` Török Edwin
2006-02-20 16:26 ` James Morris
2006-02-20 16:42   ` Patrick McHardy
2006-02-20 16:42     ` Patrick McHardy
2006-02-20 17:40   ` Török Edwin
2006-02-20 20:06     ` James Morris
  -- strict thread matches above, loose matches on Subject: below --
2006-02-18 12:20 Török Edwin
2006-02-18 19:28 ` Patrick McHardy
2006-02-18 20:03   ` Török Edwin
2006-02-18 20:07     ` Patrick McHardy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200602181432.14483.edwin@gurde.com \
    --to=edwin@gurde.com \
    --cc=fireflier-devel@lists.sourceforge.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martinmaurer@gmx.at \
    --cc=netfilter-devel@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.