From: syzbot ci <syzbot+cid215e48543b447a0@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: liveupdate: Preserve tmpfs files across Live Update
Date: Fri, 23 Oct 2026 05:22:47 -0700 [thread overview]
Message-ID: <6adb5197.3ebfcf67.79b0c.25a5.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] liveupdate: Preserve tmpfs files across Live Update
https://lore.kernel.org/all/20261022225035.377445-1-dmatlack@google.com
* [PATCH v2 01/10] liveupdate: Pass user argument to file preserve and retrieve
* [PATCH v2 02/10] selftests: liveupdate: Add tests for preserve and retrieve user argument
* [PATCH v2 03/10] liveupdate: Allow file handlers to mark retrieve failures as retryable
* [PATCH v2 04/10] mm: Rename memfd_luo to shmem_luo
* [PATCH v2 05/10] liveupdate: Don't WARN if tracking a retrieved file fails
* [PATCH v2 06/10] mm/shmem_luo: Don't make early retrieve failures permanent
* [PATCH v2 07/10] mm/shmem_luo: Retrieve tmpfs files onto a tmpfs mount chosen by userspace
* [PATCH v2 08/10] mm/shmem_luo: Allow preserving tmpfs files that are still linked
* [PATCH v2 09/10] mm/shmem_luo: Allow retrieving tmpfs files with O_RDONLY
* [PATCH v2 10/10] selftests/liveupdate: Add a test for preserving tmpfs files
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/2816c2da-cbb6-401c-a706-161071b40ae4
***
kernel build error
tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: bd1ecbb61afefc6a8b876ccbc31e9228b44e9eab
arch: amd64
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/87530454-496d-4027-a57a-40856ca7f0f5/config
mm/shmem_luo.c:335:20: error: initializing 'struct mnt_idmap *' with an expression of type 'const struct mnt_idmap *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
***
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:
[akpm@linux-foundation.org baolin.wang@linux.alibaba.com brauner@kernel.org corbet@lwn.net david@kernel.org dmatlack@google.com graf@amazon.com hughd@google.com kexec@lists.infradead.org liam@infradead.org linux-doc@vger.kernel.org linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org linux-mm@kvack.org ljs@kernel.org mhocko@suse.com pasha.tatashin@soleen.com pratyush@kernel.org rdunlap@infradead.org rppt@kernel.org skhan@linuxfoundation.org skhawaja@google.com surenb@google.com vbabka@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-10-23 12:22 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=6adb5197.3ebfcf67.79b0c.25a5.GAE@google.com \
--to=syzbot+cid215e48543b447a0@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