public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Emil Renner Berthing <kernel@esmil.dk>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Palmer Dabbelt <palmer@rivosinc.com>,
	Charlie Jenkins <charlie@rivosinc.com>
Subject: arch/riscv/kernel/module.c:33:25: sparse: sparse: cast to restricted __le16
Date: Thu, 16 Nov 2023 07:00:22 +0800	[thread overview]
Message-ID: <202311160648.Adh0V2Wd-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   c42d9eeef8e5ba9292eda36fd8e3c11f35ee065c
commit: 8cbe0accc4a6ba7ed34812a1c7e1ba67e7f7b2a4 riscv: Avoid unaligned access when relocating modules
date:   8 days ago
config: riscv-randconfig-r133-20231115 (https://download.01.org/0day-ci/archive/20231116/202311160648.Adh0V2Wd-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231116/202311160648.Adh0V2Wd-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/202311160648.Adh0V2Wd-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   WARNING: invalid argument to '-march': '_zihintpause'
>> arch/riscv/kernel/module.c:33:25: sparse: sparse: cast to restricted __le16
   arch/riscv/kernel/module.c:33:55: sparse: sparse: cast to restricted __le16
>> arch/riscv/kernel/module.c:38:19: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned short [usertype] @@     got restricted __le16 [usertype] @@
   arch/riscv/kernel/module.c:38:19: sparse:     expected unsigned short [usertype]
   arch/riscv/kernel/module.c:38:19: sparse:     got restricted __le16 [usertype]
   arch/riscv/kernel/module.c:39:19: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned short [usertype] @@     got restricted __le16 [usertype] @@
   arch/riscv/kernel/module.c:39:19: sparse:     expected unsigned short [usertype]
   arch/riscv/kernel/module.c:39:19: sparse:     got restricted __le16 [usertype]
   arch/riscv/kernel/module.c:46:20: sparse: sparse: cast to restricted __le16
   arch/riscv/kernel/module.c:51:17: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned short [usertype] @@     got restricted __le16 [usertype] @@
   arch/riscv/kernel/module.c:51:17: sparse:     expected unsigned short [usertype]
   arch/riscv/kernel/module.c:51:17: sparse:     got restricted __le16 [usertype]

vim +33 arch/riscv/kernel/module.c

    29	
    30	static int riscv_insn_rmw(void *location, u32 keep, u32 set)
    31	{
    32		u16 *parcel = location;
  > 33		u32 insn = (u32)le16_to_cpu(parcel[0]) | (u32)le16_to_cpu(parcel[1]) << 16;
    34	
    35		insn &= keep;
    36		insn |= set;
    37	
  > 38		parcel[0] = cpu_to_le16(insn);
    39		parcel[1] = cpu_to_le16(insn >> 16);
    40		return 0;
    41	}
    42	

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

                 reply	other threads:[~2023-11-15 23:01 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=202311160648.Adh0V2Wd-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=charlie@rivosinc.com \
    --cc=kernel@esmil.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=palmer@rivosinc.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