From: Jeff Garzik <jeff@garzik.org>
To: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
Cc: netdev@vger.kernel.org
Subject: Re: hard_start_xmit struct sk_buff read-only?
Date: Sat, 22 Dec 2007 03:50:02 -0500 [thread overview]
Message-ID: <476CCFBA.2010305@garzik.org> (raw)
In-Reply-To: <249190.1925.qm@web52006.mail.re2.yahoo.com>
Matti Linnanvuori wrote:
> An old article about Linux's network drivers mentioned
> that the struct sk_buff whose pointer is passed to a
> driver's hard_start_xmit function is read-only to the
> function. Is that still so? If it is, there is no
> mention about it in the kernel tree as far as I know.
This begs the question, what are you trying to do? ;-)
In terms of object lifetimes, control passes to the net driver when
->hard_start_xmit() is called, but that does not mean you can freely
scribble over things -- the skb may have been cloned, its destructor
callback still needs to be called (via dev_kfree_skb), etc.
Jeff
next prev parent reply other threads:[~2007-12-22 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 6:32 hard_start_xmit struct sk_buff read-only? Matti Linnanvuori
2007-12-22 8:50 ` Jeff Garzik [this message]
2007-12-22 9:18 ` Matti Linnanvuori
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=476CCFBA.2010305@garzik.org \
--to=jeff@garzik.org \
--cc=mattilinnanvuori@yahoo.com \
--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).