[PATCH] net: guard against coalescing packets from buggy network drivers
From: Svenning SÃrensen
Date: Fri Apr 25 2014 - 11:07:58 EST
This patch adds a guard against coalescing packets received by buggy network
drivers that don't initialize skb->tail properly.
Coalescing such packets will corrupt data in a way that makes it hard to
track down the real cause of the problem. Observed symptoms are a flood of
WARNs by tcp_recvmsg at random times, leaving no clear indication as to why
the packet buffers were corrupted. See for example this thread:
https://groups.google.com/forum/#!topic/linux.kernel/A8ZI9aXooSU
Obviously the correct thing to do is fixing the drivers in question (eg. by
using skb_put() instead of just setting skb->len) - this patch will
hopefully
help to track them down with less effort than I had to put into it :)
NB: in my case it was an out-of-tree Bluegiga WiFi driver; a quick look
indicates
that there are in-tree drivers (for hardware that I don't own) with the
same bug.
Signed-off-by: Svenning Soerensen <sss@xxxxxxxxxxx>
diff --git a/net/core/skbuff.c b/net/core/skbuff.c
index 1b62343..188a60a 100644
--- a/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -3833,6 +3833,19 @@ bool skb_try_coalesce(struct sk_buff *to, struct
sk_buff *from,
return false;
if (len <= skb_tailroom(to)) {
+ /* Guard against buggy network drivers that don't initialize
+ * skb properly: if they manipulate skb->len directly without
+ * setting skb->tail, the skb_put below may return a pointer to
+ * live data (such as TCP headers) that (without this guard)
+ * would get overwritten by coalescing.
+ * The correct thing to do is fixing the network drivers - but
+ * this guard should give us a chance to spot them before they
+ * cause real hard-to-debug problems :)
+ */
+ if (WARN_ONCE(skb_tail_pointer(to) < to->data,
+ "skb inconsistency: tail below data\n"))
+ return false;
+
BUG_ON(skb_copy_bits(from, 0, skb_put(to, len), len));
*delta_truesize = 0;
return true;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/