From: David Miller <davem@davemloft.net>
To: loke.chetan@gmail.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com, joe@perches.com,
bhutchings@solarflare.com, shemminger@vyatta.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next af-packet 1/2] Enhance af-packet to provide (near zero)lossless packet capture functionality.
Date: Fri, 01 Jul 2011 15:36:33 -0700 (PDT) [thread overview]
Message-ID: <20110701.153633.267893668051099806.davem@davemloft.net> (raw)
In-Reply-To: <1308708650-25509-2-git-send-email-loke.chetan@gmail.com>
From: Chetan Loke <loke.chetan@gmail.com>
Date: Tue, 21 Jun 2011 22:10:49 -0400
> +struct bd_v1 {
-
> + __u32 block_status;
> + __u32 num_pkts;
> + __u32 offset_to_first_pkt;
-
> + __u32 blk_len;
-
> + __u64 seq_num;
...
> + union {
> + struct {
> + __u32 words[4];
> + __u64 dword;
> + } __attribute__ ((__packed__));
> + struct bd_v1 bd1;
...
> +#define BLOCK_STATUS(x) ((x)->words[0])
> +#define BLOCK_NUM_PKTS(x) ((x)->words[1])
> +#define BLOCK_O2FP(x) ((x)->words[2])
> +#define BLOCK_LEN(x) ((x)->words[3])
> +#define BLOCK_SNUM(x) ((x)->dword)
This BLOCK_SNUM definition is buggy. It modifies the
first 64-bit word in the block descriptor.
But the sequence number lives 16 bytes into the descriptor.
This value is only written to once and never used by anything.
I would just remove it entirely.
Next, having this overlay thing is entirely pointless. Just refer to
the block descriptor members directly! You certainly wouldn't have
had this sequence number bug if you had done that.
next prev parent reply other threads:[~2011-07-01 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 2:10 [PATCH v2 net-next af-packet 0/2] " Chetan Loke
2011-06-22 2:10 ` [PATCH v2 net-next af-packet 1/2] " Chetan Loke
2011-07-01 22:36 ` David Miller [this message]
2011-07-05 14:53 ` chetan loke
2011-07-05 15:01 ` David Miller
2011-07-06 21:45 ` chetan loke
2011-07-07 7:13 ` David Miller
2011-07-07 13:04 ` chetan loke
2011-07-07 13:11 ` David Miller
2011-06-22 2:10 ` [PATCH v2 net-next af-packet 2/2] " Chetan Loke
2011-06-22 3:02 ` [PATCH v2 net-next af-packet 0/2] " chetan loke
2011-06-22 8:35 ` David Miller
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=20110701.153633.267893668051099806.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=eric.dumazet@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loke.chetan@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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®