All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: "David S. Miller" <davem@davemloft.net>,
	Maillist netdev <netdev@oss.sgi.com>
Subject: Re: [PATCH PKT_SCHED 4/4]: fix CONFIG_NET_CLS_ACT skb leaks in	HFSC/CBQ
Date: Wed, 19 Jan 2005 14:33:46 +0100	[thread overview]
Message-ID: <41EE61BA.4030406@trash.net> (raw)
In-Reply-To: <1106141206.1047.937.camel@jzny.localdomain>

jamal wrote:

>I dont have time, but please double check that the following still
>applies:
>
>1) A qdisc receiving a STOLEN/QUEUED/SHOT signal from the classification
>result MUST free the packet and immediately stop processing that packet.
>The infrastructure code will clone packets if they want to steal or
>queue it.
>
It does now. Before there were things like "unsigned int len = skb->len"
after the call to tc_classify.

>2) Return code of qdisc from enqueue function need to be dealt with
>care. For example if the packet is localy generated and it is a TCP
>packet you could confuse the stack by telling it the packet was dropped
>because it will retransmit (and some things will happen with the window
>adjustments).
>
TC_ACT_SHOT => NET_XMIT_DROP
TC_ACT_STOLEN | TC_ACT_QUEUED => NET_XMIT_SUCCESS

>3) packets that are dropped because of a full Q should continue to
>return a XMIT_DROP (you want TCP for example to know about this)
>
They do.

  reply	other threads:[~2005-01-19 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19  4:38 [PATCH PKT_SCHED 4/4]: fix CONFIG_NET_CLS_ACT skb leaks in HFSC/CBQ Patrick McHardy
2005-01-19 13:26 ` jamal
2005-01-19 13:33   ` Patrick McHardy [this message]
2005-01-19 14:30     ` jamal

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=41EE61BA.4030406@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.