All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [openeuler:openEuler-1.0-LTS 1941/1941] drivers/dma/pl330.c:2599:15: warning: 'src' may be used uninitialized in this function
Date: Sat, 13 Dec 2025 04:28:04 +0800	[thread overview]
Message-ID: <202512130409.sZE93fMA-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "likely FALSE maybe-used-uninitialized warning on old compiler"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: kernel@openeuler.org

Hi Frank,

First bad commit (maybe != root cause):

tree:   https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head:   df8d11fbcbb07177c2500e63d7f5a36063977596
commit: 0299853c014aa0eecf7fb85ac2f1ebd0a9a6ba73 [1941/1941] dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV
:::::: branch date: 17 hours ago
:::::: commit date: 1 year, 9 months ago
config: arm64-randconfig-002-20251212 (https://download.01.org/0day-ci/archive/20251213/202512130409.sZE93fMA-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251213/202512130409.sZE93fMA-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/r/202512130409.sZE93fMA-lkp@intel.com/

Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings

All warnings (new ones prefixed by >>):

   drivers/dma/pl330.c: In function 'pl330_prep_dma_cyclic':
>> drivers/dma/pl330.c:2599:15: warning: 'src' may be used uninitialized in this function [-Wmaybe-uninitialized]
     px->src_addr = src;
     ~~~~~~~~~~~~~^~~~~
   drivers/dma/pl330.c:2657:13: note: 'src' was declared here
     dma_addr_t src;
                ^~~
>> drivers/dma/pl330.c:2598:15: warning: 'dst' may be used uninitialized in this function [-Wmaybe-uninitialized]
     px->dst_addr = dst;
     ~~~~~~~~~~~~~^~~~~
   drivers/dma/pl330.c:2656:13: note: 'dst' was declared here
     dma_addr_t dst;
                ^~~
   drivers/dma/pl330.c:297: warning: cannot understand function prototype: 'struct pl330_reqcfg '


vim +/src +2599 drivers/dma/pl330.c

b3040e40675ec2 Jassi Brar 2010-05-23  2593  
b3040e40675ec2 Jassi Brar 2010-05-23  2594  static inline void fill_px(struct pl330_xfer *px,
b3040e40675ec2 Jassi Brar 2010-05-23  2595  		dma_addr_t dst, dma_addr_t src, size_t len)
b3040e40675ec2 Jassi Brar 2010-05-23  2596  {
b3040e40675ec2 Jassi Brar 2010-05-23  2597  	px->bytes = len;
b3040e40675ec2 Jassi Brar 2010-05-23 @2598  	px->dst_addr = dst;
b3040e40675ec2 Jassi Brar 2010-05-23 @2599  	px->src_addr = src;
b3040e40675ec2 Jassi Brar 2010-05-23  2600  }
b3040e40675ec2 Jassi Brar 2010-05-23  2601  

:::::: The code at line 2599 was first introduced by commit
:::::: b3040e40675ec2c43542331cd30d4ee3dae797e8 DMA: PL330: Add dma api driver

:::::: TO: Jassi Brar <jassi.brar@samsung.com>
:::::: CC: Dan Williams <dan.j.williams@intel.com>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-12-12 20:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202512130409.sZE93fMA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.