From: kbuild test robot <lkp@intel.com>
To: linux-kernel-owner@vger.kernel.org
Cc: kbuild-all@01.org, Zhouyang Jia <jiazhouyang09@gmail.com>,
Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] xen/scsiback: add error handling for xenbus_printf
Date: Sat, 16 Jun 2018 03:22:27 +0800 [thread overview]
Message-ID: <201806160344.bKH3FDHG%fengguang.wu@intel.com> (raw)
In-Reply-To: <1529082372-59097-1-git-send-email-jiazhouyang09@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2283 bytes --]
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on xen-tip/linux-next]
[also build test ERROR on v4.17 next-20180615]
[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/linux-kernel-owner-vger-kernel-org/xen-scsiback-add-error-handling-for-xenbus_printf/20180616-011349
base: https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git linux-next
config: i386-randconfig-x009-201823 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers//xen/xen-scsiback.c: In function 'scsiback_do_add_lun':
>> drivers//xen/xen-scsiback.c:1032:32: error: 'err' undeclared (first use in this function)
xenbus_dev_error(info->dev, err,
^~~
drivers//xen/xen-scsiback.c:1032:32: note: each undeclared identifier is reported only once for each function it appears in
vim +/err +1032 drivers//xen/xen-scsiback.c
1009
1010 static void scsiback_do_add_lun(struct vscsibk_info *info, const char *state,
1011 char *phy, struct ids_tuple *vir, int try)
1012 {
1013 struct v2p_entry *entry;
1014 unsigned long flags;
1015
1016 if (try) {
1017 spin_lock_irqsave(&info->v2p_lock, flags);
1018 entry = scsiback_chk_translation_entry(info, vir);
1019 spin_unlock_irqrestore(&info->v2p_lock, flags);
1020 if (entry)
1021 return;
1022 }
1023 if (!scsiback_add_translation_entry(info, phy, vir)) {
1024 if (xenbus_printf(XBT_NIL, info->dev->nodename, state,
1025 "%d", XenbusStateInitialised)) {
1026 pr_err("xenbus_printf error %s\n", state);
1027 scsiback_del_translation_entry(info, vir);
1028 }
1029 } else if (!try) {
1030 if (xenbus_printf(XBT_NIL, info->dev->nodename, state,
1031 "%d", XenbusStateClosed))
> 1032 xenbus_dev_error(info->dev, err,
1033 "%s: writing %s", __func__, state);
1034 }
1035 }
1036
---
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: 32088 bytes --]
next prev parent reply other threads:[~2018-06-15 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 3:46 [PATCH] " Zhouyang Jia
2018-06-15 17:06 ` [PATCH v2] " Zhouyang Jia
2018-06-15 19:22 ` kbuild test robot [this message]
2018-06-16 0:14 ` [PATCH v3] " Zhouyang Jia
2018-06-19 12:52 ` Juergen Gross
2018-06-19 13:01 ` Juergen Gross
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=201806160344.bKH3FDHG%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=jiazhouyang09@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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
all inboxes | Powered by JetHome®