From: kbuild test robot <lkp@intel.com>
To: Qu Wenruo <wqu@suse.com>
Cc: kbuild-all@01.org, linux-btrfs@vger.kernel.org,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] block: Add new BLK_STS_FSCORRUPTED status
Date: Wed, 10 Apr 2019 21:04:41 +0800 [thread overview]
Message-ID: <201904102123.DfAfZXNP%lkp@intel.com> (raw)
In-Reply-To: <20190410083508.21091-2-wqu@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2404 bytes --]
Hi Qu,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.1-rc4 next-20190410]
[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/Qu-Wenruo/errno-h-Export-EFSCORRUPTED-error-number/20190410-183556
config: sparc64-allyesconfig (attached as .config)
compiler: sparc64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=sparc64
All errors (new ones prefixed by >>):
>> block/blk-core.c:138:29: error: 'EFSCORRUPTED' undeclared here (not in a function); did you mean 'FS_NRSUPER'?
[BLK_STS_FSCORRUPTED] = { -EFSCORRUPTED, "filesystem is corrupted" },
^~~~~~~~~~~~
FS_NRSUPER
vim +138 block/blk-core.c
121
122 static const struct {
123 int errno;
124 const char *name;
125 } blk_errors[] = {
126 [BLK_STS_OK] = { 0, "" },
127 [BLK_STS_NOTSUPP] = { -EOPNOTSUPP, "operation not supported" },
128 [BLK_STS_TIMEOUT] = { -ETIMEDOUT, "timeout" },
129 [BLK_STS_NOSPC] = { -ENOSPC, "critical space allocation" },
130 [BLK_STS_TRANSPORT] = { -ENOLINK, "recoverable transport" },
131 [BLK_STS_TARGET] = { -EREMOTEIO, "critical target" },
132 [BLK_STS_NEXUS] = { -EBADE, "critical nexus" },
133 [BLK_STS_MEDIUM] = { -ENODATA, "critical medium" },
134 [BLK_STS_PROTECTION] = { -EILSEQ, "protection" },
135 [BLK_STS_RESOURCE] = { -ENOMEM, "kernel resource" },
136 [BLK_STS_DEV_RESOURCE] = { -EBUSY, "device resource" },
137 [BLK_STS_AGAIN] = { -EAGAIN, "nonblocking retry" },
> 138 [BLK_STS_FSCORRUPTED] = { -EFSCORRUPTED, "filesystem is corrupted" },
139
140 /* device mapper special case, should not leak out: */
141 [BLK_STS_DM_REQUEUE] = { -EREMCHG, "dm internal retry" },
142
143 /* everything else not covered above: */
144 [BLK_STS_IOERR] = { -EIO, "I/O" },
145 };
146
---
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: 56171 bytes --]
next prev parent reply other threads:[~2019-04-10 13:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 8:35 [PATCH RFC 1/2] errno.h: Export EFSCORRUPTED error number Qu Wenruo
2019-04-10 8:35 ` [PATCH 2/2] block: Add new BLK_STS_FSCORRUPTED status Qu Wenruo
2019-04-10 8:55 ` Nikolay Borisov
2019-04-10 13:04 ` kbuild test robot [this message]
2019-04-10 15:11 ` [PATCH RFC 1/2] errno.h: Export EFSCORRUPTED error number Darrick J. Wong
2019-04-10 15:28 ` Nikolay Borisov
2019-04-11 0:28 ` Qu Wenruo
2019-04-11 1:06 ` Darrick J. Wong
2019-04-11 1:43 ` Qu Wenruo
2019-04-11 1:47 ` Darrick J. Wong
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=201904102123.DfAfZXNP%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=wqu@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.