From: syzbot ci <syzbot+cie464680588e3636b@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: udf: Fix data loss when converting inline inodes to out of line
Date: Thu, 30 Jul 2026 15:26:02 -0700 [thread overview]
Message-ID: <6a6bcf7a.77639fcc.3d4fd0.0011.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] udf: Fix data loss when converting inline inodes to out of line
https://lore.kernel.org/all/20260729144547.4028292-2-jack@suse.cz
* [PATCH] udf: Fix data loss when converting inline inodes to out of line
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/4fd6ec7d-910f-419f-97fd-98adfdca5e52
***
kernel build error
tree: vfs
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/vfs/vfs.git
base: 05c09c9c8a79d5539fef30d42e732eba90a15dcf
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/bf7f881a-5ac4-4451-8a16-c8d869102893/config
fs/udf/inode.c:348:13: error: use of undeclared identifier 'UDF_MAP_CREATE'
fs/udf/inode.c:346:20: error: variable has incomplete type 'struct udf_map_rq'
fs/udf/inode.c:382:8: error: call to undeclared function 'udf_map_block'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
***
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 patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[jack@suse.cz linux-fsdevel@vger.kernel.org stable@vger.kernel.org]
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-07-30 22:26 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=6a6bcf7a.77639fcc.3d4fd0.0011.GAE@google.com \
--to=syzbot+cie464680588e3636b@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 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.