From: Pavel Begunkov <asml.silence@gmail.com>
To: Matthew Wilcox <willy@infradead.org>,
Veronika Kabatova <vkabatov@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
CKI Project <cki-project@redhat.com>,
linux-block@vger.kernel.org
Subject: Re: ❌ FAIL: Test report for kernel 5.13.0-rc6 (block, b0740de3)
Date: Mon, 21 Jun 2021 23:57:06 +0100 [thread overview]
Message-ID: <8a7b26a3-a17d-e851-690a-5a33b06f5dec@gmail.com> (raw)
In-Reply-To: <YNELoqls01MVLsuT@casper.infradead.org>
On 6/21/21 10:58 PM, Matthew Wilcox wrote:
> On Mon, Jun 21, 2021 at 11:07:16PM +0200, Veronika Kabatova wrote:
>> On Mon, Jun 21, 2021 at 11:00 PM Jens Axboe <axboe@kernel.dk> wrote:
>>>
>>> On 6/21/21 2:57 PM, Veronika Kabatova wrote:
>>>> On Mon, Jun 21, 2021 at 9:20 PM Veronika Kabatova <vkabatov@redhat.com> wrote:
>>>>>
>>>>> On Mon, Jun 21, 2021 at 9:17 PM CKI Project <cki-project@redhat.com> wrote:
>>>>>>
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> We ran automated tests on a recent commit from this kernel tree:
>>>>>>
>>>>>> Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
>>>>>> Commit: b0740de3330a - Merge branch 'for-5.14/drivers-late' into for-next
>>>>>>
>>>>>> The results of these automated tests are provided below.
>>>>>>
>>>>>> Overall result: FAILED (see details below)
>>>>>> Merge: OK
>>>>>> Compile: FAILED
>>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> the failure is introduced between this commit and d142f908ebab64955eb48e.
>>>>> Currently seeing if I can bisect it closer but maybe someone already has an
>>>>> idea what went wrong.
>>>>>
>>>>
>>>> First commit failing the compilation is 7a2b0ef2a3b83733d7.
>>>
>>> Where's the log? Adding Willy...
>>>
>>
>> Logs and kernel configs for each arch are linked in the original email at
>> https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/06/21/324657779
>
> Which aren't there by the time they get to the original commit author.
> You need to do better than this; the Intel build-bot bisects to the
> commit which actually causes the error.
Matthew, I've just followed the link out of curiosity:
...
00:04:22 In file included from fs/orangefs/inode.c:14:
00:04:22 ./include/linux/fileattr.h:36:60: warning: ‘struct fsxattr’ declared inside parameter list will not be visible outside of this definition or declaration
00:04:22 36 | int copy_fsxattr_to_user(const struct fileattr *fa, struct fsxattr __user *ufa);
00:04:22 | ^~~~~~~
00:04:22 ./include/linux/fileattr.h: In function ‘fileattr_has_fsx’:
00:04:22 ./include/linux/fileattr.h:13:10: error: ‘FS_XFLAG_SYNC’ undeclared (first use in this function)
00:04:22 13 | (FS_XFLAG_SYNC | FS_XFLAG_IMMUTABLE | FS_XFLAG_APPEND | \
00:04:22 | ^~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:51:37: note: in expansion of macro ‘FS_XFLAG_COMMON’
00:04:22 51 | ((fa->fsx_xflags & ~FS_XFLAG_COMMON) || fa->fsx_extsize != 0 ||
00:04:22 | ^~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:13:10: note: each undeclared identifier is reported only once for each function it appears in
00:04:22 13 | (FS_XFLAG_SYNC | FS_XFLAG_IMMUTABLE | FS_XFLAG_APPEND | \
00:04:22 | ^~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:51:37: note: in expansion of macro ‘FS_XFLAG_COMMON’
00:04:22 51 | ((fa->fsx_xflags & ~FS_XFLAG_COMMON) || fa->fsx_extsize != 0 ||
00:04:22 | ^~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:13:26: error: ‘FS_XFLAG_IMMUTABLE’ undeclared (first use in this function)
00:04:22 13 | (FS_XFLAG_SYNC | FS_XFLAG_IMMUTABLE | FS_XFLAG_APPEND | \
00:04:22 | ^~~~~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:51:37: note: in expansion of macro ‘FS_XFLAG_COMMON’
00:04:22 51 | ((fa->fsx_xflags & ~FS_XFLAG_COMMON) || fa->fsx_extsize != 0 ||
00:04:22 | ^~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:13:47: error: ‘FS_XFLAG_APPEND’ undeclared (first use in this function)
00:04:22 13 | (FS_XFLAG_SYNC | FS_XFLAG_IMMUTABLE | FS_XFLAG_APPEND | \
00:04:22 | ^~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:51:37: note: in expansion of macro ‘FS_XFLAG_COMMON’
00:04:22 51 | ((fa->fsx_xflags & ~FS_XFLAG_COMMON) || fa->fsx_extsize != 0 ||
00:04:22 | ^~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:14:10: error: ‘FS_XFLAG_NODUMP’ undeclared (first use in this function); did you mean ‘FS_XFLAG_COMMON’?
00:04:22 14 | FS_XFLAG_NODUMP | FS_XFLAG_NOATIME | FS_XFLAG_DAX | \
00:04:22 | ^~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:51:37: note: in expansion of macro ‘FS_XFLAG_COMMON’
00:04:22 51 | ((fa->fsx_xflags & ~FS_XFLAG_COMMON) || fa->fsx_extsize != 0 ||
00:04:22 | ^~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:14:28: error: ‘FS_XFLAG_NOATIME’ undeclared (first use in this function)
00:04:22 14 | FS_XFLAG_NODUMP | FS_XFLAG_NOATIME | FS_XFLAG_DAX | \
00:04:22 | ^~~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:51:37: note: in expansion of macro ‘FS_XFLAG_COMMON’
00:04:22 51 | ((fa->fsx_xflags & ~FS_XFLAG_COMMON) || fa->fsx_extsize != 0 ||
00:04:22 | ^~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:14:47: error: ‘FS_XFLAG_DAX’ undeclared (first use in this function)
00:04:22 14 | FS_XFLAG_NODUMP | FS_XFLAG_NOATIME | FS_XFLAG_DAX | \
00:04:22 | ^~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:51:37: note: in expansion of macro ‘FS_XFLAG_COMMON’
00:04:22 51 | ((fa->fsx_xflags & ~FS_XFLAG_COMMON) || fa->fsx_extsize != 0 ||
00:04:22 | ^~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:15:10: error: ‘FS_XFLAG_PROJINHERIT’ undeclared (first use in this function)
00:04:22 15 | FS_XFLAG_PROJINHERIT)
00:04:22 | ^~~~~~~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h:51:37: note: in expansion of macro ‘FS_XFLAG_COMMON’
00:04:22 51 | ((fa->fsx_xflags & ~FS_XFLAG_COMMON) || fa->fsx_extsize != 0 ||
00:04:22 | ^~~~~~~~~~~~~~~
00:04:22 ./include/linux/fileattr.h: At top level:
00:04:22 ./include/linux/fileattr.h:55:29: warning: ‘struct dentry’ declared inside parameter list will not be visible outside of this definition or declaration
00:04:22 55 | int vfs_fileattr_get(struct dentry *dentry, struct fileattr *fa);
00:04:22 | ^~~~~~
00:04:22 ./include/linux/fileattr.h:56:64: warning: ‘struct dentry’ declared inside parameter list will not be visible outside of this definition or declaration
00:04:22 56 | int vfs_fileattr_set(struct user_namespace *mnt_userns, struct dentry *dentry,
00:04:22 | ^~~~~~
00:04:22 ./include/linux/fileattr.h: In function ‘fileattr_has_fsx’:
00:04:22 ./include/linux/fileattr.h:53:1: error: control reaches end of non-void function [-Werror=return-type]
00:04:22 53 | }
00:04:22 | ^
00:04:22 cc1: some warnings being treated as errors
...
--
Pavel Begunkov
next prev parent reply other threads:[~2021-06-21 22:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cki.3F4F097E3B.299V5OKJ7M@redhat.com>
2021-06-21 19:20 ` ❌ FAIL: Test report for kernel 5.13.0-rc6 (block, b0740de3) Veronika Kabatova
2021-06-21 20:57 ` Veronika Kabatova
2021-06-21 21:00 ` Jens Axboe
2021-06-21 21:07 ` Veronika Kabatova
2021-06-21 21:58 ` Matthew Wilcox
2021-06-21 22:57 ` Pavel Begunkov [this message]
2021-06-21 23:32 ` Matthew Wilcox
2021-06-21 23:42 ` Jens Axboe
2021-06-21 23:49 ` Matthew Wilcox
2021-06-22 0:48 ` Jens Axboe
2021-06-21 23:36 ` Jens Axboe
2021-06-21 21:10 ` Keith Busch
2021-06-21 21:13 ` Jens Axboe
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=8a7b26a3-a17d-e851-690a-5a33b06f5dec@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=cki-project@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=vkabatov@redhat.com \
--cc=willy@infradead.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 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.