From: David Howells <dhowells@redhat.com>
To: willemb@google.com
Cc: dhowells@redhat.com, netdev@vger.kernel.org
Subject: Getting at the UDP headers from ->data_ready()
Date: Mon, 11 Apr 2016 22:04:09 +0100 [thread overview]
Message-ID: <19466.1460408649@warthog.procyon.org.uk> (raw)
Hi Willem,
With regards to:
commit 4d0fc73ebe94ac984a187f21fbf4f3a1ac846f5a
Author: Willem de Bruijn <willemb@google.com>
Date: Thu Apr 7 11:44:59 2016 -0400
rxrpc: do not pull udp headers on receive
Commit e6afc8ace6dd modified the udp receive path by pulling the udp
header before queuing an skbuff onto the receive queue.
Does that mean that I can no longer access the UDP header via udp_hdr(skb)
from with the ->data_ready() handler?
I'm guessing that's not actually the case since ip_hdr(skb) seems to work - or
is that something I shouldn't be using since the part of the buffer containing
the IP header might've been discarded?
David
next reply other threads:[~2016-04-11 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 21:04 David Howells [this message]
2016-04-11 21:18 ` Getting at the UDP headers from ->data_ready() Willem de Bruijn
2016-04-11 21:23 ` David Howells
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=19466.1460408649@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox