Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp7729464ybi; Tue, 9 Jul 2019 03:25:03 -0700 (PDT) X-Google-Smtp-Source: APXvYqzxDDg7WxxBsOz+8FjcSovlt72rCC4YJzXzrcLm3oqPveb62mVB1hYu7crHPxIgQqnw7bhT X-Received: by 2002:a65:6656:: with SMTP id z22mr1726195pgv.197.1562667902803; Tue, 09 Jul 2019 03:25:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562667902; cv=none; d=google.com; s=arc-20160816; b=FANHFfsbadmtsn45DZzI1Wt9QikBvFCqifJB9rFn8svjPgD0IFXWHbJMGmKmvebX2A gyX2Bxn5U7QPCwvW++4frnNwr6jaEVT8Rua2d5Qu07r/N5Z3cA0+X9rXACLB8KgDdq3i 7CZXU9kZUJqGzWSYfgmM//rLX4oGnxVSlk+1/Zt0TX4Y4dR2E1v1Xzjo5iCUQoQvIiDQ UsUekCPPokODt4jrvNraoKEvm87kCOaj8TL4JgQrqMEFI4mTicP+YjA2i+7kxM0734HA OAxHS53YvNbZzAz3ZPAqVt83uSrMUc4VrxLOxqeCOJ+p26++BdMepDePYMDwSGMX8Jxf nFQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=LHn7sh6ZYwvh5+D/h2PrSTgVx9fde1Yu4h3Dr05pCsY=; b=FEtKebbs5CiJ4JHxX3RWoA2LiT4oqqgBTpcxKWWHlmoJKhu3G2UKFU0maepF8qxK+q rkPa2HcI6Zzhi+i4V9qENbgyAKkSNYbZto0uh4SOIhV7ql/8AP8aCe2B/1fTYPc16PrT sGp+J9/lmDIiSRqNbIU1KSU+BIQz/v6TrPtEnEpG3AslMiRe8QcBJ6Clq+BLFbF28hKW KjEK6YakroJgBNvWlGPfi7OjivquzSrrEw8ip3TnoufL1Kx5iWF0vb920SiGgUrO9LhH mt/zR/OHL/APqaBVRhSrUkvNCWyTRl8eNYhjKG0VHy+WOBzvRhWvqnVxlUPECeUVurjy UiGw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@endlessm-com.20150623.gappssmtp.com header.s=20150623 header.b=S6x8jcHv; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q133si21231110pgq.410.2019.07.09.03.24.48; Tue, 09 Jul 2019 03:25:02 -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=@endlessm-com.20150623.gappssmtp.com header.s=20150623 header.b=S6x8jcHv; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726324AbfGIKWG (ORCPT + 99 others); Tue, 9 Jul 2019 06:22:06 -0400 Received: from mail-pg1-f193.google.com ([209.85.215.193]:46586 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725989AbfGIKWF (ORCPT ); Tue, 9 Jul 2019 06:22:05 -0400 Received: by mail-pg1-f193.google.com with SMTP id i8so9190643pgm.13 for ; Tue, 09 Jul 2019 03:22:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=endlessm-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=LHn7sh6ZYwvh5+D/h2PrSTgVx9fde1Yu4h3Dr05pCsY=; b=S6x8jcHvKJGfpw+Yld/kbXFq1TShqWb7H9Z+ZjTW7WXiQJY0xIFNau7xT+ZDdNqeNe 07H063fJx/xr2fqRFg+7gKq6ZfH9r1EzHTVrgJYwTZnQ79yv+mWP9P6vK2Dso8w9j+Fv nP3mNJa/v/zaokDhy4yTfby3sgmKvu0R4hb0tMTPB8iG678pMO1ypho2UPvDZM4aPtac YXZntBd9k5dQwwmnjHbpIFGowGjkhYiS8pzutGE9v6WXFeBwteBRmXrOdJYRQNEEkUl4 r73M7fho8QHRPAUrbSuG0UVKeYRPvS6adMCzBnDyqbCDRNdBfNZDeJK2j3LhcxaJmM+m 3Biw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=LHn7sh6ZYwvh5+D/h2PrSTgVx9fde1Yu4h3Dr05pCsY=; b=E5+XNm20G2oCA+tG6+Sa7k01k8y+gi5FWwaMxzpHP6N99QkEIxiNrmbXkk5ZHWGhge nefr2l6rpZbIJT0KpdwRbak2X/sl27dCksZ5XZ7jFpRXbvlf547Hg62sBT5kYrpxZp2M WrS55G2biH/v53vQ21SKxkKNVhXV4dAKq8wqkV1pKe/2h+Fgxf43uWVsdg0GYPODz2DW eDnSs/X/mhMBdU2BeFQPsnYtUVOajB7QbY++8X4mR2mVVCDfvlbYj0OoJgBTizOaYLkK eYXRfFioETj3ifk/m3E1VKrw1t1CzCFcDA5iIh59DleKdm6VRwhq87jsa6mbHeWfP5pK kdgw== X-Gm-Message-State: APjAAAWeBeMJYFqGN/pwwE7Z9dov4u5eYlgk84yBjpmCorjKUlyNAssF MszPxzyg/cu2T0ApyrFM0QFNew== X-Received: by 2002:a17:90a:2228:: with SMTP id c37mr32162607pje.9.1562667724503; Tue, 09 Jul 2019 03:22:04 -0700 (PDT) Received: from localhost.localdomain (123-204-46-122.static.seed.net.tw. [123.204.46.122]) by smtp.gmail.com with ESMTPSA id j1sm40161849pgl.12.2019.07.09.03.22.00 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Tue, 09 Jul 2019 03:22:03 -0700 (PDT) From: Jian-Hong Pan To: Yan-Hsuan Chuang , Kalle Valo , "David S . Miller" , Larry Finger , David Laight Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux@endlessm.com, Daniel Drake , Jian-Hong Pan , stable@vger.kernel.org Subject: [PATCH v2 1/2] rtw88: pci: Rearrange the memory usage for skb in RX ISR Date: Tue, 9 Jul 2019 18:20:59 +0800 Message-Id: <20190709102059.7036-1-jian-hong@endlessm.com> X-Mailer: git-send-email 2.22.0 In-Reply-To: <20190708063252.4756-1-jian-hong@endlessm.com> References: <20190708063252.4756-1-jian-hong@endlessm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Testing with RTL8822BE hardware, when available memory is low, we frequently see a kernel panic and system freeze. First, rtw_pci_rx_isr encounters a memory allocation failure (trimmed): rx routine starvation WARNING: CPU: 7 PID: 9871 at drivers/net/wireless/realtek/rtw88/pci.c:822 rtw_pci_rx_isr.constprop.25+0x35a/0x370 [rtwpci] [ 2356.580313] RIP: 0010:rtw_pci_rx_isr.constprop.25+0x35a/0x370 [rtwpci] Then we see a variety of different error conditions and kernel panics, such as this one (trimmed): rtw_pci 0000:02:00.0: pci bus timeout, check dma status skbuff: skb_over_panic: text:00000000091b6e66 len:415 put:415 head:00000000d2880c6f data:000000007a02b1ea tail:0x1df end:0xc0 dev: ------------[ cut here ]------------ kernel BUG at net/core/skbuff.c:105! invalid opcode: 0000 [#1] SMP NOPTI RIP: 0010:skb_panic+0x43/0x45 When skb allocation fails and the "rx routine starvation" is hit, the function returns immediately without updating the RX ring. At this point, the RX ring may continue referencing an old skb which was already handed off to ieee80211_rx_irqsafe(). When it comes to be used again, bad things happen. This patch allocates a new, data-sized skb first in RX ISR. After copying the data in, we pass it to the upper layers. However, if skb allocation fails, we effectively drop the frame. In both cases, the original, full size ring skb is reused. In addition, to fixing the kernel crash, the RX routine should now generally behave better under low memory conditions. Buglink: https://bugzilla.kernel.org/show_bug.cgi?id=204053 Signed-off-by: Jian-Hong Pan Cc: --- drivers/net/wireless/realtek/rtw88/pci.c | 49 +++++++++++------------- 1 file changed, 22 insertions(+), 27 deletions(-) diff --git a/drivers/net/wireless/realtek/rtw88/pci.c b/drivers/net/wireless/realtek/rtw88/pci.c index cfe05ba7280d..e9fe3ad896c8 100644 --- a/drivers/net/wireless/realtek/rtw88/pci.c +++ b/drivers/net/wireless/realtek/rtw88/pci.c @@ -763,6 +763,7 @@ static void rtw_pci_rx_isr(struct rtw_dev *rtwdev, struct rtw_pci *rtwpci, u32 pkt_offset; u32 pkt_desc_sz = chip->rx_pkt_desc_sz; u32 buf_desc_sz = chip->rx_buf_desc_sz; + u32 new_len; u8 *rx_desc; dma_addr_t dma; @@ -790,40 +791,34 @@ static void rtw_pci_rx_isr(struct rtw_dev *rtwdev, struct rtw_pci *rtwpci, pkt_offset = pkt_desc_sz + pkt_stat.drv_info_sz + pkt_stat.shift; - if (pkt_stat.is_c2h) { - /* keep rx_desc, halmac needs it */ - skb_put(skb, pkt_stat.pkt_len + pkt_offset); + /* discard current skb if the new skb cannot be allocated as a + * new one in rx ring later + */ + new_len = pkt_stat.pkt_len + pkt_offset; + new = dev_alloc_skb(new_len); + if (WARN_ONCE(!new, "rx routine starvation\n")) + goto next_rp; + + /* put the DMA data including rx_desc from phy to new skb */ + skb_put_data(new, skb->data, new_len); - /* pass offset for further operation */ - *((u32 *)skb->cb) = pkt_offset; - skb_queue_tail(&rtwdev->c2h_queue, skb); + if (pkt_stat.is_c2h) { + /* pass rx_desc & offset for further operation */ + *((u32 *)new->cb) = pkt_offset; + skb_queue_tail(&rtwdev->c2h_queue, new); ieee80211_queue_work(rtwdev->hw, &rtwdev->c2h_work); } else { - /* remove rx_desc, maybe use skb_pull? */ - skb_put(skb, pkt_stat.pkt_len); - skb_reserve(skb, pkt_offset); - - /* alloc a smaller skb to mac80211 */ - new = dev_alloc_skb(pkt_stat.pkt_len); - if (!new) { - new = skb; - } else { - skb_put_data(new, skb->data, skb->len); - dev_kfree_skb_any(skb); - } - /* TODO: merge into rx.c */ - rtw_rx_stats(rtwdev, pkt_stat.vif, skb); + /* remove rx_desc */ + skb_pull(new, pkt_offset); + + rtw_rx_stats(rtwdev, pkt_stat.vif, new); memcpy(new->cb, &rx_status, sizeof(rx_status)); ieee80211_rx_irqsafe(rtwdev->hw, new); } - /* skb delivered to mac80211, alloc a new one in rx ring */ - new = dev_alloc_skb(RTK_PCI_RX_BUF_SIZE); - if (WARN(!new, "rx routine starvation\n")) - return; - - ring->buf[cur_rp] = new; - rtw_pci_reset_rx_desc(rtwdev, new, ring, cur_rp, buf_desc_sz); +next_rp: + /* new skb delivered to mac80211, re-enable original skb DMA */ + rtw_pci_reset_rx_desc(rtwdev, skb, ring, cur_rp, buf_desc_sz); /* host read next element in ring */ if (++cur_rp >= ring->r.len) -- 2.22.0