From: kernel test robot <lkp@intel.com>
To: Keith Busch <kbusch@meta.com>,
axboe@kernel.dk, hch@lst.de, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-fsdevel@vger.kernel.org,
io-uring@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, sagi@grimberg.me,
asml.silence@gmail.com, anuj20.g@samsung.com,
joshi.k@samsung.com, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv13 10/11] nvme: register fdp parameters with the block layer
Date: Wed, 11 Dec 2024 22:40:15 +0800 [thread overview]
Message-ID: <202412112244.XIKhzaWR-lkp@intel.com> (raw)
In-Reply-To: <20241210194722.1905732-11-kbusch@meta.com>
Hi Keith,
kernel test robot noticed the following build warnings:
[auto build test WARNING on axboe-block/for-next]
[also build test WARNING on next-20241211]
[cannot apply to brauner-vfs/vfs.all hch-configfs/for-next linus/master v6.13-rc2]
[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/Keith-Busch/fs-add-a-write-stream-field-to-the-kiocb/20241211-080803
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
patch link: https://lore.kernel.org/r/20241210194722.1905732-11-kbusch%40meta.com
patch subject: [PATCHv13 10/11] nvme: register fdp parameters with the block layer
config: i386-buildonly-randconfig-002-20241211 (https://download.01.org/0day-ci/archive/20241211/202412112244.XIKhzaWR-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241211/202412112244.XIKhzaWR-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/202412112244.XIKhzaWR-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/device.h:15,
from include/linux/async.h:14,
from drivers/nvme/host/core.c:7:
drivers/nvme/host/core.c: In function 'nvme_query_fdp_granularity':
>> drivers/nvme/host/core.c:2176:26: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
2176 | "failed to allocate %lu bytes for FDP config log\n",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:110:30: note: in definition of macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ^~~
include/linux/dev_printk.h:156:61: note: in expansion of macro 'dev_fmt'
156 | dev_printk_index_wrap(_dev_warn, KERN_WARNING, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~
drivers/nvme/host/core.c:2175:17: note: in expansion of macro 'dev_warn'
2175 | dev_warn(ctrl->device,
| ^~~~~~~~
drivers/nvme/host/core.c:2176:48: note: format string is defined here
2176 | "failed to allocate %lu bytes for FDP config log\n",
| ~~^
| |
| long unsigned int
| %u
In file included from include/linux/device.h:15,
from include/linux/async.h:14,
from drivers/nvme/host/core.c:7:
drivers/nvme/host/core.c: In function 'nvme_query_fdp_info':
drivers/nvme/host/core.c:2254:26: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
2254 | "failed to allocate %lu bytes for FDP io-mgmt\n",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:110:30: note: in definition of macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ^~~
include/linux/dev_printk.h:156:61: note: in expansion of macro 'dev_fmt'
156 | dev_printk_index_wrap(_dev_warn, KERN_WARNING, dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~
drivers/nvme/host/core.c:2253:17: note: in expansion of macro 'dev_warn'
2253 | dev_warn(ctrl->device,
| ^~~~~~~~
drivers/nvme/host/core.c:2254:48: note: format string is defined here
2254 | "failed to allocate %lu bytes for FDP io-mgmt\n",
| ~~^
| |
| long unsigned int
| %u
vim +2176 drivers/nvme/host/core.c
2153
2154 static int nvme_query_fdp_granularity(struct nvme_ctrl *ctrl,
2155 struct nvme_ns_info *info, u8 fdp_idx)
2156 {
2157 struct nvme_fdp_config_log hdr, *h;
2158 struct nvme_fdp_config_desc *desc;
2159 size_t size = sizeof(hdr);
2160 int i, n, ret;
2161 void *log;
2162
2163 ret = nvme_get_log_lsi(ctrl, 0, NVME_LOG_FDP_CONFIGS, 0,
2164 NVME_CSI_NVM, &hdr, size, 0, info->endgid);
2165 if (ret) {
2166 dev_warn(ctrl->device,
2167 "FDP configs log header status:0x%x endgid:%x\n", ret,
2168 info->endgid);
2169 return ret;
2170 }
2171
2172 size = le32_to_cpu(hdr.sze);
2173 h = kzalloc(size, GFP_KERNEL);
2174 if (!h) {
2175 dev_warn(ctrl->device,
> 2176 "failed to allocate %lu bytes for FDP config log\n",
2177 size);
2178 return -ENOMEM;
2179 }
2180
2181 ret = nvme_get_log_lsi(ctrl, 0, NVME_LOG_FDP_CONFIGS, 0,
2182 NVME_CSI_NVM, h, size, 0, info->endgid);
2183 if (ret) {
2184 dev_warn(ctrl->device,
2185 "FDP configs log status:0x%x endgid:%x\n", ret,
2186 info->endgid);
2187 goto out;
2188 }
2189
2190 n = le16_to_cpu(h->numfdpc) + 1;
2191 if (fdp_idx > n) {
2192 dev_warn(ctrl->device, "FDP index:%d out of range:%d\n",
2193 fdp_idx, n);
2194 /* Proceed without registering FDP streams */
2195 ret = 0;
2196 goto out;
2197 }
2198
2199 log = h + 1;
2200 desc = log;
2201 for (i = 0; i < fdp_idx; i++) {
2202 log += le16_to_cpu(desc->dsze);
2203 desc = log;
2204 }
2205
2206 if (le32_to_cpu(desc->nrg) > 1) {
2207 dev_warn(ctrl->device, "FDP NRG > 1 not supported\n");
2208 ret = 0;
2209 goto out;
2210 }
2211
2212 info->runs = le64_to_cpu(desc->runs);
2213 out:
2214 kfree(h);
2215 return ret;
2216 }
2217
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-12-11 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 19:47 [PATCHv13 00/11] block write streams with nvme fdp Keith Busch
2024-12-10 19:47 ` [PATCHv13 10/11] nvme: register fdp parameters with the block layer Keith Busch
2024-12-11 6:41 ` Nitesh Shetty
2024-12-11 9:30 ` John Garry
2024-12-11 15:55 ` Keith Busch
2024-12-11 11:23 ` Hannes Reinecke
2024-12-11 14:40 ` kernel test robot [this message]
2024-12-11 17:18 ` kernel test robot
[not found] ` <CGME20241211060149epcas5p4d16e78bd3d184e57465c3622a2c8e98d@epcas5p4.samsung.com>
[not found] ` <20241210194722.1905732-6-kbusch@meta.com>
2024-12-11 5:53 ` [PATCHv13 05/11] block: expose write streams for block device nodes Nitesh Shetty
[not found] ` <CGME20241211065235epcas5p2a233ac902da67bf2d755d21d98e6eb21@epcas5p2.samsung.com>
[not found] ` <20241210194722.1905732-7-kbusch@meta.com>
2024-12-11 6:44 ` [PATCHv13 06/11] io_uring: enable per-io write streams Nitesh Shetty
2024-12-11 7:13 ` [PATCHv13 00/11] block write streams with nvme fdp Christoph Hellwig
2024-12-12 5:51 ` Kanchan Joshi
2024-12-12 6:05 ` Christoph Hellwig
[not found] ` <20241210194722.1905732-5-kbusch@meta.com>
2024-12-11 8:46 ` [PATCHv13 04/11] block: introduce a write_stream_granularity queue limit John Garry
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=202412112244.XIKhzaWR-lkp@intel.com \
--to=lkp@intel.com \
--cc=anuj20.g@samsung.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sagi@grimberg.me \
/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).