netdev - Re: Getting at the UDP headers from ->data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1831.1460409813@warthog.procyon.org.uk>
Date:	Mon, 11 Apr 2016 22:23:33 +0100
From:	David Howells <dhowells@...hat.com>
To:	Willem de Bruijn <willemdebruijn.kernel@...il.com>
Cc:	dhowells@...hat.com, Willem de Bruijn <willemb@...gle.com>,
	Network Development <netdev@...r.kernel.org>
Subject: Re: Getting at the UDP headers from ->data_ready()

Willem de Bruijn <willemdebruijn.kernel@...il.com> wrote:

> The network and transport header pointers are still valid. Commit e6afc8ace6dd
> only  changes where skb->data points to. It does not discard the data between
> skb->head and skb->data. This rxrpc follow-up patch fixes some offset
> arithmetic to the payload, which is computed relative to skb->data.
> 
> There are other uses of ip_hdr and udp_hdr in udp_recvmsg and similar
> recvmsg handlers for other protocols. For instance, in the source address
> processing for recvfrom ("if (sin) { .. }")

Excellent, thanks!

David