From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, pabeni@redhat.com,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net] udp: on peeking bad csum, drop packets even if not at head
Date: Mon, 21 Aug 2017 17:39:12 -0400 [thread overview]
Message-ID: <20170821213912.93333-1-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
When peeking, if a bad csum is discovered, the skb is unlinked from
the queue with __sk_queue_drop_skb and the peek operation restarted.
__sk_queue_drop_skb only drops packets that match the queue head. With
sk_peek_off, the skb need not be at head, causing the call to fail and
the same skb to be found again on restart.
Walk the queue to find the correct skb. Limit the walk to sk_peek_off,
to bound cycle cost to at most twice the original skb_queue_walk in
__skb_try_recv_from_queue.
The operation may race with updates to sk_peek_off. As the operation
is retried, it will eventually succeed.
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
Simpler would be to check (skb->csum_complete_sw && !sbk->csum_valid)
in __skb_try_recv_from_queue to ignore skbs with bad checksum. But
__udp_lib_checksum_complete does not update those fields if called
while peeking, because the skb is shared. I found no way around that.
---
net/core/datagram.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/net/core/datagram.c b/net/core/datagram.c
index a21ca8dee5ea..5cf32b2372d3 100644
--- a/net/core/datagram.c
+++ b/net/core/datagram.c
@@ -360,9 +360,17 @@ int __sk_queue_drop_skb(struct sock *sk, struct sk_buff_head *sk_queue,
int err = 0;
if (flags & MSG_PEEK) {
+ struct sk_buff *lskb;
+ int off = sk_peek_offset(sk, flags);
+
err = -ENOENT;
spin_lock_bh(&sk_queue->lock);
- if (skb == skb_peek(sk_queue)) {
+ lskb = skb_peek(sk_queue);
+ while (lskb != skb && lskb && off >= lskb->len) {
+ off -= lskb->len;
+ lskb = skb_peek_next(lskb, sk_queue);
+ }
+ if (lskb == skb) {
__skb_unlink(skb, sk_queue);
refcount_dec(&skb->users);
if (destructor)
--
2.14.1.480.gb18f417b89-goog
next reply other threads:[~2017-08-21 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 21:39 Willem de Bruijn [this message]
2017-08-21 22:37 ` [PATCH net] udp: on peeking bad csum, drop packets even if not at head Willem de Bruijn
2017-08-21 22:40 ` Eric Dumazet
2017-08-22 0:12 ` Willem de Bruijn
2017-08-22 1:11 ` Willem de Bruijn
2017-08-22 16:39 ` [PATCH v2 " Eric Dumazet
2017-08-22 16:47 ` Paolo Abeni
2017-08-22 17:29 ` Willem de Bruijn
2017-08-22 21:28 ` 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=20170821213912.93333-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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;
as well as URLs for NNTP newsgroup(s).