From: syzbot ci <syzbot+ci7353ed648947c91d@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm, swap: never bypass swap cache and cleanup flags (swap table phase II)
Date: Wed, 29 Oct 2025 09:43:06 -0700 [thread overview]
Message-ID: <6902441a.050a0220.3344a1.042a.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] mm, swap: never bypass swap cache and cleanup flags (swap table phase II)
https://lore.kernel.org/all/20251029-swap-table-p2-v1-0-3d43f3b6ec32@tencent.com
* [PATCH 01/19] mm/swap: rename __read_swap_cache_async to swap_cache_alloc_folio
* [PATCH 02/19] mm, swap: split swap cache preparation loop into a standalone helper
* [PATCH 03/19] mm, swap: never bypass the swap cache even for SWP_SYNCHRONOUS_IO
* [PATCH 04/19] mm, swap: always try to free swap cache for SWP_SYNCHRONOUS_IO devices
* [PATCH 05/19] mm, swap: simplify the code and reduce indention
* [PATCH 06/19] mm, swap: free the swap cache after folio is mapped
* [PATCH 07/19] mm/shmem: never bypass the swap cache for SWP_SYNCHRONOUS_IO
* [PATCH 08/19] mm/shmem, swap: remove SWAP_MAP_SHMEM
* [PATCH 09/19] mm, swap: swap entry of a bad slot should not be considered as swapped out
* [PATCH 10/19] mm, swap: consolidate cluster reclaim and check logic
* [PATCH 11/19] mm, swap: split locked entry duplicating into a standalone helper
* [PATCH 12/19] mm, swap: use swap cache as the swap in synchronize layer
* [PATCH 13/19] mm, swap: remove workaround for unsynchronized swap map cache state
* [PATCH 14/19] mm, swap: sanitize swap entry management workflow
* [PATCH 15/19] mm, swap: add folio to swap cache directly on allocation
* [PATCH 16/19] mm, swap: check swap table directly for checking cache
* [PATCH 17/19] mm, swap: clean up and improve swap entries freeing
* [PATCH 18/19] mm, swap: drop the SWAP_HAS_CACHE flag
* [PATCH 19/19] mm, swap: remove no longer needed _swap_info_get
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/01d6b19c-9614-4f8f-949e-c5adf3eab00f
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: f30d294530d939fa4b77d61bc60f25c4284841fa
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/345b9221-49ac-41ee-9a72-57ed683ef067/config
mm/swapfile.c:1368:2: error: void function 'swap_alloc_slow' should not return a value [-Wreturn-mismatch]
***
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:
[akpm@linux-foundation.org baohua@kernel.org baolin.wang@linux.alibaba.com bhe@redhat.com chrisl@kernel.org david@redhat.com hannes@cmpxchg.org hughd@google.com kasong@tencent.com linux-kernel@vger.kernel.org linux-mm@kvack.org lorenzo.stoakes@oracle.com nphamcs@gmail.com ryncsn@gmail.com shikemeng@huaweicloud.com willy@infradead.org ying.huang@linux.alibaba.com yosry.ahmed@linux.dev youngjun.park@lge.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-10-29 16:43 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=6902441a.050a0220.3344a1.042a.GAE@google.com \
--to=syzbot+ci7353ed648947c91d@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.