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, Dan Carpenter <error27@gmail.com>
Subject: [linux-next:master 776/12662] drivers/gpu/drm/drm_gpuvm.c:1321 drm_gpuvm_exec_lock_range() error: uninitialized symbol 'ret'.
Date: Sat, 6 Jan 2024 19:22:25 +0800	[thread overview]
Message-ID: <202401061927.fCkU4eLk-lkp@intel.com> (raw)

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: Linux Memory Management List <linux-mm@kvack.org>
TO: Danilo Krummrich <dakr@redhat.com>
CC: Boris Brezillon <bbrezillon@kernel.org>
CC: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   e2425464bc87159274879ab30f9d4fe624b9fcd2
commit: 50c1a36f594bb3dd33f3f9386c5d960cd12327d8 [776/12662] drm/gpuvm: track/lock/validate external/evicted objects
:::::: branch date: 28 hours ago
:::::: commit date: 8 weeks ago
config: i386-randconfig-141-20231115 (https://download.01.org/0day-ci/archive/20240106/202401061927.fCkU4eLk-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0

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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202401061927.fCkU4eLk-lkp@intel.com/

smatch warnings:
drivers/gpu/drm/drm_gpuvm.c:1321 drm_gpuvm_exec_lock_range() error: uninitialized symbol 'ret'.

vim +/ret +1321 drivers/gpu/drm/drm_gpuvm.c

50c1a36f594bb3 Danilo Krummrich 2023-11-08  1291  
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1292  /**
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1293   * drm_gpuvm_exec_lock_range() - prepare all BOs mapped within a given range
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1294   * @vm_exec: the &drm_gpuvm_exec wrapper
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1295   * @addr: the start address within the VA space
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1296   * @range: the range to iterate within the VA space
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1297   *
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1298   * Acquires all dma-resv locks of all &drm_gem_objects mapped between @addr and
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1299   * @addr + @range.
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1300   *
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1301   * Returns: 0 on success, negative error code on failure.
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1302   */
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1303  int
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1304  drm_gpuvm_exec_lock_range(struct drm_gpuvm_exec *vm_exec,
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1305  			  u64 addr, u64 range)
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1306  {
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1307  	struct drm_gpuvm *gpuvm = vm_exec->vm;
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1308  	struct drm_exec *exec = &vm_exec->exec;
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1309  	int ret;
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1310  
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1311  	drm_exec_init(exec, vm_exec->flags);
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1312  
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1313  	drm_exec_until_all_locked(exec) {
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1314  		ret = drm_gpuvm_prepare_range(gpuvm, exec, addr, range,
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1315  					      vm_exec->num_fences);
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1316  		drm_exec_retry_on_contention(exec);
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1317  		if (ret)
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1318  			goto err;
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1319  	}
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1320  
50c1a36f594bb3 Danilo Krummrich 2023-11-08 @1321  	return ret;
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1322  
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1323  err:
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1324  	drm_exec_fini(exec);
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1325  	return ret;
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1326  }
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1327  EXPORT_SYMBOL_GPL(drm_gpuvm_exec_lock_range);
50c1a36f594bb3 Danilo Krummrich 2023-11-08  1328  

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

                 reply	other threads:[~2024-01-06 11:23 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=202401061927.fCkU4eLk-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=error27@gmail.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.