From: kernel test robot <lkp@intel.com>
To: Holger Brunck <holger.brunck@hitachienergy.com>, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linuxppc-dev@lists.ozlabs.org, andrew+netdev@lunn.ch,
chleroy@kernel.org, qiang.zhao@nxp.com, horms@kernel.org,
Holger Brunck <holger.brunck@hitachienergy.com>
Subject: Re: [PATCH net] net: wan: fsl_ucc_hdlc: free tx_skbuff in uhdlc_memclean
Date: Fri, 15 May 2026 11:05:07 +0800 [thread overview]
Message-ID: <202605151029.MIApM8zq-lkp@intel.com> (raw)
In-Reply-To: <20260504161145.2217950-1-holger.brunck@hitachienergy.com>
Hi Holger,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
[also build test ERROR on v7.1-rc3 next-20260508]
[cannot apply to net/main linus/master]
[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/Holger-Brunck/net-wan-fsl_ucc_hdlc-free-tx_skbuff-in-uhdlc_memclean/20260514-055007
base: net-next/main
patch link: https://lore.kernel.org/r/20260504161145.2217950-1-holger.brunck%40hitachienergy.com
patch subject: [PATCH net] net: wan: fsl_ucc_hdlc: free tx_skbuff in uhdlc_memclean
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20260515/202605151029.MIApM8zq-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260515/202605151029.MIApM8zq-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/202605151029.MIApM8zq-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
>> drivers/net/wan/fsl_ucc_hdlc.c:775:32: error: expected ';' in 'for' statement specifier
775 | for (i = 0; i < TX_BD_RING_LEN) {
| ^
>> drivers/net/wan/fsl_ucc_hdlc.c:775:14: warning: variable 'i' used in loop condition not modified in loop body [-Wfor-loop-analysis]
775 | for (i = 0; i < TX_BD_RING_LEN) {
| ^
1 warning and 1 error generated.
vim +775 drivers/net/wan/fsl_ucc_hdlc.c
740
741 static void uhdlc_memclean(struct ucc_hdlc_private *priv)
742 {
743 int i;
744
745 qe_muram_free(ioread16be(&priv->ucc_pram->riptr));
746 qe_muram_free(ioread16be(&priv->ucc_pram->tiptr));
747
748 if (priv->rx_bd_base) {
749 dma_free_coherent(priv->dev,
750 RX_BD_RING_LEN * sizeof(struct qe_bd),
751 priv->rx_bd_base, priv->dma_rx_bd);
752
753 priv->rx_bd_base = NULL;
754 priv->dma_rx_bd = 0;
755 }
756
757 if (priv->tx_bd_base) {
758 dma_free_coherent(priv->dev,
759 TX_BD_RING_LEN * sizeof(struct qe_bd),
760 priv->tx_bd_base, priv->dma_tx_bd);
761
762 priv->tx_bd_base = NULL;
763 priv->dma_tx_bd = 0;
764 }
765
766 if (priv->ucc_pram) {
767 qe_muram_free(priv->ucc_pram_offset);
768 priv->ucc_pram = NULL;
769 priv->ucc_pram_offset = 0;
770 }
771
772 kfree(priv->rx_skbuff);
773 priv->rx_skbuff = NULL;
774
> 775 for (i = 0; i < TX_BD_RING_LEN) {
776 kfree(priv->tx_skbuff[i]);
777 priv->tx_skbuff[i] = NULL;
778 }
779
780 kfree(priv->tx_skbuff);
781 priv->tx_skbuff = NULL;
782
783 if (priv->uccf) {
784 ucc_fast_free(priv->uccf);
785 priv->uccf = NULL;
786 }
787
788 if (priv->rx_buffer) {
789 dma_free_coherent(priv->dev,
790 (RX_BD_RING_LEN + TX_BD_RING_LEN) * MAX_RX_BUF_LENGTH,
791 priv->rx_buffer, priv->dma_rx_addr);
792 priv->rx_buffer = NULL;
793 priv->dma_rx_addr = 0;
794
795 priv->tx_buffer = NULL;
796 priv->dma_tx_addr = 0;
797
798 }
799 }
800
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-05-15 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 16:11 [PATCH net] net: wan: fsl_ucc_hdlc: free tx_skbuff in uhdlc_memclean Holger Brunck
2026-05-05 5:37 ` Christophe Leroy (CS GROUP)
2026-05-05 8:33 ` Holger Brunck
2026-05-05 23:47 ` Jakub Kicinski
2026-05-06 8:27 ` Holger Brunck
2026-05-15 3:05 ` kernel test robot [this message]
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=202605151029.MIApM8zq-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=chleroy@kernel.org \
--cc=holger.brunck@hitachienergy.com \
--cc=horms@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=qiang.zhao@nxp.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