From: jamal <hadi@cyberus.ca>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Patrick McHardy <kaber@trash.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] [NET_DOC] Document some simple rules for actions
Date: Tue, 16 Oct 2007 09:09:42 -0400 [thread overview]
Message-ID: <1192540182.4480.99.camel@localhost> (raw)
In-Reply-To: <20071016125134.GA11319@gondor.apana.org.au>
On Tue, 2007-16-10 at 20:51 +0800, Herbert Xu wrote:
> But I still think the distinction between skb_clone and
> skb_copy_header is wrong.
>
> When you munge a packet, it's still going to go back up
> the stack and be processed along the same path. Therefore
> you should be calling pskb_expand_head.
Dang, just noticed i said skb_expand() in the doc - is that the
issue? I will resend that one patch.
We do call pskb_expand_head() - example look at act_pedit.c
> In other words, this does not explain why skb_copy/pskb_copy
> and skb_copy_expand should differ from skb_clone. As far as
> I can see all these functions should behave in the same manner
> with respect to tc_verd
We need to avoid actions from infinetely looping (eg when they ask for
being reclassified) in a directed graph. That loop ttl count must be
reset to zero if we branch, because that is a new directed path. This is
always true and therefore that field must always be reset.
I have a feeling i am going on a tangent if that doesnt respond to your
comment above.
cheers,
jamal
next prev parent reply other threads:[~2007-10-16 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 12:33 [PATCH 3/3] [NET_DOC] Document some simple rules for actions jamal
2007-10-16 12:51 ` Herbert Xu
2007-10-16 13:09 ` jamal [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-21 19:22 jamal
2007-10-26 9:52 ` David Miller
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=1192540182.4480.99.camel@localhost \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).