From: "Török Edwin" <edwin@gurde.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Christoph Hellwig <hch@infradead.org>,
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 16:15:30 +0200 [thread overview]
Message-ID: <200602181615.31004.edwin@gurde.com> (raw)
In-Reply-To: <1140268203.4698.7.camel@laptopd505.fenrus.org>
On Saturday 18 February 2006 15:10, Arjan van de Ven wrote:
> > As a last resort, I'll try to maintain this as separate patch to be
> > applied to the kernel, but that is something I'd really try to avoid,
> > because:
>
> the problem is this: The export is going away for a reason and not "just
> because".
I understand that, I didn't say there wasn't a reason for it going away.
> And that reason is that the implementation is going to be
> radically redone such that this isn't possible anymore. At all.
Could you tell me on which thread is this reimplementation being discussed?
I'd like to get a more clear picture of what exports I can use, and which
ones I can't.
Is the sk_sleep field of struct socket going to remain? If yes what am I
allowed to do with it inside ipt_owner.c?
Can you provide a function (in the new implementation) that at least gives me
a list of pids that are going to be woken up by data being received on a
socket? (for the moment it doesn't matter if that function will take some
time to complete its job, it's still going to be faster, than doing all this
from userspace). Then I could do the rest of the checking in userspace.
Or if that is not possible, could you tell me what kind of information am I
going to be able to obtain from the wait_queue_t of the socket?
> No amount of patching can fix that ;)
That is why I started this thread in the first place. I want to implement the
inode match in such a way that it will use only functions/structures it is
supposed to, (and not some functions/structures that are going away).
Could you please help me, and tell me _how_ I can implement this, _without_
doing something that won't be possible in the (near) future.
P.S.: This is my first attempt at modifying the kernel. If I ask something
that is obvious, just point me where the documentation for that is, or to the
thread where that has been already discussed.
Thanks,
Edwin
next prev parent reply other threads:[~2006-02-18 14:16 UTC|newest]
Thread overview: 15+ 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
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 [this message]
2006-02-20 16:26 ` James Morris
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=200602181615.31004.edwin@gurde.com \
--to=edwin@gurde.com \
--cc=arjan@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox