From: syzbot ci <syzbot+ci858fd911e60e50b6@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: speakup: Serialize synth clearing against locked readers
Date: Mon, 02 Nov 2026 23:20:43 -0800 [thread overview]
Message-ID: <6ae98b4b.80718103.e2fb0.08c2.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] speakup: Serialize synth clearing against locked readers
https://lore.kernel.org/all/179363263139.43100.8043437977710970575@kylinos.cn
* [PATCH v2] speakup: Serialize synth clearing against locked readers
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/dacbf728-8a46-46a5-92e9-5978e917ae77
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
arch: amd64
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/d2e1902d-8835-4425-9c79-e8fd59c6a01f/config
drivers/accessibility/speakup/synth.c:485:45: error: use of undeclared identifier 'flags'
drivers/accessibility/speakup/synth.c:487:50: error: use of undeclared identifier 'flags'
***
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.
To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[chris@the-brannons.com gregkh@linuxfoundation.org kirk@reisers.ca linux-kernel@vger.kernel.org samuel.thibault@ens-lyon.org speakup@linux-speakup.org stable@vger.kernel.org w.d.hubbs@gmail.com xiehongyu1@kylinos.cn]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-11-03 7:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6ae98b4b.80718103.e2fb0.08c2.GAE@google.com \
--to=syzbot+ci858fd911e60e50b6@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