From: syzbot ci <syzbot+ci859541442dc092f5@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm/mprotect: micro-optimization work
Date: Fri, 20 Mar 2026 14:22:34 -0700 [thread overview]
Message-ID: <69bdba9a.050a0220.3bf4de.002e.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] mm/mprotect: micro-optimization work
https://lore.kernel.org/all/20260319183108.1105090-1-pfalcato@suse.de
* [PATCH 1/4] mm/mprotect: encourage inlining with __always_inline
* [PATCH 2/4] mm/mprotect: move softleaf code out of the main function
* [PATCH 3/4] mm/mprotect: un-inline folio_pte_batch_flags()
* [PATCH 4/4] mm/mprotect: special-case small folios when applying write permissions
and found the following issue:
SYZFATAL: image testing failed w/o kernel bug
Full report is available here:
https://ci.syzbot.org/series/e0692a77-9ffa-40af-8b48-7b4fc751e44e
***
SYZFATAL: image testing failed w/o kernel bug
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 91bd3a1b2dbec55eab74063fd77e8fdcfc556de6
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/3c14de24-2f65-4ba9-bd9e-0b64ef85fb72/config
***
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 david@kernel.org dev.jain@arm.com jannh@google.com jhladky@redhat.com liam.howlett@oracle.com linux-kernel@vger.kernel.org linux-mm@kvack.org ljs@kernel.org luyang@redhat.com pfalcato@suse.de 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-03-20 21: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=69bdba9a.050a0220.3bf4de.002e.GAE@google.com \
--to=syzbot+ci859541442dc092f5@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