From: kernel test robot <lkp@intel.com>
To: Thomas Fourier <fourier.thomas@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Thomas Fourier <fourier.thomas@gmail.com>,
Ping-Ke Shih <pkshih@realtek.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drive/realtek/rtlwifi: fix possible memory leak
Date: Fri, 13 Jun 2025 06:45:06 +0800 [thread overview]
Message-ID: <202506130644.NKPuRVsI-lkp@intel.com> (raw)
In-Reply-To: <20250612090724.17777-1-fourier.thomas@gmail.com>
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on wireless-next/main]
[also build test ERROR on wireless/main linus/master v6.16-rc1 next-20250612]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Fourier/drive-realtek-rtlwifi-fix-possible-memory-leak/20250612-171134
base: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
patch link: https://lore.kernel.org/r/20250612090724.17777-1-fourier.thomas%40gmail.com
patch subject: [PATCH] drive/realtek/rtlwifi: fix possible memory leak
config: i386-randconfig-006-20250613 (https://download.01.org/0day-ci/archive/20250613/202506130644.NKPuRVsI-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250613/202506130644.NKPuRVsI-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202506130644.NKPuRVsI-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/net/wireless/realtek/rtlwifi/pci.c: In function '_rtl_pci_init_one_rxdesc':
>> drivers/net/wireless/realtek/rtlwifi/pci.c:577:39: error: expected ';' before 'return'
577 | kfree_skb(skb)
| ^
| ;
578 | return 0;
| ~~~~~~
vim +577 drivers/net/wireless/realtek/rtlwifi/pci.c
550
551 static int _rtl_pci_init_one_rxdesc(struct ieee80211_hw *hw,
552 struct sk_buff *new_skb, u8 *entry,
553 int rxring_idx, int desc_idx)
554 {
555 struct rtl_priv *rtlpriv = rtl_priv(hw);
556 struct rtl_pci *rtlpci = rtl_pcidev(rtl_pcipriv(hw));
557 u32 bufferaddress;
558 u8 tmp_one = 1;
559 struct sk_buff *skb;
560
561 if (likely(new_skb)) {
562 skb = new_skb;
563 goto remap;
564 }
565 skb = dev_alloc_skb(rtlpci->rxbuffersize);
566 if (!skb)
567 return 0;
568
569 remap:
570 /* just set skb->cb to mapping addr for pci_unmap_single use */
571 *((dma_addr_t *)skb->cb) =
572 dma_map_single(&rtlpci->pdev->dev, skb_tail_pointer(skb),
573 rtlpci->rxbuffersize, DMA_FROM_DEVICE);
574 bufferaddress = *((dma_addr_t *)skb->cb);
575 if (dma_mapping_error(&rtlpci->pdev->dev, bufferaddress)) {
576 if (!new_skb)
> 577 kfree_skb(skb)
578 return 0;
579 }
580 rtlpci->rx_ring[rxring_idx].rx_buf[desc_idx] = skb;
581 if (rtlpriv->use_new_trx_flow) {
582 /* skb->cb may be 64 bit address */
583 rtlpriv->cfg->ops->set_desc(hw, (u8 *)entry, false,
584 HW_DESC_RX_PREPARE,
585 (u8 *)(dma_addr_t *)skb->cb);
586 } else {
587 rtlpriv->cfg->ops->set_desc(hw, (u8 *)entry, false,
588 HW_DESC_RXBUFF_ADDR,
589 (u8 *)&bufferaddress);
590 rtlpriv->cfg->ops->set_desc(hw, (u8 *)entry, false,
591 HW_DESC_RXPKT_LEN,
592 (u8 *)&rtlpci->rxbuffersize);
593 rtlpriv->cfg->ops->set_desc(hw, (u8 *)entry, false,
594 HW_DESC_RXOWN,
595 (u8 *)&tmp_one);
596 }
597 return 1;
598 }
599
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-12 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 9:07 Thomas Fourier
2025-06-12 22:45 ` kernel test robot [this message]
2025-06-13 0:41 ` Ping-Ke Shih
2025-06-13 7:38 ` [PATCH rtw-next] wifi: rtlwifi: fix possible skb memory leak in _rtl_pci_init_one_rxdesc() Thomas Fourier
2025-06-16 3:56 ` Ping-Ke Shih
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=202506130644.NKPuRVsI-lkp@intel.com \
--to=lkp@intel.com \
--cc=fourier.thomas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pkshih@realtek.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
all inboxes | Powered by JetHome®