From: kbuild test robot <lkp@intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: kbuild-all@01.org, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <keith.busch@intel.com>,
Hannes Reinecke <hare@suse.de>,
maxg@mellanox.com,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH v2 3/8] nvmet: implement namespace identify descriptor list
Date: Fri, 2 Jun 2017 08:14:59 +0800 [thread overview]
Message-ID: <201706020730.grqRkmRE%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170601111750.20880-4-jthumshirn@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]
Hi Johannes,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.12-rc3 next-20170601]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Johannes-Thumshirn/nvme-introduce-NVMe-Namespace-Identification-Descriptor-structures/20170601-224249
config: x86_64-randconfig-s2-06020617 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the linux-review/Johannes-Thumshirn/nvme-introduce-NVMe-Namespace-Identification-Descriptor-structures/20170601-224249 HEAD eed0e29a990ae9332379fbaf71b249bb482b3c6b builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
drivers/nvme//target/admin-cmd.c: In function 'nvmet_execute_identify_desclist':
>> drivers/nvme//target/admin-cmd.c:383: error: 'struct nvmet_ns' has no member named 'uuid'
>> drivers/nvme//target/admin-cmd.c:383: error: 'struct nvmet_ns' has no member named 'uuid'
drivers/nvme//target/admin-cmd.c:392: error: 'struct nvmet_ns' has no member named 'uuid'
drivers/nvme//target/admin-cmd.c:393: error: 'struct nvmet_ns' has no member named 'uuid'
drivers/nvme//target/admin-cmd.c:396: error: 'struct nvmet_ns' has no member named 'uuid'
vim +383 drivers/nvme//target/admin-cmd.c
377 ns = nvmet_find_namespace(req->sq->ctrl, req->cmd->identify.nsid);
378 if (!ns) {
379 status = NVME_SC_INVALID_NS | NVME_SC_DNR;
380 goto out;
381 }
382
> 383 if (memchr_inv(&ns->uuid, 0, sizeof(ns->uuid))) {
384 memset(&hdr, 0, sizeof(hdr));
385 hdr.nidt = NVME_NIDT_UUID;
386 hdr.nidl = NVME_NIDT_UUID_LEN;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33087 bytes --]
next prev parent reply other threads:[~2017-06-02 0:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 11:17 [PATCH v2 0/8] Implement NVMe Namespace Descriptor Identification Johannes Thumshirn
2017-06-01 11:17 ` [PATCH v2 1/8] nvme: introduce NVMe Namespace Identification Descriptor structures Johannes Thumshirn
2017-06-01 14:07 ` Max Gurtovoy
2017-06-01 11:17 ` [PATCH v2 2/8] nvme: rename uuid to nguid in nvme_ns Johannes Thumshirn
2017-06-07 13:47 ` Andy Shevchenko
2017-06-07 13:49 ` Johannes Thumshirn
2017-06-01 11:17 ` [PATCH v2 3/8] nvmet: implement namespace identify descriptor list Johannes Thumshirn
2017-06-01 23:08 ` kbuild test robot
2017-06-02 0:14 ` kbuild test robot [this message]
2017-06-01 11:17 ` [PATCH v2 4/8] nvmet: add uuid field to nvme_ns and populate via configfs Johannes Thumshirn
2017-06-01 11:17 ` [PATCH v2 5/8] nvme: get list of namespace descriptors Johannes Thumshirn
2017-06-01 11:17 ` [PATCH v2 6/8] nvme: provide UUID value to userspace Johannes Thumshirn
2017-06-01 12:47 ` Keith Busch
2017-06-01 13:01 ` Johannes Thumshirn
2017-06-01 11:17 ` [PATCH v2 7/8] nvmet: allow overriding the NVMe VS via configfs Johannes Thumshirn
2017-06-01 11:17 ` [PATCH v2 8/8] nvmet: use NVME_IDENTIFY_DATA_SIZE Johannes Thumshirn
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=201706020730.grqRkmRE%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=kbuild-all@01.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=maxg@mellanox.com \
--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).