From: syzbot ci <syzbot+cif1a685ed4fedda3c@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: ovl: brtfs' temp_fsid doesn't work with ovl index=on
Date: Mon, 13 Oct 2025 20:01:07 -0700 [thread overview]
Message-ID: <68edbcf3.050a0220.ac43.0080.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] ovl: brtfs' temp_fsid doesn't work with ovl index=on
https://lore.kernel.org/all/20251014015707.129013-1-andrealmeid@igalia.com
* [RFC PATCH 1/1] ovl: Use fsid as unique identifier for trusted origin
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/4340d138-387c-44f4-8c56-ae6b02b8f9bd
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: 0d97f2067c166eb495771fede9f7b73999c67f66
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/386d1795-79d4-4df9-965d-d25c2114654d/config
fs/overlayfs/copy_up.c:431:9: error: array type '__u8[16]' (aka 'unsigned char[16]') is not assignable
fs/overlayfs/copy_up.c:470:17: error: indirection requires pointer operand ('uuid_t' invalid)
***
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:
[amir73il@gmail.com anand.jain@oracle.com andrealmeid@igalia.com clm@fb.com dsterba@suse.com gpiccoli@igalia.com kernel-dev@igalia.com linux-btrfs@vger.kernel.org linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org linux-unionfs@vger.kernel.org miklos@szeredi.hu]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-10-14 3:01 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=68edbcf3.050a0220.ac43.0080.GAE@google.com \
--to=syzbot+cif1a685ed4fedda3c@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