mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Schulz <pschulz@foursticks.com.au>
To: linux-kernel@vger.kernel.org
Cc: pschulz@foursticks.com
Subject: Re: Linux sk_buff issues.
Date: Tue, 31 Jul 2001 15:13:03 +0930	[thread overview]
Message-ID: <E15RSJ5-0001mT-00@mars.foursticks.com.au> (raw)

Greetings,

In the 2.4.1 kernel..
While looking at the packet classifier code (net/sched/cls_u32.c) and other
ipv4 code that makes use of sk_buf, the following is observed:

-- There exist data structures in sk_buf for the mac layer (mac), net
	header (nh), and transport header (h).

-- These data structures contain explicit labels for the various header
	fields (depending on the protocol used) as well as a 'raw'
	field.

-- Most of the cls_u32 code and packet handling code uses the
	'raw' label in the data-structure.

Using kgdb, and tracing these datastructures, there are cases where the data
looks to be inconsistant. (for example, skb->nh.iph
points to one part of memory and skb->h.tcphdr points to a different part).
Also, the values seem to be different, eg., (struct udphdr *)((char
*)skb->nh.raw + 20)->source != skb->h.udp->source. I am assuming using
skb->nh.raw is the corrent version to use at this point. Is this correct and
are their any guidelines to be aware of?

Thanks,
Paul
--
                       Paul Schulz - Software Engineer
        Foursticks Pty Ltd - 2/259 Glen Osmond Road, Frewville, SA 5063
    Phone: +61 8 8338 5500   Fax: +61 8 8338 5511   Mobile: +61 401 981 301
       Email: pschulz@foursticks.com           Web: www.foursticks.com




             reply	other threads:[~2001-07-31  5:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31  5:43 Paul Schulz [this message]
2001-08-01 22:43 ` Alexey Kuznetsov

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=E15RSJ5-0001mT-00@mars.foursticks.com.au \
    --to=pschulz@foursticks.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pschulz@foursticks.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

all inboxes | Powered by JetHome®