Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp5085006ybl; Mon, 26 Aug 2019 22:23:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqxrtg76HVmHxN8OTA2IUxI3kz6AA3uKPMYicZiKK7g/C8QCjuMep3p2q2/WV5KvHt/C7AVw X-Received: by 2002:a65:6281:: with SMTP id f1mr18492960pgv.400.1566883435815; Mon, 26 Aug 2019 22:23:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566883435; cv=none; d=google.com; s=arc-20160816; b=YmHG+ipVZ+5baH/8qyYx3YbLZqUyTNrc64L7+ilpOtsXy6yiuUOJkZSjkaJj74GMY7 P0DlHi3ctTiF9CIzAaBx1v3vaGz5D7Hb3CC6Dv9jyG7PPfoXV9r1fNdcTEhL3fUVEQ0I egU1XX7Kou6nUuGTN1TzASOqe5GFoJtgqq1uZjjJm5YyVMTLmHrmC/eygIhkj5YRlpdC wowRwqV1Ddt7Wm2pHdmIBcQwEEanzPN2hs2bsgKHf/VOHZuv5T/d+yS0fOo5gyb+6GOq oWvyJ8nlfSN1XBIH5LXU92lsE3i+G1L/S/rhmnDxPFJUgkscaEvErpz5wfadSepcuU1E vIeA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=sC2NjC8+A0TKELBjbIVVNtKDnT9aRehN1CXf+Kpbi1M=; b=IzR6MzhGiOISsWA0mNYpsvWHC8qS+1zUGBSMrmCQaLbwUpjXydsBpmKSXx6LVs/doN wTDyrya9/QkLBsXfWy9N/Svobch8+fDPR0y1UBqFMqcMnK9l+PEjme368Ix+KLXLrTpp gm3pLIWr3g7qzBvhWTpXGx8ssBNQBXXflL+r33G1s4oj+BbmqcVAUsw16jl70mO6of+0 y88oZl+N3GgdsoyOQTmQcfLkqjMZUkKv37MQNNB5KTgqgBBpOkvJR2YhrBBBc+u4cM7M zkc3SYxtMUCCzLTWzUxxIIHlEZUhQ5nnrtLWZo4o63ZcecNQiu3r7xUxd+D8/N38zQma JRgw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=X4NiWjJi; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id az7si11643806plb.71.2019.08.26.22.23.24; Mon, 26 Aug 2019 22:23:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=X4NiWjJi; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726152AbfH0FXV (ORCPT + 99 others); Tue, 27 Aug 2019 01:23:21 -0400 Received: from mail-qk1-f193.google.com ([209.85.222.193]:44026 "EHLO mail-qk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725811AbfH0FXV (ORCPT ); Tue, 27 Aug 2019 01:23:21 -0400 Received: by mail-qk1-f193.google.com with SMTP id m2so16019195qkd.10 for ; Mon, 26 Aug 2019 22:23:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sC2NjC8+A0TKELBjbIVVNtKDnT9aRehN1CXf+Kpbi1M=; b=X4NiWjJimWS+yY7P9ODH4dTSXcADuJFv2Dzvp7EpZLt1KWavXUOtnEMzZafunw9qIk 5di4G0Sx5gZ6kgyKqos7Sfws36gBgXsVJTWxo/5TNgAYLJf3p8N3i1oBKl0m89QGBnEN RVpYGnp3cQwzaxHxYiJjQhTCbcVR1ACjqiB1s= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sC2NjC8+A0TKELBjbIVVNtKDnT9aRehN1CXf+Kpbi1M=; b=euteX5JPNW6dMKGmYG3V112I/S6WRy4xTeXsgIQNQNM095Azes1qBxnERaiPxWlLiF C7eE/VzI23O27H7e3RuidCcr50uVLtMtYiDCtFPwvJJh6l5lJuim61EE2RiuU8ZegT8b ipyGt4+FELOt7YZlvETUGQVP7Dahi0hUcoXJUzG7gbObJAsFQIG8zxTvzWBvbUzKPmUa WnQyYUR3zSohmYvfPhNIPPZKhyBdzfFFJ3by13mGVyLxUfaTetSnaV/BLx/UCHGjL5hK grM0nMFyejrqF9Isi5JVaOzoaPIF+WeHmTwgCgN+nrUUnzJcLVnCs9yREvUAaNFbKk/k mxMA== X-Gm-Message-State: APjAAAWvoucTLw99VAuXf48xM7tSssfTHvzO5zt5Nupp+hom6x9+XI6i ss0y2+UGPUsUl+QIXo6Z/4lOgRQQCfWEpYeD5THhoQ== X-Received: by 2002:ae9:f301:: with SMTP id p1mr20356780qkg.353.1566883399611; Mon, 26 Aug 2019 22:23:19 -0700 (PDT) MIME-Version: 1.0 References: <20190827003326.147452-1-drinkcat@chromium.org> <36878f3488f047978038c844daedd02f@aptaiexm02f.ap.qualcomm.com> In-Reply-To: <36878f3488f047978038c844daedd02f@aptaiexm02f.ap.qualcomm.com> From: Nicolas Boichat Date: Tue, 27 Aug 2019 13:23:08 +0800 Message-ID: Subject: Re: [PATCH, RFC] ath10k: Fix skb->len (properly) in ath10k_sdio_mbox_rx_packet To: Wen Gong Cc: "kvalo@codeaurora.org" , Alagu Sankar , "netdev@vger.kernel.org" , "briannorris@chromium.org" , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "ath10k@lists.infradead.org" , "wgong@codeaurora.org" , "niklas.cassel@linaro.org" , "tientzu@chromium.org" , "David S . Miller" Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Tue, Aug 27, 2019 at 11:34 AM Wen Gong wrote: > > > -----Original Message----- > > From: ath10k On Behalf Of Nicolas > > Boichat > > Sent: Tuesday, August 27, 2019 8:33 AM > > To: kvalo@codeaurora.org > > Cc: Alagu Sankar ; netdev@vger.kernel.org; > > briannorris@chromium.org; linux-wireless@vger.kernel.org; linux- > > kernel@vger.kernel.org; ath10k@lists.infradead.org; > > wgong@codeaurora.org; niklas.cassel@linaro.org; tientzu@chromium.org; > > David S . Miller > > Subject: [EXT] [PATCH, RFC] ath10k: Fix skb->len (properly) in > > ath10k_sdio_mbox_rx_packet > > > > (not a formal patch, take this as a bug report for now, I can clean > > up depending on the feedback I get here) > > > > There's at least 3 issues here, and the patch fixes 2/3 only, I'm not sure > > how/if 1 should be handled. > > 1. ath10k_sdio_mbox_rx_alloc allocating skb of a incorrect size (too > > small) > > 2. ath10k_sdio_mbox_rx_packet calling skb_put with that incorrect size. > > 3. ath10k_sdio_mbox_rx_process_packet attempts to fixup the size, but > > does not use proper skb_put commands to do so, so we end up with > > a mismatch between skb->head + skb->tail and skb->data + skb->len. > > > > Let's start with 3, this is quite serious as this and causes corruptions > > in the TCP stack, as the stack tries to coalesce packets, and relies on > > skb->tail being correct (that is, skb_tail_pointer must point to the > > first byte _after_ the data): one must never manipulate skb->len > > directly. > > > > Instead, we need to use skb_put to allocate more space (which updates > > skb->len and skb->tail). But it seems odd to do that in > > ath10k_sdio_mbox_rx_process_packet, so I move the code to > > ath10k_sdio_mbox_rx_packet (point 2 above). > > > > However, there is still something strange (point 1 above), why is > > ath10k_sdio_mbox_rx_alloc allocating packets of the incorrect > > (too small?) size? What happens if the packet is bigger than alloc_len? > > Does this lead to corruption/lost data? > > > > Fixes: 8530b4e7b22bc3b ("ath10k: sdio: set skb len for all rx packets") > > Signed-off-by: Nicolas Boichat > > > > --- > > > > One simple way to test this is this scriplet, that sends a lot of > > small packets over SSH: > > (for i in `seq 1 300`; do echo $i; sleep 0.1; done) | ssh $IP cat > > > > In my testing it rarely ever reach 300 without failure. > > > > drivers/net/wireless/ath/ath10k/sdio.c | 18 ++++++++++++------ > > 1 file changed, 12 insertions(+), 6 deletions(-) > > > > diff --git a/drivers/net/wireless/ath/ath10k/sdio.c > > b/drivers/net/wireless/ath/ath10k/sdio.c > > index 8ed4fbd8d6c3888..a9f5002863ee7bb 100644 > > --- a/drivers/net/wireless/ath/ath10k/sdio.c > > +++ b/drivers/net/wireless/ath/ath10k/sdio.c > > @@ -381,16 +381,14 @@ static int > > ath10k_sdio_mbox_rx_process_packet(struct ath10k *ar, > > struct ath10k_htc_hdr *htc_hdr = (struct ath10k_htc_hdr *)skb->data; > > bool trailer_present = htc_hdr->flags & > > ATH10K_HTC_FLAG_TRAILER_PRESENT; > > enum ath10k_htc_ep_id eid; > > - u16 payload_len; > > u8 *trailer; > > int ret; > > > > - payload_len = le16_to_cpu(htc_hdr->len); > > - skb->len = payload_len + sizeof(struct ath10k_htc_hdr); > > + /* TODO: Remove this? */ > If the pkt->act_len has set again in ath10k_sdio_mbox_rx_packet, seems not needed. Sure, will drop. > > + WARN_ON(skb->len != le16_to_cpu(htc_hdr->len) + sizeof(*htc_hdr)); > > > > if (trailer_present) { > > - trailer = skb->data + sizeof(*htc_hdr) + > > - payload_len - htc_hdr->trailer_len; > > + trailer = skb->data + skb->len - htc_hdr->trailer_len; > > > > eid = pipe_id_to_eid(htc_hdr->eid); > > > > @@ -637,8 +635,16 @@ static int ath10k_sdio_mbox_rx_packet(struct > > ath10k *ar, > > ret = ath10k_sdio_readsb(ar, ar_sdio->mbox_info.htc_addr, > > skb->data, pkt->alloc_len); > > pkt->status = ret; > > - if (!ret) > > + if (!ret) { > > + /* Update actual length. */ > > + /* FIXME: This looks quite wrong, why is pkt->act_len not > > + * correct in the first place? > > + */ > Firmware will do bundle for rx packet, and the aligned length by block size(256) of each packet's len is same > in a bundle. > > Eg. > packet 1 len: 300, aligned length:512 > packet 2 len: 400, aligned length:512 > packet 3 len: 200, aligned length:256 > packet 4 len: 100, aligned length:256 > packet 5 len: 700, aligned length:768 > packet 6 len: 600, aligned length:768 > > then packet 1,2 will in bundle 1, packet 3,4 in a bundle 2, packet 5,6 in a bundle 3. > > For bundle 1, packet 1,2 will both allocate with len 512, and act_len is 300 first, > then packet 2's len will be overwrite to 400. > > For bundle 2, packet 3,4 will both allocate with len 256, and act_len is 200 first, > then packet 4's len will be overwrite to 100. > > For bundle 3, packet 5,6 will both allocate with len 768, and act_len is 700 first, > then packet 6's len will be overwrite to 600. Ok thanks, I'll send a v2 with an improved description. > > + struct ath10k_htc_hdr *htc_hdr = > > + (struct ath10k_htc_hdr *)skb->data; > > + pkt->act_len = le16_to_cpu(htc_hdr->len) + sizeof(*htc_hdr); > > skb_put(skb, pkt->act_len); > > + } > > > > return ret; > > } > > -- > > 2.23.0.187.g17f5b7556c-goog > > > > > > _______________________________________________ > > ath10k mailing list > > ath10k@lists.infradead.org > > http://lists.infradead.org/mailman/listinfo/ath10k