From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: "Wei Yongjun" <yjwei@nanjing-fnst.com>
Cc: netdev@vger.kernel.org, "David Miller" <davem@davemloft.net>
Subject: Re: [PATCH] SNMPv2 udpInDatagrams counter error
Date: Mon, 31 Jul 2006 09:57:50 +0100 [thread overview]
Message-ID: <200607310957.50332@strip-the-willow> (raw)
In-Reply-To: <075801c6b47d$08c49350$6004a8c0@WeiYongjun>
Hi,
| if (!sk->sk_filter && skb->ip_summed != CHECKSUM_UNNECESSARY) {
|
| IPv6 doesn't do this, so I think delete condition 'sk->sk_filter' is better.
| Do you think so?
I think the sk->sk_filter is there for a good reason. If you delete it, that routine
is forced to always compute UDP checksums, even if the only receiving application is
a tcpdump process. I may be wrong here, but I think that deleting the sk_filter statement
is not at a good idea.
The other alternatives discussed (afaik) so far were:
1) Move the increment of UDP_MIB_INDATAGRAMS from udp_queue_rcv_skb() to udp_recvmsg()
(first patch uploaded to http://bugzilla.kernel.org/show_bug.cgi?id=6660). This
was discussed: not a good idea, since in-kernel applications may use the data_ready
handler rather than udp_recvmsg().
2) Decrement UDP_MIB_INDATAGRAMS in udp_recvmsg() when the checksum turns out to be
wrong (second patch uploaded to above address). This would be a fix to the problem
you are stating, it also solves the problem of missing out the data_ready handlers in
(1), and was suggested earlier on this mailing list.
-- Gerrit
next prev parent reply other threads:[~2006-07-31 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 8:51 [PATCH] SNMPv2 udpInDatagrams counter error Wei Yongjun
2006-07-31 8:19 ` Gerrit Renker
[not found] ` <075801c6b47d$08c49350$6004a8c0@WeiYongjun>
2006-07-31 8:57 ` Gerrit Renker [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-31 10:03 Wei Yongjun
2006-07-31 10:42 ` Herbert Xu
2006-07-31 11:21 Wei Yongjun
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=200607310957.50332@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yjwei@nanjing-fnst.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.