From: "David S. Miller" <davem@redhat.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: wensong@linux-vs.org, netdev@oss.sgi.com
Subject: Re: [2.4/2.6 PATCHES] Change some ip_fragment checks to help IPVS
Date: Sat, 11 Oct 2003 11:53:57 -0700 [thread overview]
Message-ID: <20031011115357.0c756785.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0310111956070.31823-100000@u.domain.uli>
On Sat, 11 Oct 2003 20:18:33 +0300 (EEST)
Julian Anastasov <ja@ssi.bg> wrote:
> # [IPV4]: ip_copy_metadata must copy the nfcache field
I can't believe we missed this, I'll definitely apply
these patches.
Thanks.
> # [IPV4]: ip_fragment should not reassemble if all frags do not have owner
This one I have to think about some more.
next prev parent reply other threads:[~2003-10-11 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 17:18 [2.4/2.6 PATCHES] Change some ip_fragment checks to help IPVS Julian Anastasov
2003-10-11 18:07 ` David S. Miller
2003-10-11 18:08 ` David S. Miller
2003-10-11 18:53 ` David S. Miller [this message]
2003-10-11 19:02 ` David S. Miller
2003-10-14 12:03 ` kuznet
2003-10-14 22:55 ` Julian Anastasov
2003-10-14 22:51 ` David S. Miller
2003-10-15 7:01 ` Julian Anastasov
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=20031011115357.0c756785.davem@redhat.com \
--to=davem@redhat.com \
--cc=ja@ssi.bg \
--cc=netdev@oss.sgi.com \
--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).