From: kernel test robot <lkp@intel.com>
To: Md Sadre Alam <quic_mdalam@quicinc.com>,
axboe@kernel.dk, song@kernel.org, yukuai3@huawei.com,
agk@redhat.com, snitzer@kernel.org, mpatocka@redhat.com,
adrian.hunter@intel.com, quic_asutoshd@quicinc.com,
ritesh.list@gmail.com, ulf.hansson@linaro.org,
andersson@kernel.org, konradybcio@kernel.org, kees@kernel.org,
gustavoars@kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
dm-devel@lists.linux.dev, linux-mmc@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-hardening@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, quic_srichara@quicinc.com,
quic_varada@quicinc.com, quic_mdalam@quicinc.com
Subject: Re: [PATCH v2 1/3] dm-inlinecrypt: Add inline encryption support
Date: Wed, 18 Sep 2024 13:08:09 +0800 [thread overview]
Message-ID: <202409181233.1FrQNVtU-lkp@intel.com> (raw)
In-Reply-To: <20240916085741.1636554-2-quic_mdalam@quicinc.com>
Hi Md,
kernel test robot noticed the following build warnings:
[auto build test WARNING on device-mapper-dm/for-next]
[also build test WARNING on axboe-block/for-next linus/master song-md/md-next v6.11 next-20240917]
[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/Md-Sadre-Alam/dm-inlinecrypt-Add-inline-encryption-support/20240916-170452
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
patch link: https://lore.kernel.org/r/20240916085741.1636554-2-quic_mdalam%40quicinc.com
patch subject: [PATCH v2 1/3] dm-inlinecrypt: Add inline encryption support
config: csky-randconfig-r111-20240918 (https://download.01.org/0day-ci/archive/20240918/202409181233.1FrQNVtU-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20240918/202409181233.1FrQNVtU-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/202409181233.1FrQNVtU-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/md/dm-inline-crypt.c:120:26: sparse: sparse: cast to restricted __le64
drivers/md/dm-inline-crypt.c:214:32: sparse: sparse: self-comparison always evaluates to false
vim +120 drivers/md/dm-inline-crypt.c
109
110 static void crypt_inline_encrypt_submit(struct dm_target *ti, struct bio *bio)
111 {
112 struct inlinecrypt_config *cc = ti->private;
113 u64 dun[BLK_CRYPTO_DUN_ARRAY_SIZE];
114
115 bio_set_dev(bio, cc->dev->bdev);
116 if (bio_sectors(bio)) {
117 memset(dun, 0, BLK_CRYPTO_MAX_IV_SIZE);
118 bio->bi_iter.bi_sector = cc->start +
119 dm_target_offset(ti, bio->bi_iter.bi_sector);
> 120 dun[0] = le64_to_cpu(bio->bi_iter.bi_sector + cc->iv_offset);
121 bio_crypt_set_ctx(bio, cc->blk_key, dun, GFP_KERNEL);
122 }
123
124 submit_bio_noacct(bio);
125 }
126
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-18 5:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 8:57 [PATCH v2 0/3] Add inline encryption support Md Sadre Alam
2024-09-16 8:57 ` [PATCH v2 1/3] dm-inlinecrypt: " Md Sadre Alam
2024-09-17 5:05 ` kernel test robot
2024-09-17 6:38 ` kernel test robot
2024-09-18 5:08 ` kernel test robot [this message]
2024-09-21 18:55 ` Eric Biggers
2024-09-24 7:44 ` Christoph Hellwig
2024-09-24 22:04 ` Eric Biggers
2024-10-01 8:37 ` Christoph Hellwig
2024-10-18 3:26 ` Adrian Vovk
2024-10-18 5:22 ` Christoph Hellwig
[not found] ` <CAAdYy_mVy3uXPqWbjPzK_i8w7Okq73wKBQyc95TbnonE36rPgQ@mail.gmail.com>
2024-10-18 5:56 ` Christoph Hellwig
2024-10-18 15:03 ` Adrian Vovk
2024-10-23 6:57 ` Christoph Hellwig
2024-10-24 2:52 ` Adrian Vovk
2024-10-24 3:17 ` Adrian Vovk
2024-10-24 6:14 ` Christoph Hellwig
2024-10-24 7:52 ` Adrian Vovk
2024-10-24 9:04 ` Christoph Hellwig
2024-10-24 15:32 ` Adrian Vovk
2024-10-24 15:59 ` Christoph Hellwig
2024-10-24 16:23 ` Adrian Vovk
2024-10-29 11:08 ` Mikulas Patocka
2024-10-24 8:11 ` Geoff Back
2024-10-24 15:28 ` Adrian Vovk
2024-10-24 19:21 ` John Stoffel
2024-10-24 20:45 ` Adrian Vovk
2024-10-15 10:59 ` Mikulas Patocka
2024-09-16 8:57 ` [PATCH v2 2/3] mmc: cqhci: Add additional algo mode for inline encryption Md Sadre Alam
2024-09-16 8:57 ` [PATCH v2 3/3] mmc: sdhci-msm: " Md Sadre Alam
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=202409181233.1FrQNVtU-lkp@intel.com \
--to=lkp@intel.com \
--cc=adrian.hunter@intel.com \
--cc=agk@redhat.com \
--cc=andersson@kernel.org \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_asutoshd@quicinc.com \
--cc=quic_mdalam@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=ritesh.list@gmail.com \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=yukuai3@huawei.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;
as well as URLs for NNTP newsgroup(s).