From: syzbot ci <syzbot+ci13de108e9834717f@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: fs: Replace user_access_{begin/end} by scoped user access
Date: Tue, 10 Mar 2026 16:26:56 -0700 [thread overview]
Message-ID: <69b0a8c0.a70a0220.51e36.0004.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] fs: Replace user_access_{begin/end} by scoped user access
https://lore.kernel.org/all/5021aa325554b3d2437341514ab0a2977e158274.1773153431.git.chleroy@kernel.org
* [PATCH] fs: Replace user_access_{begin/end} by scoped user access
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/c5ff6b4a-5474-49d1-84d5-d436ae5ee0ef
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 1f318b96cc84d7c2ab792fcc0bfd42a7ca890681
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/376590a1-6630-4285-a1fe-4d05a61dc629/config
fs/readdir.c:454:26: error: too few arguments provided to function-like macro invocation
fs/readdir.c:452:2: error: use of undeclared identifier 'scoped_user_write_access_size'; did you mean '__scoped_user_write_access_end'?
fs/readdir.c:454:29: error: use of undeclared identifier 'efault'
fs/readdir.c:532:60: error: use of undeclared label 'efault'
fs/readdir.c:540:2: error: unknown type name 'buf'
fs/readdir.c:540:5: error: expected identifier or '('
fs/readdir.c:541:2: error: unknown type name 'buf'
fs/readdir.c:541:5: error: expected identifier or '('
fs/readdir.c:542:2: error: unknown type name 'ctx'
fs/readdir.c:542:5: error: expected identifier or '('
fs/readdir.c:543:2: error: expected identifier or '('
fs/readdir.c:544:1: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
fs/readdir.c:544:7: error: expected ';' after top level declarator
fs/readdir.c:545:2: error: unknown type name 'buf'
fs/readdir.c:545:5: error: expected identifier or '('
fs/readdir.c:546:2: error: expected identifier or '('
fs/readdir.c:547:1: error: extraneous closing brace ('}')
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
The email will later be sent to:
[brauner@kernel.org chleroy@kernel.org david.laight.linux@gmail.com jack@suse.cz linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org tglx@linutronix.de torvalds@linux-foundation.org viro@zeniv.linux.org.uk]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
next reply other threads:[~2026-03-10 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 23:26 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-13 3:43 [moderation/CI] Re: fs: Replace user_access_{begin/end} by scoped user access syzbot ci
2026-03-15 12:28 ` Aleksandr Nogikh
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=69b0a8c0.a70a0220.51e36.0004.GAE@google.com \
--to=syzbot+ci13de108e9834717f@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox