From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] update: _working_ code to add device+inode check to ipt_owner.c
Date: Thu, 9 Sep 2004 22:38:13 +0100 [thread overview]
Message-ID: <20040909213813.GC10892@lkcl.net> (raw)
In-Reply-To: <20040909181034.GF10046@lkcl.net>
On Thu, Sep 09, 2004 at 07:10:34PM +0100, Luke Kenneth Casson Leighton wrote:
> On Thu, Sep 09, 2004 at 09:19:31AM -0700, Chris Wright wrote:
> > * Luke Kenneth Casson Leighton (lkcl@lkcl.net) wrote:
> > > wow, gosh, it works.
> > >
> > > okay, this is a patch to add support in iptables for per-program
> > > firewall filtering.
> > >
> > > also included is the patches to iptables-1.2.11.
> > >
> > > i have confidence that this patch will provide support for
> > > BOTH incoming AND outgoing per-program packet filtering.
> >
> > Programs can share a socket. Incoming is in interrupt context. You
> > have no idea who will be woken up. How do you handle this?
>
> chris, hi,
chris - for example, i notice that at the top of ipt_owner.c it says
"deals with local outgoing sockets".
so... does sk_buff _only_ contain a list of outgoing sockets?
iiiisss... there a different socket for incoming traffic that
someone is different from the list of sockets associated with
a task?
is the clue in what you say about "Incoming is in interrupt context"?
are the sockets in the interrupt context somehow different / special
such that they would never get to this code?
gloop, gloop, i'm drowning in lack of knowledge, here.
l.
next prev parent reply other threads:[~2004-09-09 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 16:22 [patch] update: _working_ code to add device+inode check to ipt_owner.c Luke Kenneth Casson Leighton
2004-09-09 16:19 ` Chris Wright
2004-09-09 18:10 ` Luke Kenneth Casson Leighton
2004-09-09 18:48 ` Chris Wright
2004-09-09 21:25 ` Luke Kenneth Casson Leighton
2004-09-09 23:04 ` Chris Wright
2004-09-10 0:08 ` Luke Kenneth Casson Leighton
2004-09-10 0:21 ` Chris Wright
2004-09-10 0:59 ` Luke Kenneth Casson Leighton
2004-09-10 1:08 ` Chris Wright
2004-09-10 1:34 ` Luke Kenneth Casson Leighton
2004-09-09 21:38 ` Luke Kenneth Casson Leighton [this message]
2004-09-09 23:41 ` Chris Wright
2004-09-10 0:10 ` Luke Kenneth Casson Leighton
2004-09-09 16:29 ` Stephen Smalley
2004-09-09 16:33 ` Stephen Smalley
2004-09-09 17:44 ` Luke Kenneth Casson Leighton
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=20040909213813.GC10892@lkcl.net \
--to=lkcl@lkcl.net \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.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