netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Salatiel Filho <salatiel.filho@gmail.com>,
	Jan Engelhardt <jengelh@medozas.de>, "Y. D." <duyuyang@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: IMQ bug: kernel reboot immediately
Date: Thu, 23 Apr 2009 14:13:59 +0200	[thread overview]
Message-ID: <49F05B87.5060903@trash.net> (raw)
In-Reply-To: <20090423121104.GC6809@ff.dom.local>

Jarek Poplawski wrote:
> On Thu, Apr 23, 2009 at 01:46:10PM +0200, Patrick McHardy wrote:
>> Jarek Poplawski wrote:
>>> On Thu, Apr 23, 2009 at 01:22:19PM +0200, Patrick McHardy wrote:
>>> ...
>>>> Currently not, the conntrack association is done at a later point.
>>>> We could add a classifier or TC action that performs the lookup
>>>> during ingress classification.
>>> BTW, some time ago I started to wonder how safe are those various
>>> ingress activities wrt. invalid packets, dropped later in ip_rcv().
>> Leaving aside the ipt action, I'm not aware of any problems caused
>> by ingress classification. Could you be more specific?
> 
> There is nothing specific yet. I hope these other classifiers and
> actions aren't mislead too much to go astray.

Generally, there shouldn't be any problems specific to ingress since
the classifiers have to expect all kinds of invalid packets on egress
as well.

  reply	other threads:[~2009-04-23 12:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 15:27 IMQ bug: kernel reboot immediately Y. D.
2009-04-23  8:43 ` Jarek Poplawski
2009-04-23 10:20   ` Patrick McHardy
2009-04-23 10:23     ` Jan Engelhardt
2009-04-23 10:28       ` Patrick McHardy
2009-04-23 11:12         ` Salatiel Filho
2009-04-23 11:22           ` Patrick McHardy
2009-04-23 11:40             ` Jarek Poplawski
2009-04-23 11:46               ` Patrick McHardy
2009-04-23 12:11                 ` Jarek Poplawski
2009-04-23 12:13                   ` Patrick McHardy [this message]
2009-04-23 12:37             ` Salatiel Filho
2009-04-23 12:41               ` Patrick McHardy
2009-04-23 23:32                 ` Salatiel Filho
2009-04-24 14:49                   ` Patrick McHardy
2009-04-24 14:55                     ` Denys Fedoryschenko
2009-04-24 15:14                       ` Salatiel Filho
2009-04-24 15:19                         ` Patrick McHardy
2009-04-24 15:23                           ` Salatiel Filho
2009-04-24 15:29                             ` Patrick McHardy
2009-04-23 12:29     ` Y. D.
2009-04-23 12:46       ` Jarek Poplawski
2009-05-02 12:03 ` pud

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=49F05B87.5060903@trash.net \
    --to=kaber@trash.net \
    --cc=duyuyang@gmail.com \
    --cc=jarkao2@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=salatiel.filho@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).