From: kbuild test robot <lkp@intel.com>
To: Milan Broz <gmazyland@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mike Snitzer <snitzer@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: drivers/md/dm-crypt.c:792:24: sparse: sparse: cast from restricted __le32
Date: Thu, 28 May 2020 18:15:33 +0800 [thread overview]
Message-ID: <202005281832.4bGes70k%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b0c3ba31be3e45a130e13b278cf3b90f69bda6f6
commit: bbb1658461ac85ef7e0563bb11283f94ea5eb651 dm crypt: Implement Elephant diffuser for Bitlocker compatibility
date: 4 months ago
config: parisc-randconfig-s032-20200528 (attached as .config)
compiler: hppa-linux-gcc (GCC) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-240-gf0fe1cd9-dirty
git checkout bbb1658461ac85ef7e0563bb11283f94ea5eb651
# save the attached .config to linux build tree
make W=1 C=1 ARCH=parisc CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
./arch/parisc/include/generated/uapi/asm/unistd_32.h:380:41: sparse: sparse: no newline at end of file
drivers/md/dm-crypt.c:782:24: sparse: sparse: cast to restricted __le32
drivers/md/dm-crypt.c:782:24: sparse: sparse: cast to restricted __le32
drivers/md/dm-crypt.c:782:24: sparse: sparse: cast to restricted __le32
drivers/md/dm-crypt.c:782:24: sparse: sparse: cast to restricted __le32
drivers/md/dm-crypt.c:782:24: sparse: sparse: cast to restricted __le32
drivers/md/dm-crypt.c:782:24: sparse: sparse: cast to restricted __le32
>> drivers/md/dm-crypt.c:792:24: sparse: sparse: cast from restricted __le32
>> drivers/md/dm-crypt.c:792:24: sparse: sparse: cast from restricted __le32
>> drivers/md/dm-crypt.c:792:24: sparse: sparse: cast from restricted __le32
>> drivers/md/dm-crypt.c:792:24: sparse: sparse: cast from restricted __le32
>> drivers/md/dm-crypt.c:792:24: sparse: sparse: cast from restricted __le32
>> drivers/md/dm-crypt.c:792:24: sparse: sparse: cast from restricted __le32
vim +792 drivers/md/dm-crypt.c
785
786 static void diffuser_cpu_to_disk(__le32 *d, size_t n)
787 {
788 #ifndef __LITTLE_ENDIAN
789 int i;
790
791 for (i = 0; i < n; i++)
> 792 d[i] = cpu_to_le32((u32)d[i]);
793 #endif
794 }
795
---
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: 33209 bytes --]
reply other threads:[~2020-05-28 10:40 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=202005281832.4bGes70k%lkp@intel.com \
--to=lkp@intel.com \
--cc=gmazyland@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome