netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: djohnson+linux-kernel@sw.starentnetworks.com,
	greearb@candelatech.com, shemminger@linux-foundation.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	bguo@sw.starentnetworks.com
Subject: Re: expected behavior of PF_PACKET on NETIF_F_HW_VLAN_RX device?
Date: Thu, 01 Nov 2007 16:26:01 -0700	[thread overview]
Message-ID: <472A6089.7020104@hp.com> (raw)
In-Reply-To: <20071101.150723.30590053.davem@davemloft.net>

David Miller wrote:
> From: Rick Jones <rick.jones2@hp.com>
>>I'll try to go pester folks in tcpdump-workers then.
> 
> 
> The thing to check is "TP_STATUS_CSUMNOTREADY".
> 
> When using mmap(), it will be provided in the descriptor.  When using
> recvmsg() it will be provided via a PACKET_AUXDATA control message
> when enabled via the PACKET_AUXDATA socket option.

Figures... the "dailies" and "weeklies" for tar files of tcpdump and libpcap 
source are fubar... again.  I've email in to tcpdump-workers on that one.  If 
that isn't resolved quickly I'll learn how to access their CVS (pick an SCM, any 
SCM...)

I did an apt-get of debian lenny's tcpdump and sources:

hpcpc103:~# tcpdump -V
tcpdump version 3.9.8
libpcap version 0.9.8

and that seems to show the false checksum failure and not use the 
TP_STATUS_CSUMNOTREADY - at least that didn't appear in a grepping of the 
sources.  At first I thought it might be, but then I realized that my snaplen 
was too short to get the whole TSO'ed frame so tcpdump wasn't even trying to 
verify.  After disabling TSO on the NIC, leaving CKO on, and making my snaplen > 
1500 I could see it was doing undesirable stuff.

I'll see what top of trunk has at some point and what the folks there think of 
adding-in a change.

rick jones

  reply	other threads:[~2007-11-01 23:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 18:43 expected behavior of PF_PACKET on NETIF_F_HW_VLAN_RX device? Dave Johnson
2007-10-31 19:33 ` Stephen Hemminger
2007-11-01  1:06   ` Ben Greear
2007-11-01  1:10     ` David Miller
2007-11-01  1:23     ` Stephen Hemminger
2007-11-01  1:31       ` Ben Greear
2007-11-01  4:50       ` David Miller
2007-11-01 15:04         ` Ben Greear
2007-11-01 21:35           ` David Miller
2007-11-01 21:36           ` Dave Johnson
2007-11-01 21:48             ` Rick Jones
2007-11-01 21:59               ` David Miller
2007-11-01 22:04                 ` Rick Jones
2007-11-01 22:07                   ` David Miller
2007-11-01 23:26                     ` Rick Jones [this message]
2007-11-05 17:46                       ` [PATCH 1/2] NET: Re-add VLAN tag for devices incapable of keeping it Dave Johnson
2007-11-05 18:00                         ` Patrick McHardy
2007-11-05 23:15                           ` David Miller
2007-11-06  0:21                             ` Patrick McHardy
2007-11-06  0:35                               ` David Miller
2007-11-06 18:03                               ` Krzysztof Halasa
2007-11-06 18:56                                 ` Ben Greear
2007-11-06 20:08                                   ` Krzysztof Halasa
2007-11-06 23:55                                 ` Patrick McHardy
2007-11-05 17:47                       ` [PATCH 2/2] " Dave Johnson
2007-11-06  2:39                         ` Ramkrishna Vepa
2007-11-06 18:28                           ` Ramkrishna Vepa
2007-11-06 18:34                             ` Dave Johnson
2007-11-01 21:58             ` expected behavior of PF_PACKET on NETIF_F_HW_VLAN_RX device? David Miller
2007-11-02 18:08             ` Dave Johnson
2007-11-02 21:20               ` David Miller
2007-11-02 21:52               ` Michael Chan

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=472A6089.7020104@hp.com \
    --to=rick.jones2@hp.com \
    --cc=bguo@sw.starentnetworks.com \
    --cc=davem@davemloft.net \
    --cc=djohnson+linux-kernel@sw.starentnetworks.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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).