From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C5A2A153598 for ; Tue, 19 Nov 2024 04:00:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1731988834; cv=none; b=qNzV9TDzGmGyriwg+VOHoOU+HPLE3pwshDSl6Vg5S2ZG+iHXpPhnVSBf6oG+hkMEyEez1gZ6kyOhgwIvamovJ2RAhakUWO/Z1oSlAjZkMPPzR2eR27mhsAOXVAC1Dbqv5haeggwdk+ax+y5YwJwWvfiu7qpLmnNtecqIMHoPXnk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1731988834; c=relaxed/simple; bh=XMxXePRIUNYrcx+oHmMdO0vMKcuyikB2EZRQK8MUx6o=; h=Date:From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type: Content-Disposition; b=KMLvDy8dj2Ax9F9VvqufK8QvERsPqNmdsWgEBlIcWYnZpbnBNiHOSLgEfo29FXcQhybty6bjoqof+O73Expc/+GQKQvUYyDq5E66xI25o6l81+eW1MTvdT26ggKlB7V/ERd+Lf+Xf2dTopkqUZtA5ZY0LY1Unb+j99DSEHOaEOg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=JDj4QGYz; arc=none smtp.client-ip=192.198.163.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="JDj4QGYz" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1731988832; x=1763524832; h=date:from:to:cc:subject:message-id:mime-version; bh=XMxXePRIUNYrcx+oHmMdO0vMKcuyikB2EZRQK8MUx6o=; b=JDj4QGYzf0NUGOm6ZC60AoOl3ANi1dvd9pe3l+/TlUjHyazFsp+GJbSC GHkfZSCpTeqDVMx1d1ebS3F+x/plnAe/1NtkqJRmSqgHhx2TvlZ6E6EXS sjPBBLf6YiWhAYsHUgxSFDB5070L8/jGp9Cz73tH6DZUzA5aw4bvRoDHS vAVI/3TulIEAd9nKFwEPoj8TkCJlq+Zv87FrmZaLS+uZEwXB0uxX5ndRz +kzvHvf6T7DO2sGCdhPTmCovxOd+Q9hew3LrBKzRvMrtMn3BQkn/AS0Su dNYQof01E587VTGqN89hSywmiu0GD5/qS3Nrcp96i+YtEtuBnbBZHbeQH w==; X-CSE-ConnectionGUID: yB5BLbBHQPStSAH3ylObAw== X-CSE-MsgGUID: tlCvWNE3Q66tZXgPlINc6g== X-IronPort-AV: E=McAfee;i="6700,10204,11260"; a="42600222" X-IronPort-AV: E=Sophos;i="6.12,165,1728975600"; d="scan'208";a="42600222" Received: from fmviesa009.fm.intel.com ([10.60.135.149]) by fmvoesa105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Nov 2024 20:00:31 -0800 X-CSE-ConnectionGUID: rY8h/9pfQKqD218IaknpcQ== X-CSE-MsgGUID: x+ZNwzC9SDCR+aTAZmUtUw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.12,165,1728975600"; d="scan'208";a="89848799" Received: from lkp-server02.sh.intel.com (HELO 2cc4542d09d4) ([10.239.97.151]) by fmviesa009.fm.intel.com with ESMTP; 18 Nov 2024 20:00:30 -0800 Received: from kbuild by 2cc4542d09d4 with local (Exim 4.96) (envelope-from ) id 1tDFPf-00005s-1Y; Tue, 19 Nov 2024 04:00:27 +0000 Date: Tue, 19 Nov 2024 11:59:43 +0800 From: kernel test robot To: kernel@openeuler.org, Wupeng Ma Cc: oe-kbuild-all@lists.linux.dev Subject: [openeuler:OLK-6.6 1474/1474] mm/memblock.c:1409:20: sparse: sparse: symbol 'memblock_alloc_range_nid_flags' was not declared. Should it be static? Message-ID: <202411191138.D8HmiY92-lkp@intel.com> Precedence: bulk X-Mailing-List: oe-kbuild-all@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: 8a039651010897592567f5751c4e706ab794e9c0 commit: 64018b291c1f49622c4b23b303364d760306d662 [1474/1474] mm/memblock: Introduce ability to alloc memory from specify memory region config: x86_64-randconfig-121-20241118 (https://download.01.org/0day-ci/archive/20241119/202411191138.D8HmiY92-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/20241119/202411191138.D8HmiY92-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 | Closes: https://lore.kernel.org/oe-kbuild-all/202411191138.D8HmiY92-lkp@intel.com/ sparse warnings: (new ones prefixed by >>) >> mm/memblock.c:1409:20: sparse: sparse: symbol 'memblock_alloc_range_nid_flags' was not declared. Should it be static? vim +/memblock_alloc_range_nid_flags +1409 mm/memblock.c 1386 1387 /** 1388 * memblock_alloc_range_nid_flags - allocate boot memory block with specify flag 1389 * @size: size of memory block to be allocated in bytes 1390 * @align: alignment of the region and block's size 1391 * @start: the lower bound of the memory region to allocate (phys address) 1392 * @end: the upper bound of the memory region to allocate (phys address) 1393 * @nid: nid of the free area to find, %NUMA_NO_NODE for any node 1394 * @exact_nid: control the allocation fall back to other nodes 1395 * @flags: alloc memory from specify memblock flag 1396 * 1397 * The allocation is performed from memory region limited by 1398 * memblock.current_limit if @end == %MEMBLOCK_ALLOC_ACCESSIBLE. 1399 * 1400 * If the specified node can not hold the requested memory and @exact_nid 1401 * is false, the allocation falls back to any node in the system. 1402 * 1403 * In addition, function sets the min_count to 0 using kmemleak_alloc_phys for 1404 * allocated boot memory block, so that it is never reported as leaks. 1405 * 1406 * Return: 1407 * Physical address of allocated memory block on success, %0 on failure. 1408 */ > 1409 phys_addr_t __init memblock_alloc_range_nid_flags(phys_addr_t size, 1410 phys_addr_t align, phys_addr_t start, 1411 phys_addr_t end, int nid, 1412 bool exact_nid, 1413 enum memblock_flags flags) 1414 { 1415 phys_addr_t found; 1416 1417 if (WARN_ONCE(nid == MAX_NUMNODES, "Usage of MAX_NUMNODES is deprecated. Use NUMA_NO_NODE instead\n")) 1418 nid = NUMA_NO_NODE; 1419 1420 if (!align) { 1421 /* Can't use WARNs this early in boot on powerpc */ 1422 dump_stack(); 1423 align = SMP_CACHE_BYTES; 1424 } 1425 1426 again: 1427 found = memblock_find_in_range_node(size, align, start, end, nid, 1428 flags); 1429 if (found && !memblock_reserve(found, size)) 1430 goto done; 1431 1432 if (nid != NUMA_NO_NODE && !exact_nid) { 1433 found = memblock_find_in_range_node(size, align, start, 1434 end, NUMA_NO_NODE, 1435 flags); 1436 if (found && !memblock_reserve(found, size)) 1437 goto done; 1438 } 1439 1440 if (flags & MEMBLOCK_MIRROR) { 1441 flags &= ~MEMBLOCK_MIRROR; 1442 pr_warn_ratelimited("Could not allocate %pap bytes of mirrored memory\n", 1443 &size); 1444 goto again; 1445 } 1446 1447 return 0; 1448 1449 done: 1450 /* 1451 * Skip kmemleak for those places like kasan_init() and 1452 * early_pgtable_alloc() due to high volume. 1453 */ 1454 if (end != MEMBLOCK_ALLOC_NOLEAKTRACE) 1455 /* 1456 * Memblock allocated blocks are never reported as 1457 * leaks. This is because many of these blocks are 1458 * only referred via the physical address which is 1459 * not looked up by kmemleak. 1460 */ 1461 kmemleak_alloc_phys(found, size, 0); 1462 1463 /* 1464 * Some Virtual Machine platforms, such as Intel TDX or AMD SEV-SNP, 1465 * require memory to be accepted before it can be used by the 1466 * guest. 1467 * 1468 * Accept the memory of the allocated buffer. 1469 */ 1470 accept_memory(found, found + size); 1471 1472 return found; 1473 } 1474 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki