mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Will Deacon <will@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: arch/arm64/kernel/efi.c:88:21: sparse: sparse: cast to non-scalar
Date: Tue, 7 Jul 2020 02:27:11 +0800	[thread overview]
Message-ID: <202007070205.1i4bao5c%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2597 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   dcb7fd82c75ee2d6e6f9d8cc71c52519ed52e258
commit: dee081bf8f824cabeb7c7495367d5dad0a444eb1 READ_ONCE: Drop pointer qualifiers when reading from scalar types
date:   3 months ago
config: arm64-randconfig-s032-20200706 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.2-14-g8fce3d7a-dirty
        git checkout dee081bf8f824cabeb7c7495367d5dad0a444eb1
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=arm64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> arch/arm64/kernel/efi.c:88:21: sparse: sparse: cast to non-scalar
>> arch/arm64/kernel/efi.c:88:21: sparse: sparse: cast from non-scalar

vim +88 arch/arm64/kernel/efi.c

f7d92489426579 Ard Biesheuvel    2015-11-30  84  
8b1e0f81fb6fcf Anshuman Khandual 2019-07-11  85  static int __init set_permissions(pte_t *ptep, unsigned long addr, void *data)
bd264d046aad25 Ard Biesheuvel    2016-06-29  86  {
bd264d046aad25 Ard Biesheuvel    2016-06-29  87  	efi_memory_desc_t *md = data;
20a004e7b017cc Will Deacon       2018-02-15 @88  	pte_t pte = READ_ONCE(*ptep);
bd264d046aad25 Ard Biesheuvel    2016-06-29  89  
bd264d046aad25 Ard Biesheuvel    2016-06-29  90  	if (md->attribute & EFI_MEMORY_RO)
bd264d046aad25 Ard Biesheuvel    2016-06-29  91  		pte = set_pte_bit(pte, __pgprot(PTE_RDONLY));
bd264d046aad25 Ard Biesheuvel    2016-06-29  92  	if (md->attribute & EFI_MEMORY_XP)
bd264d046aad25 Ard Biesheuvel    2016-06-29  93  		pte = set_pte_bit(pte, __pgprot(PTE_PXN));
bd264d046aad25 Ard Biesheuvel    2016-06-29  94  	set_pte(ptep, pte);
bd264d046aad25 Ard Biesheuvel    2016-06-29  95  	return 0;
bd264d046aad25 Ard Biesheuvel    2016-06-29  96  }
bd264d046aad25 Ard Biesheuvel    2016-06-29  97  

:::::: The code at line 88 was first introduced by commit
:::::: 20a004e7b017cce282a46ac5d02c2b9c6b9bb1fa arm64: mm: Use READ_ONCE/WRITE_ONCE when accessing page tables

:::::: TO: Will Deacon <will.deacon@arm.com>
:::::: CC: Catalin Marinas <catalin.marinas@arm.com>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37441 bytes --]

                 reply	other threads:[~2020-07-06 19:00 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=202007070205.1i4bao5c%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will@kernel.org \
    /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

all inboxes | Powered by JetHome®