From: Werner Almesberger <wa@almesberger.net>
To: chas williams <chas@locutus.cmf.nrl.navy.mil>
Cc: Mitchell Blank Jr <mitch@sfgoth.com>,
"David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [ATM] who 'owns' the skb created by drivers/atm?
Date: Sun, 23 Feb 2003 00:15:50 -0300 [thread overview]
Message-ID: <20030223001550.I2791@almesberger.net> (raw)
In-Reply-To: <200302211608.h1LG8tGi014271@locutus.cmf.nrl.navy.mil>; from chas@locutus.cmf.nrl.navy.mil on Fri, Feb 21, 2003 at 11:08:55AM -0500
chas williams wrote:
> In message <20030220222404.B11525@sfgoth.com>,Mitchell Blank Jr writes:
>>Hmmmm.. I guess we've just been getting lucky before in that case - we've
>>always just left the ATM_SKB() stuff in there.
The "cb must be in virgin state" rule is indeed news to me. But
maybe the rule has always been there, and nobody really noticed :-)
> this is one option. the other would be to clone the skb and pass the
> clone to the ip layer. the last option, and the one i prefer, would
> be to make the atm drivers not modify skb->cb (or reset it) when passing
> up the skb. the atm socket layer doesnt rely on it, and it would keep
> the 'extra' processing to a minimum.
I'm not sure this is the problem: as far as I remember, the ATM stack
doesn't assume that other layers leave skb->cb intact. In fact, it
shouldn't even touch an skb once it has been passed on.
BTW, I'm happy that ATM finally has a maintainer again. Thanks, Chas !
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2003-02-23 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 1:18 [ATM] who 'owns' the skb created by drivers/atm? chas williams
2003-02-21 1:42 ` James Morris
2003-02-21 6:22 ` David S. Miller
2003-02-21 6:12 ` Mitchell Blank Jr
2003-02-21 6:00 ` David S. Miller
2003-02-21 6:24 ` Mitchell Blank Jr
2003-02-21 16:08 ` chas williams
2003-02-23 3:15 ` Werner Almesberger [this message]
2003-02-24 1:55 ` chas williams
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=20030223001550.I2791@almesberger.net \
--to=wa@almesberger.net \
--cc=chas@locutus.cmf.nrl.navy.mil \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitch@sfgoth.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.