From: kernel test robot <lkp@intel.com>
To: Dev Jain <dev.jain@arm.com>,
akpm@linux-foundation.org, david@redhat.com, willy@infradead.org,
kirill.shutemov@linux.intel.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
ryan.roberts@arm.com, anshuman.khandual@arm.com,
catalin.marinas@arm.com, cl@gentwo.org, vbabka@suse.cz,
mhocko@suse.com, apopple@nvidia.com, dave.hansen@linux.intel.com,
will@kernel.org, baohua@kernel.org, jack@suse.cz,
mark.rutland@arm.com, hughd@google.com, aneesh.kumar@kernel.org,
yang@os.amperecomputing.com, peterx@redhat.com,
ioworker0@gmail.com, jglisse@google.com,
wangkefeng.wang@huawei.com, ziy@nvidia.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Dev Jain <dev.jain@arm.com>
Subject: Re: [PATCH v3 1/2] mm: Abstract THP allocation
Date: Thu, 12 Sep 2024 21:26:48 +0800 [thread overview]
Message-ID: <202409122144.jqe4JROY-lkp@intel.com> (raw)
In-Reply-To: <20240911065600.1002644-2-dev.jain@arm.com>
Hi Dev,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.11-rc7]
[also build test WARNING on linus/master]
[cannot apply to akpm-mm/mm-everything next-20240912]
[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/Dev-Jain/mm-Abstract-THP-allocation/20240911-145809
base: v6.11-rc7
patch link: https://lore.kernel.org/r/20240911065600.1002644-2-dev.jain%40arm.com
patch subject: [PATCH v3 1/2] mm: Abstract THP allocation
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240912/202409122144.jqe4JROY-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/20240912/202409122144.jqe4JROY-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/202409122144.jqe4JROY-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/huge_memory.c:1012:6: warning: variable 'pgtable' is used uninitialized whenever 'if' condition is true [-Wsometimes-uninitialized]
1012 | if (unlikely(!folio)) {
| ^~~~~~~~~~~~~~~~
include/linux/compiler.h:77:22: note: expanded from macro 'unlikely'
77 | # define unlikely(x) __builtin_expect(!!(x), 0)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
mm/huge_memory.c:1051:6: note: uninitialized use occurs here
1051 | if (pgtable)
| ^~~~~~~
mm/huge_memory.c:1012:2: note: remove the 'if' if its condition is always false
1012 | if (unlikely(!folio)) {
| ^~~~~~~~~~~~~~~~~~~~~~~
1013 | ret = VM_FAULT_FALLBACK;
| ~~~~~~~~~~~~~~~~~~~~~~~~
1014 | goto release;
| ~~~~~~~~~~~~~
1015 | }
| ~
mm/huge_memory.c:1006:19: note: initialize the variable 'pgtable' to silence this warning
1006 | pgtable_t pgtable;
| ^
| = NULL
1 warning generated.
vim +1012 mm/huge_memory.c
1001
1002 static vm_fault_t __do_huge_pmd_anonymous_page(struct vm_fault *vmf)
1003 {
1004 struct vm_area_struct *vma = vmf->vma;
1005 struct folio *folio;
1006 pgtable_t pgtable;
1007 unsigned long haddr = vmf->address & HPAGE_PMD_MASK;
1008 vm_fault_t ret = 0;
1009 gfp_t gfp = vma_thp_gfp_mask(vma);
1010
1011 folio = pmd_thp_fault_alloc(gfp, vma, haddr, vmf->address);
> 1012 if (unlikely(!folio)) {
1013 ret = VM_FAULT_FALLBACK;
1014 goto release;
1015 }
1016
1017 pgtable = pte_alloc_one(vma->vm_mm);
1018 if (unlikely(!pgtable)) {
1019 ret = VM_FAULT_OOM;
1020 goto release;
1021 }
1022
1023 vmf->ptl = pmd_lock(vma->vm_mm, vmf->pmd);
1024
1025 if (unlikely(!pmd_none(*vmf->pmd))) {
1026 goto unlock_release;
1027 } else {
1028 ret = check_stable_address_space(vma->vm_mm);
1029 if (ret)
1030 goto unlock_release;
1031
1032 /* Deliver the page fault to userland */
1033 if (userfaultfd_missing(vma)) {
1034 spin_unlock(vmf->ptl);
1035 folio_put(folio);
1036 pte_free(vma->vm_mm, pgtable);
1037 ret = handle_userfault(vmf, VM_UFFD_MISSING);
1038 VM_BUG_ON(ret & VM_FAULT_FALLBACK);
1039 return ret;
1040 }
1041 pgtable_trans_huge_deposit(vma->vm_mm, vmf->pmd, pgtable);
1042 map_pmd_thp(folio, vmf, vma, haddr);
1043 spin_unlock(vmf->ptl);
1044 __pmd_thp_fault_success_stats(vma);
1045 }
1046
1047 return 0;
1048 unlock_release:
1049 spin_unlock(vmf->ptl);
1050 release:
1051 if (pgtable)
1052 pte_free(vma->vm_mm, pgtable);
1053 if (folio)
1054 folio_put(folio);
1055 return ret;
1056
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-12 13:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 6:55 [PATCH v3 0/2] Do not shatter hugezeropage on wp-fault Dev Jain
2024-09-11 6:55 ` [PATCH v3 1/2] mm: Abstract THP allocation Dev Jain
2024-09-11 9:27 ` David Hildenbrand
2024-09-11 9:29 ` David Hildenbrand
2024-09-11 12:02 ` Dev Jain
2024-09-11 12:00 ` Dev Jain
2024-09-11 12:35 ` David Hildenbrand
2024-09-11 12:55 ` Dev Jain
2024-09-11 12:53 ` Dev Jain
2024-09-11 13:00 ` David Hildenbrand
2024-09-11 13:05 ` Dev Jain
2024-09-11 13:14 ` David Hildenbrand
2024-09-11 13:16 ` Dev Jain
2024-09-11 10:52 ` Kefeng Wang
2024-09-11 12:22 ` Dev Jain
2024-09-12 13:26 ` kernel test robot [this message]
2024-09-11 6:56 ` [PATCH v3 2/2] mm: Allocate THP on hugezeropage wp-fault Dev Jain
2024-09-11 9:36 ` David Hildenbrand
2024-09-11 12:10 ` Dev Jain
2024-09-11 12:36 ` David Hildenbrand
2024-09-12 15:44 ` kernel test robot
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=202409122144.jqe4JROY-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=apopple@nvidia.com \
--cc=baohua@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cl@gentwo.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hughd@google.com \
--cc=ioworker0@gmail.com \
--cc=jack@suse.cz \
--cc=jglisse@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterx@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.com \
--cc=ziy@nvidia.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