From: "David S. Miller" <davem@redhat.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: wensong@linux-vs.org, rusty@rustcorp.com.au, netdev@oss.sgi.com
Subject: Re: [2.6 PATCH] ipvs - avoid returning NF_DROP from the packet schedulers
Date: Wed, 8 Oct 2003 08:48:33 -0700 [thread overview]
Message-ID: <20031008084833.0efcc4e1.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0310081101170.5889-200000@u.domain.uli>
On Wed, 8 Oct 2003 11:09:20 +0300 (EEST)
Julian Anastasov <ja@ssi.bg> wrote:
> It seems my NF_DROP approach leads to new bugs. So, better
> free skb, return NF_STOLEN and add some comments. If someone
> wants to fix it in another way, go ahead.
Applied, thanks.
prev parent reply other threads:[~2003-10-08 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 8:09 [2.6 PATCH] ipvs - avoid returning NF_DROP from the packet schedulers Julian Anastasov
2003-10-08 15:48 ` David S. Miller [this message]
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=20031008084833.0efcc4e1.davem@redhat.com \
--to=davem@redhat.com \
--cc=ja@ssi.bg \
--cc=netdev@oss.sgi.com \
--cc=rusty@rustcorp.com.au \
--cc=wensong@linux-vs.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;
as well as URLs for NNTP newsgroup(s).