From: kernel test robot <lkp@intel.com>
To: Peter Xu <peterx@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: mm/gup.c:778:15: sparse: sparse: cast to non-scalar
Date: Fri, 24 Jan 2025 10:01:40 +0800 [thread overview]
Message-ID: <202501240922.a4YzQD7u-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: e0b1f59142746f74476a03040f745329c8355a7e
commit: e6fd5564c07c3c749ff3d1b2aa35540b4047e395 mm/gup: cache p4d in follow_p4d_mask()
date: 9 months ago
config: alpha-randconfig-r112-20250124 (https://download.01.org/0day-ci/archive/20250124/202501240922.a4YzQD7u-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250124/202501240922.a4YzQD7u-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/202501240922.a4YzQD7u-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/gup.c:778:15: sparse: sparse: cast to non-scalar
>> mm/gup.c:778:15: sparse: sparse: cast from non-scalar
mm/gup.c: note: in included file (through include/linux/mm.h):
include/linux/pgtable.h:315:16: sparse: sparse: cast to non-scalar
include/linux/pgtable.h:315:16: sparse: sparse: cast from non-scalar
include/linux/pgtable.h:315:16: sparse: sparse: cast to non-scalar
include/linux/pgtable.h:315:16: sparse: sparse: cast from non-scalar
mm/gup.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/mm.h):
include/linux/page-flags.h:241:46: sparse: sparse: self-comparison always evaluates to false
mm/gup.c:682:9: sparse: sparse: context imbalance in 'follow_page_pte' - unexpected unlock
mm/gup.c: note: in included file (through include/linux/mm.h):
include/linux/pgtable.h:322:16: sparse: sparse: cast to non-scalar
include/linux/pgtable.h:322:16: sparse: sparse: cast from non-scalar
include/linux/pgtable.h:315:16: sparse: sparse: cast to non-scalar
include/linux/pgtable.h:315:16: sparse: sparse: cast from non-scalar
mm/gup.c:911:18: sparse: sparse: context imbalance in 'get_gate_page' - unexpected unlock
vim +778 mm/gup.c
769
770 static struct page *follow_p4d_mask(struct vm_area_struct *vma,
771 unsigned long address, pgd_t *pgdp,
772 unsigned int flags,
773 struct follow_page_context *ctx)
774 {
775 p4d_t *p4dp, p4d;
776
777 p4dp = p4d_offset(pgdp, address);
> 778 p4d = READ_ONCE(*p4dp);
779 if (p4d_none(p4d))
780 return no_page_table(vma, flags);
781 BUILD_BUG_ON(p4d_huge(p4d));
782 if (unlikely(p4d_bad(p4d)))
783 return no_page_table(vma, flags);
784
785 return follow_pud_mask(vma, address, p4dp, flags, ctx);
786 }
787
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-01-24 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 2:01 kernel test robot [this message]
2025-01-24 18:43 ` mm/gup.c:778:15: sparse: sparse: cast to non-scalar Peter Xu
-- strict thread matches above, loose matches on Subject: below --
2025-03-04 10:42 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=202501240922.a4YzQD7u-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterx@redhat.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 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.